3 ms·
If it is a single HTML page with all CSS and important JS built in, I don't see how multiplexing will help the single page load faster.
by rebelde 10y ago
If it is a single HTML page with all CSS and important JS built in, I don't see how multiplexing will help the single page load faster.
- untog 10y agoThat would also be very inefficient if you have more than 1 page with common CSS/JS, though.
- pbhjpbhj 10y agoNot OP but IME it can be faster, setting up multiple HTTP connections can be the bottleneck, YMMV a lot. That's why connections are one aspect of pageload metrics. Some sites are such that they'll only get ~1.something page-views per client per day. See eg https://developer.yahoo.com/performance/rules.html#num_http= https://developer.yahoo.com/performance/rules.html#num_http=
- pbhjpbhj 10y agoCould you do HTTPS as default then offer to bump people to HTTP (and a slimmer site) if they want it? Do people with strong requirements for fast pages tend to use proxies that lighten the page (Opera used to have this built in) by reducing image sizes and such - presumably then it wouldn't matter if the original connection was HTTPS?? Would you mind sharing the site in question and the modal (ie most common) specs of your users devices?
- pixl97 10y ago> with all CSS and important JS built in If your page is anything over a few KB in size you are really messing up then. Break CSS and JS into separate files so the browser can cache them and doesn't have to ask for them every single time the page is reloaded.
- angry-hacker 10y agoOften times its better to write them all inline - - if they are small of course. At least with http. Http2 is different story.