Y'all be running perf budget deficits like your stock is the global reserve currency.
-
-
Replying to @slightlylate
What would you personally feel comfortable using as the page level budget for a website in 2019? (mobile ofc) 100K gzipped? 50K gzipped?
1 reply 0 retweets 0 likes -
Replying to @jaihindhreddy
I'm not particularly fussed about the HTML itself; inlined content performs well (although I'm seeing some ridonkulous document sizes thanks to "SSR"). Without knowing more about the market and vertical, for external resources, I'd want to keep external resources under ~150K.
2 replies 0 retweets 4 likes -
Replying to @slightlylate @jaihindhreddy
Obviously, your budget goes down the more of that which is JS (vs, e.g., images). JS is much more expensive. I go into some detail here: https://infrequently.org/2017/10/can-you-afford-it-real-world-web-performance-budgets/ …
1 reply 1 retweet 1 like -
Replying to @slightlylate @jaihindhreddy
Alex Russell Retweeted Alex Russell
The post is a few years old, but the trends I've been warning about have only continued to play out (we aren't at smartphone saturation yet):https://twitter.com/slightlylate/status/1139684093602349056?s=20 …
Alex Russell added,
1 reply 0 retweets 0 likes -
Replying to @slightlylate @jaihindhreddy
Some big things have changed since I wrote the blog post; notably off-thread parse/compile for V8.
@addyosmani's essential "cost of JS" series is helpful in estimating: https://v8.dev/blog/cost-of-javascript-2019 …1 reply 0 retweets 2 likes -
The Alcatel 1X that Addy mentions there is both newer and *slower* than the Moto G4's I used to recommend. It's a consequence of the low-end getting lower, and that's the cross-pressure to engines getting better.
1 reply 0 retweets 0 likes -
See, e.g.: https://www.gsmarena.com/compare.php3?idPhone1=9086&idPhone2=8103 … Android Go phones mean Chrome is currently optimizing against a *2012* memory baseline (1GB).
1 reply 0 retweets 0 likes -
Replying to @slightlylate @addyosmani
Your talk actually opened my eyes. I used to think a revolution in battery tech will fix the problem, completely forgetting heat. We need a revolution in CPU and networking as well. Cutting down JS seems far more reasonable now
1 reply 0 retweets 0 likes
We've already had a revolution in CPU and networking; life is great for rich people! The thing is that revolutions do not spread evenly or tend to occur at the low-end.
-
-
Replying to @slightlylate @addyosmani
That too! I switched to a OnePlus from an Android GO, and can attest to the fact that spec sheets are mostly lies
0 replies 0 retweets 0 likesThanks. 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.