I think this is a bit optimistic; this is a fundamental flaw of SPAs. Every new component you add degrades perf. You are punished for being DRY. It's not any 1 thing, it's death by a thousand cuts. I don't think you can back-port perf into a fundamentally broken architecture.
-
-
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 …
-
This is modern React (16.8.6) and modern
@gatsbyjs, and it's *not OK*. - 2 more replies
New conversation -
-
-
I was looking at this showcase a while back... analysed the top 20 sites at the time: the average JS to become interactive was 323kb, the worst being https://impossiblefoods.com at 820kb, smallest was https://stateofjs.com/ at 144kb... for a website that didn’t need JS whatsoever.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.