Faster content websites via SSR and progressive hydration of Web Components
summary
Claims that pages ship almost zero JavaScript by doing most work at build time and using server-rendered web components, then progressively hydrating only interactive parts. Implementation uses declarative Shadow DOM for SSR, lit SSR to emit HTML plus metadata, and a loader that hydrate-on-visible via frameworks like Astro or Rocket. Example site uses ~15 components, 2 KB main-thread JS baseline, becomes interactive in ~1.1 seconds on an older phone, and the approach yields much smaller client bundles.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 1:02Setting the scene
- 5:20The era of web components
- 15:03Addressing client-side issues
- 16:41SSR and Declarative Shadow DOM
- 22:24Hydration and islands
- 25:02Progressive hydration
- 27:29Looking beyond and conclusion
related talks
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript
13mReact Without JavaScript?
24mThe Good, The Bad, and The Web Components
25mThe first two seconds: Faster page loads with React
45mGive Me Back My Frontend!
24mSuperpowers of browser's Web API
01h 14mJust Do Less
22mBuilding faster content-driven sites