Understanding Resumability
summary
Claim: slow startup comes from how JavaScript is delivered, not feature bloat; downloads can block interactivity up to 30 seconds on bad mobile networks and every 100ms faster raises conversions. Measured a real site at 36/100 via Google PageSpeed API and a top-50 e‑commerce sweep where deleting JS gave the biggest gains. Built tooling: a Performance Insights analyzer, a resumable framework prototype called Quick that serializes listeners into HTML to skip hydration, and Party Town to move third‑party scripts into a web worker; resumability and progressive streaming together reduce time‑to‑interactive.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05JavaScript delivery issues
- 3:53JavaScript growth reasons
- 7:40Framework efficiency comparison
- 9:24Server-side rendering evolution
- 11:56Introducing resumable frameworks
- 13:19What is resumability
- 15:46Progressive frameworks and streaming
- 17:30Startup vs app performance
- 19:37Front-end CAP theorem
- 20:40Builder.io’s tools
related talks
21mWhy are web applications slow, and what to do about it
48mResumability in the next generation frontend framework With O(1) loading time
33mResumable JavaScript from Scratch
01h 03mSpeed up your Web Application
22mPerformance Empathy
31mSpeeding up Startup for Large React Apps
35mHydration, Islands, Streaming, Resumability... Me, Oh My!
20mQwik