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.
Recent Bluessky Posts- Jotwell TechLaw: Stacy-Ann Elvy, Crossroads: Privacy Law and Copyright Law in the Age of Artificial Intelligence, JOTWELL (Feb. 9, 2026), cyber.jotwell.com/crossroads-p.... February 9, 2026 Jotwell
- I wrote about my grandmother's warning at Rose Burawoy, Political Scientist – www.discourse.net/2003/09/rose... Back in 2003, recalling it from years earlier, I was still dubious. That was then. February 9, 2026 Michael Froomkin
- US helping Russia in Ukraine comes to mind February 9, 2026 Michael Froomkin
- Today's efficiency: ignoring the super bowl and the winter Olympics at the same time. February 8, 2026 Michael Froomkin
- Deeply saddened to hear of the passing of Dave Farber. He was a true pioneer who had major influence on the architecture of the Internet and tech policy. Rest in peace to one of the most "Interesting People" our field has ever known. mailarchive.ietf.org/arch/msg/iet... February 8, 2026 Joseph Lorenzo Hall, PhD
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.