Page 1 of 2
Make Firefox Faster!
Posted: Fri 29 Apr, 2005 19.30
by GJ Online
For all of us that use Firefox and have a internet connection faster than 256k here is how to make it faster.
_____________________________________
>> Open a new tab, by pressing "CTRL" + T
>> In the url bar type or copy and paste "aboutconfig" then Press "Go"
>> Then filter "network.http." This would make it easier to find what you are looking for.
>> I now want you to find and set "network.http.pipelining" to "true"
>> Set "network.http.proxy.pipelining" to "true"
>> Set "network.http.pipelining.maxrequests" to 30. That means that firefox will make up to 30 requests at one time.
>> Nearly done now, Right click select New >> Integer.
Name it "nglayout.initialpaint.delay" make sure it is set to "0" This makes Firefox act as soon as it gets the infomation.
_____________________________________
It should work now, It is 100% safe however if you mess about with the settings in there not instructed, It may not be safe.
Enjoy your new settings,
Greg 8)
Posted: Fri 29 Apr, 2005 19.34
by Chris
For all of us that use Firefox and have a internet connection faster than 256k here is how to make it faster.
_____________________________________
>> Open a new tab, by pressing "CTRL" + T
>> In the url bar type or copy and paste "aboutconfig" then Press "Go"
>> Then filter "network.http." This would make it easier to find what you are looking for.
>> I now want you to find and set "network.http.pipelining" to "true"
>> Set "network.http.proxy.pipelining" to "true"
>> Set "network.http.pipelining.maxrequests" to 300. That means that firefox will make up to 300 requests at one time.
>> Nearly done now, Right click select New >> Integer.
Name it "nglayout.initialpaint.delay" make sure it is set to "0" This makes Firefox act as soon as it gets the infomation.
_____________________________________
It should work now, It is 100% safe however if you mess about with the settings in there not instructed, It may not be safe.
Enjoy your new settings,
Greg
Do NOT put it to 300.
It can, and will floor some servers as they will have reached the maximum connection limit, and people won't be able to connect (most are set for 100 max connections).
Set it to something like 10 at most, as you will be doing no one any favours if you do set it at some stupidly high number.
The same can also be done for IE, but it is a bit more fiddly.
Posted: Fri 29 Apr, 2005 19.43
by Pete
Pipelining is a funny system that I turn on occasionally but at othertimes prefer it to be off. When it is on I always leave it at 4. Something like 300 is just plain rude in my opinion.
I'll be glad when they *finally* release 1.1 properly as the improvements in Gecko mean the speed differences in the downloading are outweighed by much faster rendering.
On the subject of browsers anyone tried Opera 8? I would but I can't be arsed.
Posted: Fri 29 Apr, 2005 19.49
by GJ Online
Edited!
Posted: Fri 29 Apr, 2005 19.54
by Pete
Name it "nglayout.initialpaint.delay" make sure it is set to "0" This makes Firefox act as soon as it gets the infomation.
That is the software equivalent of PFI funding. Although it starts rendering quicker it doesn't have enough information to take an educated guess at basic page layout. If you leave it as it is although it'll start later the eventual rendering will be quicker as it won't have to redraw the page as frequently.
Posted: Tue 03 May, 2005 10.13
by Neil Jones
Chris wrote:For all of us that use Firefox and have a internet connection faster than 256k here is how to make it faster.
*snip*
It should work now, It is 100% safe however if you mess about with the settings in there not instructed, It may not be safe.
Enjoy your new settings,
Greg
Do NOT put it to 300.
It can, and will floor some servers as they will have reached the maximum connection limit, and people won't be able to connect (most are set for 100 max connections).
Set it to something like 10 at most, as you will be doing no one any favours if you do set it at some stupidly high number.
The default is 4 IIRC, although for some reason I seem to have ended up with a value of 4 in aboutconfig and a value of 8 in user.js. Which one takes priority?
But yes, setting to 300 is quite selfish really, regardless of your connection speed. It might be 100% safe but doesn't mean you'll go anywhere any faster.
The same can also be done for IE, but it is a bit more fiddly.
This is done by delving in the registry and adding/altering the value for the number of connections the browser opens to a server, though I seem to have lost the specific key but it works along the same lines.
Posted: Tue 03 May, 2005 13.05
by Dr Lobster*
one thing i've found which really descreases the time it takes to display (on broadband) a page is to change these settings:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
MaxConnectionsPerServer REG_DWORD (Default 2)
Sets the number of simultaneous requests to a single HTTP 1.1 Server
Change to 10
MaxConnectionsPer1_0Server REG_DWORD (Default 4)
Sets the number of simultaneous requests to a single HTTP 1.0 Server
Change to 10
most pages appear instantly.
other hints to speed up browsing; i've blocked that stupid news ticker on the homepage to metropol, and i rarely see a banner advert anymore (my proxy software supports blocking of scripts, adverts, per site or globally)
Posted: Mon 09 May, 2005 16.27
by harshy
In Mozilla auto:config look for browser.turbo.enabled, set it to true
Posted: Mon 09 May, 2005 16.59
by Pete
turbo is just shoving mozilla permently in memory to make it seem less clunking that is already is
Posted: Tue 10 May, 2005 11.31
by harshy
seems to work faster on my machine after doing this so will keep it here.
Posted: Tue 10 May, 2005 13.10
by Pete
oh it'll certyainly make it faster. it's just the method it uses is the one everyone has a go at Adobe 7 for