2 ms·
The amusing thing is that HTTP/2 is mostly useful for sites that download vast numbers of tiny Javascript files for no really good reason. Like Google's sites.
by Animats 2y ago
The amusing thing is that HTTP/2 is mostly useful for sites that download vast numbers of tiny Javascript files for no really good reason. Like Google's sites.
- paulddraper 2y agoOr small icon/image files. Anyone remember those sprite files?
- cyberpunk 2y agoYou ever had to host map tiles? Those are the worst!
- SahAssar 2y agoIndeed, there is a reason most mapping libraries still support specifying multiple domains for tiles. It used to be common practice to setup a.tileserver.test, b.tileserver.test, c.tileserver.test even if they all pointed to the same IP/server just to get around the concurrent request limit in browsers.
- theandrewbailey 2y agoI've seen noticeable, meaningful speed improvements with HTTP/2 on pages with only 1 Javascript file. But I'd like to introduce you/them to tight mode: https://docs.google.com/document/d/1bCDuq9H1ih9iNjgzyAL0gpwNFiEP4TZS-YLRp_RuMlc https://docs.google.com/document/d/1bCDuq9H1ih9iNjgzyAL0gpwN... https://www.smashingmagazine.com/2025/01/tight-mode-why-browsers-produce-different-performance-results/ https://www.smashingmagazine.com/2025/01/tight-mode-why-brow...
- youngtaff 2y agoThat’s not quite true… lots of small files still have the overhead of IPC in the browser