3 ms·
I think that's a limitation of our implementations. In principle, it's just bytes that we shoving down the pipe to the browser, so it shouldn't matter for perf
by eru 2y ago
I think that's a limitation of our implementations. In principle, it's just bytes that we shoving down the pipe to the browser, so it shouldn't matter for performance whether those bytes are 'inline' or in 'external resources'.
In principle, you could imagine the server packing all the external resources that the browser will definitely ask for together, and just sending them together with the original website. But I'm not sure how much re-engineering that would be.
- erikerikson 2y agoIn principle there's no difference between principle and practice.
- eru 2y agoSimple models are still useful: understanding exactly how and why they fail is instructive. There's a reason spherical cows in a vacuum come up again and again.
- Perseids 2y agoThis feature actually existed (see https://en.wikipedia.org/wiki/HTTP/2_Server_Push https://en.wikipedia.org/wiki/HTTP/2_Server_Push ) but was deemed a failure unfortunately (see https://developer.chrome.com/blog/removing-push https://developer.chrome.com/blog/removing-push )
- eru 2y agoThanks for the links! Yes, my comment was based of a vague recollection of this kind of thing. I'll read up on the '103 early hints' and 'preload' and 'preconnect' which might be close in enough practice.