Hacker News new | ask | show | jobs
by sinuhe69 1037 days ago
Something I didn't find mentioning is increasing the number of parallel connections in Firefox. When I inspect the network and responses of FF, I often find connections were "blocked" (for several hundreds ms). Thus, increasing the number of persistent connections to a server will unblock those connections and allow the website to render much faster. Go to about:config and change:

network.http.max-persistent-connections-per-server

from the default value of 6 to 24 or 32.

Experimental results for a website: (time until finish loading)

No of Conns Prime Cache w/o Cache

6 (default) 25 s 257 s

12 21 s 212 s

18 18 s 190 s

24 15 s 147 s

4 comments

This setting is a classic in the "tweak Firefox" blog posts.

Increasing connection count will make HTTP 1.1 websites faster, but they'll also cause random rate limiting errors if you increase the value too much. How high you should set this value is up to you, but it's one of the first things you should reset when websites start acting weird in Firefox but not in other browsers.

This is good to know -- I primarily use FF and couldn't narrow down why my site was bugging out but running fine on other browsers. Glad its not a compatibility issue.
Some web servers might throttle or block you for opening too many parallel connections within a short time, so be careful not to overdo that...
The default in Chrome is 4 IIRC.
Woow. thanks. Will test ASAP