• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

speeding up firefox

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

voodoo do'er

Member
Joined
Sep 4, 2011
Location
Lives under a bridge
found this on another forum.

Code:
1. Type "about:config" into the address bar and hit enter. Scroll down and look for the following entries:

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"
Set "network.http.proxy.pipelining" to "true"

set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it recieves.


much faster for me.
 
Firefox is as fast as it is, as someone who have tried that stuff before, I can tell you that some servers may get pissed with too high pipelining, and the paint delay is there for not making window transitions choppy. If you want a faster firefox, I advise playing with hardware acceleration and smooth scrolling, and if you want you can go 64-bit FF, Waterfox.
 
Firefox is as fast as it is, as someone who have tried that stuff before, I can tell you that some servers may get pissed with too high pipelining, and the paint delay is there for not making window transitions choppy. If you want a faster firefox, I advise playing with hardware acceleration and smooth scrolling, and if you want you can go 64-bit FF, Waterfox.

what severs ?
not everyone uses windows. So Waterfox is not a sure fix for speed.
 
"network.http.pipelining" to "true"
"network.http.proxy.pipelining" to "true"

This also sped up Firefox for me when I had 56K!

This makes the browser more responsive on all types of internet services.

Using pipelining with the default amount of requests works like a charm with probably most servers.

Pipelining allows faster browsing without using more bandwidth of an ISP, thus a server shouldn't complain.

Opera has HTTP pipelining enabled by default, IIRC.
 
Last edited:
Firefox is as fast as it is, as someone who have tried that stuff before, I can tell you that some servers may get pissed with too high pipelining, and the paint delay is there for not making window transitions choppy. If you want a faster firefox, I advise playing with hardware acceleration and smooth scrolling, and if you want you can go 64-bit FF, Waterfox.


it is? last time i used FF it was bloated. i'm more partial to chrome right now :thup: even more so since they pushed out chromium for android.
 
it is? last time i used FF it was bloated. i'm more partial to chrome right now :thup: even more so since they pushed out chromium for android.

I find chrome bloated and kinda spying on me these days. I don't trust it's incognito at all. Only chrome I'd use is chromium on linux. That thing is less glitchy and fast like the old days:p

Firefox handles lots of tabs and flash content wonderfully tho. Chrome is crashfest.
 
Back