If you only try one of these tips, try pipelining - either way, you will notice these changes.
Here's the source. (Works on FF, Mozilla, Camino, etc.)
Don't be lazy.
Pipelining is an experimental feature, designed to improve page-load
performance, that is unfortunately not well supported by some web servers
and proxies. To try it out, by using about:config
to set the following preferences:
- network.http.pipelining
- Set this to true, to enable pipelining.
- network.http.proxy.pipelining
- Set this to true, to enable pipelining to the proxy server.
- network.http.pipelining.maxrequests
- Set this to 8, to have a maximum of 8 pipelining requests at once. Possible values are from 1 to 8.
By default, Firefox doesn't try to render a web page for 250
milliseconds while it's waiting for data. If you use about:config
to add the Integer preference nglayout.initialpaint.delay, and
set the value to 0, Firefox immediately starts to display the
page, even without complete data. The drawback, especially on slower
machines, is that the total time to display the page will be longer.
this i'd expect from sprees, but not from u, mcshumbot...
ReplyDeleteyea..i'm totally lazy. good thing you're around to do it for me.
ReplyDeletenerdy!!
ReplyDelete... i tried it, maybe it's faster? i can't tell if it's actually faster or i just thiiink it's faster because i'm anticipating it
Uh, Crystal, that's not really helping me convince people to try this...
ReplyDeleteok ok, sorry
ReplyDeleteso i did an non-scientific experiment at work with my two work computers. all things being not equal (too many things factoring into it), i think it does speed up firefox! :)
washingtonpost.com load about the same speed. i think the firefox with the modifications loaded cnn.com slllightly faster than the normal firefox. youtube was the one page where the modified firefox actually finished waaay ahead of the regular firefox.
i don't think you can really take any results of my "experiment" seriously :P