Here's the same on a lower device/network: https://www.webpagetest.org/result/200415_QM_aa8a7414b2f21babbdf4d0f945c831aa/ … It's a lot if script, but not enough to justify loading *that* slowly. The serialisation is what's really killing here.
Got it. So I think that suggests a more statistical approach is a better bet. What's actually choosing which components and resources to pull in here? Is it just letting the dynamic import()s run?
-
-
just running through the imports when things call window.WCAutoload.process(); bootup sets document level MutationObserver + does an initial https://github.com/elmsln/lrnwebcomponents/blob/master/elements/wc-autoload/wc-autoload.js#L37-L42 … querySelectorAll('*') - sanity check for webcomponents (-) and then if in wc-registry.json, import()
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.