Progressive Rendering – how to make your app render sooner
summary
Claims that splitting server HTML into chunks with Node.js streams cuts Time To First Byte so users see content fast are backed by a real case: full render takes about 3.5 seconds while the 327 ms first byte arrives quickly and browser loads resources in parallel. Implementation uses HTTP chunked transfer encoding, microservice-scoped partial queries, and client placeholders (React style). Practical caveats: set status, headers and cookies before the first chunk; libraries to try include tailor and dust.js.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:31Some facts about me
- 1:22We're going to talk about
- 2:21Majority of Node.js apps nowadays
- 3:18What's wrong with that?
- 7:56Back in 1997
- 8:42Back in 2005
- 9:26Netscape 1.0
- 12:48Advantages
- 14:59Browser loads resources in parallel
- 16:12But it's not perfect
- 20:24Facebook uses placeholders
- 21:09Existing solutions
- 23:29Summary
related talks
23mProgressive Rendering: Improve Performance on Slower Networks
33mRendering on the Web: Performance Implications of Application Architecture
23mMastering Server-rendered Apps
52mSSR, SPAs and PWAs
42mBuilding quick apps in 2018
34mOptimizing Performance in Large-Scale React & Node.js Applications
46mFrom nothing to a video under 2 seconds
01h 03mSpeed up your Web Application