The problem in that article has since been fixed (after existing for well over a year), I should have stated that in the tweet. There are likely more issues though, that's just one that jumped out to me at the time.
-
-
Being generous & testing on 4G: https://www.webpagetest.org/result/191017_J5_d438a3f9ef614a319b46a66ae936fb5b/ … Remember, this is govt, so 3p load should be light. My expectation for static site on this config is *easily* interactive in < 4s, and "good" is ~2s. Let's go to the tape: https://www.webpagetest.org/result/191017_J5_d438a3f9ef614a319b46a66ae936fb5b/2/details/#waterfall_view_step1 …
-
This could have easily painted at the 1.5s mark: https://www.webpagetest.org/video/compare.php?tests=191017_J5_d438a3f9ef614a319b46a66ae936fb5b-r%3A2-c%3A0&thumbSize=200&ival=100&end=full …
- 5 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wait, what's the 3.5MB of page-data.json?
-
That appears to be de-normalized JSON of all the data they eventually dump into a chart. But on it's own, it doesn't delay TTI because evaling even that much JSON shouldn't block main thread if you do it async with `await fetch(...).body.json()`
- 1 more reply
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.
Gatsby *really* needs to stop sending JS to the client by default. Not the first on-fire Gatsby site I've seen this week for similar reasons.
/cc