Mastodon Feed
slightlyoff@toot.cafe ("Alex Russell") wrote:
The timelines have been obscured to protect the guilty.
Needless to say, this is not working from a CWV perspective.
Attachments:
- "0 days since last 600+KB critical-path JS Disaster via React + Next.js" (remote)
- pixelated waterfall showing a cloud vendor's landing page, pulling in 600+KB (wire, 2.2MB unzipped) of critical path JS which then camps out on the main thread for *4 seconds* before putting up an LCP frame on an emulated slow Android. (remote)
