100K of critical-path JS on first load, for a mobile site that has a broad audience, is about right. If you're taking 35-40K of that for your *view framework*, that's...a lot.
-
-
No caching sounds like broken browsers that can't special case the most common frameworks, and is the p90 a sequence of fully unrelated page views? The snapdragon thing is interesting, but seems similar: modern JS should be be able to lazy load 50KB fast (200ms?)
-
Modern frontend practice compiles frameworks into per-site bundles. Caching defeated even if we offered it! It's worse than that, but a deep topic w/ many nuances.
- 13 more replies
New conversation -
-
-
The device is likely to be from a few years earlier too; say the Galaxy J2: https://www.gsmarena.com/samsung_galaxy_j2-7357.php … 4 28nm (slow) cores & very little RAM. Tough target today.
-
Assuming 2 connections (which, again, is super optimistic), H/2, and not much else hitting the network as we load the site, we can transfer 600KiB, but if we have to wait on JS processing for the majority of the payload, we're down nearer to 200KiB.
- 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.