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- Fails to disprove the hypothesis they want to make us all unsafe. June 8, 2026 Michael Froomkin
- @dfroomkin.bsky.social and @amandaweiss.bsky.social got married! June 5, 2026 Michael Froomkin
- Jotwell Tax: Susan Morse, Jury Rights in Civil Tax Cases??, JOTWELL (June 5, 2026) (reviewing Steve R. Johnson, Jarkesy, the Seventh Amendment, and Tax Penalties, 79 U. Mia. L. Rev. 461 (2025)), tax.jotwell.com/jury-rights-.... June 5, 2026 Jotwell
- Jotwell Torts: Anita Bernstein, Male Supremacy as a Products Liability Defect, JOTWELL (June 4, 2026) (reviewing Melissa F. Wasserman, Products Liability in a World Designed for Men, 105 Tex. L. Rev. __ (forthcoming 2027)), torts.jotwell.com/male-suprema.... June 4, 2026 Jotwell
- May I suggest jotwell.com as a very partial substitute? June 4, 2026 Michael Froomkin
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.