> But it doesn't work like this in practice! There is a limit to the number of concurrent connections a browser will make, Chrome for example is <=10 IIRC. You

> But it doesn't work like this in practice! There is a limit to the number of concurrent connections a browser will make, Chrome for example is <=10 IIRC. You can see this in the waterfall: In HTTP/2, which our site will switch to soon, the concurrent limit is 100. The world's changed, change with it, and throw away those bundlers. Either way, you can compare to our direct competitors: https://diep.io https://diep.io https://arras.io https://arras.io > Finally, why on earth are you redirecting to HTTP after serving an HTTPS response? This isn't really related to the argument at hand. My app is currently on HTTP for reasons downstream.