How To Double Firefox Speed

1. Type about:config in the address bar and then press Enter.
2. In the filter search bar type network.http.pipelining. Be sure the value field is set true,if not double-click to set true.
3. Go back to the filter search bar and type network.http.pipelining.maxrequests. Double-click this option and set its value to 8.
4. In the filter search bar and type network.http.proxy.pipelining. Once opened double-click on it and set it to true.
5. In IPv6-capable DNS servers, an IPv4 address may be returned when an IPv6 address is requested. It is possible for Mozilla to recover from this misinformation, but a significant delay is introduced.
Type network.dns.disableIPv6 in the filter search bar and set this option to true by double clicking on it.

6. CONTENT INTERRUPT PARSING
This preference controls if the application will interrupt parsing a page to respond to UI events. It does not exist by default.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New and then Boolean from the pop-up menu.

A. Enter content.interrupt.parsing in the New boolean value pop-up window and click
B. When prompted to choose the value for the new boolean, select true and click OK.]

7. Rather than wait until a page has completely downloaded to display it to the user, Mozilla applications will regularly render what has been received to that point. This option controls the maximum amount of time the application will be unresponsive while rendering pages.

Right-click (Apple users ctrl-click) anywhere in the about:config window, select New and then Integer from the pop-up menu.

A. Enter content.max.tokenizing.time in the New integer value pop-up window and click OK
B. You will be prompted to enter a value. Enter 2250000 and click OK.

8. CONTENT NOTIFY INTERVAL
This option sets the minimum amount of time to wait between reflows. Right-click (Apple users ctrl-click) anywhere in the about:config window, select New and then Integer from the pop-up menu.

A. Type content.notify.interval in the New integer value pop-up window and click OK.

B. You will be prompted to enter a value. Enter 750000 and click OK.

9. CONTENT NOTIFY ONTIMER

A. This option sets if to reflow pages at an interval any higher than that specified by content.notify.interval. Right-click (Apple users ctrl-click) anywhere in the about:config window and select New and then Boolean from the pop-up menu.

B. Type content.notify.ontimer in the New boolean value pop-up window and click OK.

C. You will be prompted to choose the value for the new boolean. Select true and click OK.

10. Notify Backoffcount
This option controls the maximum number of times the content will do timer-based reflows. After this number has been reached, the page will only reflow once it is finished downloading. Right-click (Apple users ctrl-click) anywhere in the about:config window and select New and then Integer from the pop-up menu.

A. Enter content.notify.backoffcount in the New integer value pop-up window and click OK.

B. You will be prompted to enter a value. Enter 5 and click OK.

11. CONTENT SWITCH THRESHOLD
You can interact with a loading page when content.interrupt.parsing is set to true. When a page is loading, the application has two modes: a high frequency interrupt mode and a low frequency interrupt mode. The first one interrupts the parser more frequently to allow for greater UI responsiveness during page load.

The low frequency interrupt mode interrupts the parser less frequently to allow for quicker page load. The application enters high frequency interrupt mode when you move the mouse or type on the keyboard and switch back to low frequency mode when you had no activity for a certain amount of time. This preference controls that amount of time. Right-click (Apple users ctrl-click) anywhere in the about:config window and select New and then Integer from the pop-up menu.

A. Enter content.switch.threshold in the New integer value pop-up window and click OK.

B. You will be prompted to enter a value. Enter 750000 and click OK.


12. NGLAYOUT INITIALPAINT DELAY
Mozilla applications render web pages incrementally, they display what’s been received of a page before the entire page has been downloaded. Since the start of a web page normally doesn’t have much useful information to display, Mozilla applications will wait a short interval before first rendering a page. This preference controls that interval. Right-click (Apple users ctrl-click) anywhere in the about:config window and select New and then Integer from the pop-up menu.

A. Enter nglayout.initialpaint.delay in the New integer value pop-up window and click OK.

B. You will be prompted to enter a value. Enter 0 and click OK.



EDIT : Sorry ! for posting this here. I think it needs to be posted in the tutorial forum. As i am new to this forum i may do mistakes. so to the "Moderator" If you feel this is not the proper place then move it from here. But Plz don't give me "WARN"

 

 

 

Comment/Reply (w/o sign-up)

Hi, thanks for the tips very useful, but i make a mistake, how can i change the type of any preference, for example, changing a boolean value to an integer value???? or how can i delete any preference????

Best regards,

Comment/Reply (w/o sign-up)

Thank you for your extremely useful tutorial on speeding up Firefox. Before I read you tutorial/article, the only way I knew how to speed up Firefox was to use the Network.HTTP.Pipelining option to force the client to make more connections. However, I have observed that having too many max requests can have the opposite effect on the speed of Firefox, as it slows the load speed down considerably.

Comment/Reply (w/o sign-up)

Thanks for the tips. Good job. I had no knowledge of how to speed it up other than via the Processes Page. However I'm thinking of switching to Opera so its a little late

Comment/Reply (w/o sign-up)

The above procedure can be a little tedious, so Fasterfox is a neat little extension for Firefox that not only does the above settings, but also several other speed-improving tasks.

Get it here. On the subject of Opera, even though Opera is a pretty damn good browser (it's more compatible with the W3C standards than FF, in fact, not much, but still), I find the greatest strength of FireFox in it's extensions. I love extensions. My firefox is tweaked and tuned like there's no tomorrow.
Last I heard, Opera's variant called "widgets" were lacking seriously in comparison to FF.

 

 

 

Comment/Reply (w/o sign-up)

This is because Windows imposes a limit on Half-open (SYN'd but not yet ACK'd, or CONNECT_WAIT in netstat terms) connections so that Windows would look less attractive to botnet owners intent on DDoS attacks (though Micro$oft's official position on this was "it will slow the spread of network-vectored virii" or some bullshit, which is correct, though irrelevant since most virii use human stupidity to spread). Dumb move by Microsoft, screws up bittorrent alot...anyway, if you search google you can find a patcher that will remove this restriction by patching tcpip.sys.




Opera is the ****, but I still prefer firefox on my PC. I'm an extension ***** too...I can't browse at all without adblock plus (with easylist USA sub), noscript, and greasemonkey (and a handful of userscripts). As for Opera, you will never find a better browser for a WM5 Pocket PC...even Minimo (the PocketPC mozilla port) can't match Opera on that platform. Now, if Opera supported Firefox extensions, or was at least open-source so the support could be added by the OSS community, I'd switch in a heartbeat, but for now, Firefox works wonderfully.

Comment/Reply (w/o sign-up)