Great question. I aim to keep my full app under 100k, but ¯\_(ツ)_/¯ /cc @slightlylate @aerotwist @paul_irish https://twitter.com/nolanlawson/status/741669284699463680 …
-
This Tweet is unavailable.
-
Replying to @owencm
: if you have 100k of gzipped JS in your critical path, your users are gonna have a bad time /cc
@aerotwist@paul_irish@nolanlawson1 reply 0 retweets 5 likes -
Replying to @slightlylate @owencm and
+1. Critical path is the operating word here. Modularize & lazy load!
1 reply 0 retweets 0 likes -
Replying to @DasSurma @slightlylate and
14kb first render/critical path + remaining Async is wat I would aim for
1 reply 0 retweets 0 likes -
Replying to @_vigneshh @DasSurma and
: first paint isn't particularly useful. We want *interactive* UI quickly
3 replies 0 retweets 4 likes -
Replying to @slightlylate
For a content-heavy site, time to 1st meaningful paint/content is still valuable, right? TTFI is what I tend to look at next.
3 replies 0 retweets 3 likes -
Replying to @addyosmani @slightlylate
A kind msg + some sort of loading indicator would make one wait a sec more for interactivity than a blank screen.
1 reply 0 retweets 0 likes
: that's an empirical question and one I'm gathering data on now. Hopefully will have a model to share soon.
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.