Those aren’t accessible, but cool rant.
ICYMI, I linked a trace of such a site in the post itself: https://www.webpagetest.org/result/180827_FR_7ca373cd8e9e200d531c63fa03a14809/ …
-
-
This is a fascinating contrast. Interestingly to me, about 60% of the difference in Start Render and 36% of the difference in TTI is due to http://vets.gov 's very slow TTFB. (Which is not to argue that it's not quite heavy on JS for a static site.)
- 1 more reply
New conversation -
-
-
if your point is "static sites don't need a bunch of JavaScript" I agree. However, had they used gatsby you'd get super fast server renders AND sw precaching for bad networks when you might need access to that info on the go. Maybe were in the "gets worse before better" phase.
-
Got a good Gatsby trace handy? But the background here is that font issues (the second-most frequent issue) are much easier to remediate. A bit of <link rel="preconnect"> here, some `display: optional` there. Mostly done and dusted.
- 1 more reply
New conversation -
-
-
And let's get straight on something: I'm focusing on 1p JS because it's the thing that's blocking interactivity of new sites more than anything else. Yes, fonts are often an issue. As are 3p scripts. But they don't matter until 1p JS is under control. Classic bottleneck.
- 13 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.