I'd have thought critical data would be H/2 pushed or at least `<link rel="preload">`-ed to get the parser working for you and prevent device speed from being a factor in getting that request out to the network.
Presumably the same ~400K/1.3MB (zipped/unzipped) is loaded/run on the server. That processing blocks getting content to the user while it thinks, and then delays interactivity until the ~13s mark when the code hits the client. This is a static page: https://www.webpagetest.org/video/compare.php?tests=180913_4A_97fde1f7c6cfc56657089645bed79860-r%3A1-c%3A0&thumbSize=200&ival=100&end=visual …
-
-
It's a good thing browsers implement threaded scrolling, else *nothing* would work in those 5 seconds of red.
-
I don't mean to harp on this to make Fastboot look bad. It's got exactly the same problems as most of the React SSR solutions I've seen deployed. This isn't unique.
- 9 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.