Waterfall
posts (3)
- The Layers of HTTP in the Browser: From fetch() to QUIC6/9
HTTP/1.1: Where Waterfalls and Bundling Came From
Bundling, sprite sheets and domain sharding were answers to the cost of many requests. Frontend architecture adapted itself to the limits of the protocol.
- Frontend Rendering: from server-side pages to hybrid rendering5/17
SSR returns: the server renders HTML again
The server renders the first view not to make the frontend disappear, but to make content exist earlier. The rest of the cost stays on the client.
- Frontend Rendering: from server-side pages to hybrid rendering4/17
The cost of shipping the application to the browser
Transfer size is the first cost, not the only one. What counts is the work the device must do before the application becomes usable.