The Post Jamstack World & the Rise of Hybrid Frameworks
summary
Argues that the static Jamstack alone can’t fix global mobile performance and shows concrete fixes: USA Today goes from roughly 45 seconds to 3 seconds after removing heavy JS, first paint often sits around 14,000 ms, and cheap phones like the Xiaomi Redmi 8 expose the gap. Recommends hybrid frameworks (Next.js, SvelteKit), server/edge rendering for dynamic pages, Next’s image component to shrink delivered images, and continuous measurement via a Real Experience Score on Vercel to find and fix real-user bottlenecks.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:36The web is in jeopardy
- 3:01What is the web
- 7:46Traffic distribution
- 10:52Whats the difference
- 14:26Performance
- 18:35The Solution
- 22:11Real Experience Score
- 24:12Conclusion
related talks
31mThe post-Jamstack world and the rise of Hybrid Frameworks
42mTo Truly Understand Jamstack, Forget the JAM
50mComposable decoupled frontends: the Jamstack and beyond
30mRise of the Jamstack — Mathias Biilmann
19mA Skeptic’s Intro To The Jamstack
56mJAMstack
16mNeed for Speed: How Modern JavaScript Frameworks Are Solving Web Performance
44mJAMstack: Web Apps at Ludicrous Speed
