Firefox on steroids. Nothing the advanced user will not have done already, but a very nice step-by-step guide for the rest of the world.
-
A Personal Blog
by Michael Froomkin
Laurie Silvers & Mitchell Rubenstein Distinguished Professor of Law
University of Miami School of Law
My Publications | e-mail
-
Mostly Cloudy
73°F
-
Fri

77/67
-
Sat

76/56
-
Sun

72/58
-
Mostly Cloudy
73°F
-
Who Reads Discourse.net?
Readers describe themselves.
Please join in.
Unique Homepage Views:
Sitemeter count:
Feed 1
Feed 2
Recent Comments
- Just me: Is it really a private transaction when states like our own fair Florida require you to have auto insurance?...
- Vic: I don’t understand what it wants me to DO? Bail out the REST of faltering America like we did Chrysler?...
- Michael Froomkin: AFAIK, all the ones around here are fixed, well-signed, and thus to some extent avoidable; the...
- i-celebes: Great Commercials…!!!
- Just me: We already use them right here in S.Fla. The 878 and 874 have recently installed toll booths with no cash...

Their example of 30 for the number of max requests on pipelining is probably too high to do any good and it can be kind of mean to webservers. Also, although changing the paint delay can make it appear somewhat faster, it will probably slow down the total time to render a page, since it will have to do more total drawing. But, if you like it better that way, that’s fine too.
Under 30, what’s a good number, from the webserver side?
Mozilla itself seems to suggest 8. I’ve also seen comments that with 4 or 5 you get most of the benefits. The default setting with my version of Firefox is 4. It also appears that some websites don’t always load properly if you use pipelining. So although it makes it faster in a lot of cases, you have to beaware it can fail to work sometimes.