today's Adventures In Tracing reminded me of this: http://idlewords.com/talks/website_obesity.htm … If you can't get your JS under 500K w/ gzip, it's an emergency.
-
-
Replying to @slightlylate
The main thing about emergencies is they require emergency response. Stop the presses. Pull the alarm. Break the glass.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
When your JS resources are larger than 500K (gzipped), your buildbot should go red and your tree should close.
2 replies 1 retweet 7 likes -
Replying to @slightlylate
.
@Pinboard's point is salient "The problem with picking any particular size as a threshold is that it encourages us to define deviancy down"1 reply 0 retweets 0 likes -
Replying to @slightlylate
So let me be clear: you should never have 500K of JS transfer in a page (unless, maybe, it's a game...etc.). And that's not a "limit".
1 reply 0 retweets 2 likes -
Replying to @slightlylate
...but it is a bright line you can use to know that your reactor core has already begun to melt down and you'll probably have to eject it
1 reply 0 retweets 4 likes
500K of JS is ~2MB unzipped (depending, it's complicated). Any single script this big in your build _is an error_.
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.