My talk from this year's We Love Speed is on YouTube! 👇
In "Tight Mode: how browsers REALLY load web pages", I take a very deep/very nerdy dive into why browsers sometimes intentionally delay loading resources, why they all do it differently, and why they should *stop clowning around* 🤡
#webperf
In "Tight Mode: how browsers REALLY load web pages", I take a very deep/very nerdy dive into why browsers sometimes intentionally delay loading resources, why they all do it differently, and why they should *stop clowning around* 🤡
#webperf
Comments
https://x.com/csswizardry/status/1504106607721988102
Though preloads for images broke all that :-)
Now it's probably best to put a user-timing entry just after , which is pretty much when tight mode ends.
Note that this is only for HTTP/3. I also have some tests for HTTP/2 (which is still equally broken on some servers) but haven't made anything public for that yet.
Big thanks to @patmeenan.com in particular for all his help (and work!) on this.
I still need to update my blog post after we spoke a few months ago. 🫣
Three questions:
22:05 – The third style sheet in Safari does not trigger tight mode. Is this because it takes too long to load (at +5s), or because Safari imposes a limit on how many stylesheets can be in tight mode?
I don't think this is a special case due to stylesheets.
33:53 – Can we hire you to make some balloons at kids parties?
2. this was actually SO MUCH HARDER THAN IT LOOKS. I was practicing in my hotel room all night before... luckily I think @guaca.bsky.social has some skills here, so you can book us as a double act ;)