Indeed, @gatsbyjs is in a perfect position to audit first-party JS at build time and provide better options. Resource budgets are something they can enforce like almost no blog tool before them because they're flattening everything.
...and yet...
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 …
-
-
...but nope, we're using
@gatsbyjs, so it dutifuly created multiple 100KiB+ (compressed) JS bundles. Despite full knowledge of the app state, it didn't treat the the 576KiB/3.1MiB main page bundle as a build error: https://revenuedata.doi.gov/component---src-pages-index-js-a39b8cce9d5b75c48a87.js … /cc@addyosmani -
This would have been a full second worse, but modern Chrome is effectively magic and moved two ~500ms parse tasks off to a background thread for the script: https://www.webpagetest.org/chrome/inspector-20190809/inspector.html?experiments=true&loadTimelineFromURL=/getTimeline.php?timeline=t:191017_J5_d438a3f9ef614a319b46a66ae936fb5b,r:2,c:0,s:1 …
- 3 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.