PDA

View Full Version : Speed Up Firefox


Guy
08-27-200727th August 2007, 06:11 AM
I found this in a computer forum that I frequent and quite a few people posted that it made a considerable difference so I decided to gave it a whirl. It seems to me that it worked so I'm posting it here.

To make things simple for myself I opened up two sessions of Firefox and just " copied and pasted " his commands / strings where instructed. I also printed his instructions out and checked them off as I went. I'm getting older by the minute and my short term memory is................. what a wonderful sunny day it's going to be. To bad I have to work.

In any event here it is............

Tips & Tricks that can help you to double the speed of Firefox.

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. HTTP is the application-layer protocol that most web pages are transferred with. In HTTP 1.1, multiple requests can be sent before any responses are received. This is known as pipelining. Pipelining reduces page loading times, but not all servers support it.

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 doubleclick 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. Then:
A. Enter content.interrupt.parsing in the New boolean value pop-up window and click OK
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 2333333 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 849999 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 849999 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. Rightclick (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.

Jeff JTPhoto
08-28-200728th August 2007, 01:58 PM
Thanks Guy.. Pretty noticeable increase in speed on my dial-up connection..

Guy
08-29-200729th August 2007, 03:21 AM
Thanks Guy.. Pretty noticeable increase in speed on my dial-up connection..

Jeff I'm glad you noticed the difference. I have high speed and I have seen the difference as well.

If others try it and post their comments maybe more will take the plunge. I know many people are afraid to try new things until they hear numerous positive things about it. In this case I had no reservations because it comes from a very good site I have been a member at for a few years. The tech that posted it is rock solid as well.

EV Wonder
08-29-200729th August 2007, 01:47 PM
Hello Guy, and thanks for posting the info on speeding up Firefox.

I used your easy to follow instructions and applied the necessary changes. I currently have high-speed internet, and I can't say that I noticed any real difference. Perhaps it's to soon to tell and I'll have to do a little more surfing to determine a real difference. We'll see....but I'll be sure to re-post should I notice a significant change.

Thanks again! It's helps like this that can be of real use. Seems to have worked for Jeff on his dialup...and that's good news!

EV Wonder
08-30-200730th August 2007, 10:07 PM
I have surfed a good many hours today and I now have to say that I did notice a difference after all. Though not a substantial increase in speed it was at least noticeable, and that's a good thing. Thanks again, Guy.

Guy
08-31-200731st August 2007, 07:54 AM
Thanks again, Guy.

My pleasure......... and I'm glad it worked for you.

The more I use it the more speed I see depending which sites I visit and at what time of day I'm on. Some sites / pages are blaze fast, some a bit quicker and some no change at all. I know none have slowed down and even though I don't quite understand all the technical issues who cares really.....overall I'm quite pleased with the results especially since it doesn't cost any money unlike that 70 - 200 f2.8 I have to re buy to get more speed.

If I see anything worth passing on I'll be sure to do it.

MichiganMan
09-03-20073rd September 2007, 09:15 AM
Just to note...

Using "network.http.pipelining" only has an effect if you are NOT using a Proxy Server to connect to the Internet. Also, setting it to True "may" actually break some sites, so if you run across one that "used" to work, this might be why it doesn't anymore.

Also "network.http.keep-alive" needs to be set to True, which is the default, and "network.http.version" needs to be set to 1.1, which is probably the default for the pipelining to work.

Using "network.http.proxy.pipelining" only has an effect if you are using a Proxy Server to connect to the Internet. So changing the default may have no effect for you.

And like above, "network.http.proxy.keep-alive" needs to be set to True, which is the default, and "network.http.proxy.version" needs to be set to 1.1, which is probably the default for the pipelining to work.

Setting "network.dns.disableIPv6" to True really has no speed-up effect. It is primarily there because of bugs in the Mac OS-X and in OS/2. If you don't use those, the default is False.

E.B. West
09-06-20076th September 2007, 10:48 AM
Well, I'm not sure what I did wrong, but every time I used Firefox after going through the changes, it crashed the computer. It seemed to be putting some corrupted files somewhere. I kept getting a blue screen that something was corrupted, then it wouldn't start at all, not even in safe mode. I had to uninstall Firefox AND delete the directory before a fresh installation would work.

I'm sure it was Firefox doing it because I haven't had any problems since the re-install.

Guy
09-06-20076th September 2007, 11:22 AM
Well, I'm not sure what I did wrong, but every time I used Firefox after going through the changes, it crashed the computer. It seemed to be putting some corrupted files somewhere. I kept getting a blue screen that something was corrupted, then it wouldn't start at all, not even in safe mode. I had to uninstall Firefox AND delete the directory before a fresh installation would work.

I'm sure it was Firefox doing it because I haven't had any problems since the re-install.

You are the first person I have see from this or the other site that has had problems so I would agree that you may have done something wrong. Matter of fact I haven't seen any negative comments at all until now. The large majority of folks say they notice a difference and a few said the didn't see any difference.

E.B. West
09-10-200710th September 2007, 05:02 PM
You are the first person I have see from this or the other site that has had problems so I would agree that you may have done something wrong. Matter of fact I haven't seen any negative comments at all until now. The large majority of folks say they notice a difference and a few said the didn't see any difference.


I'm always the one.:arghh: