Hydration attaches event listeners and client-side state to HTML rendered before JavaScript becomes active. It preserves SSR’s fast content display but creates an interaction gap: enhanced controls may look ready while clicks do nothing. section 5.2.1
The misleadingly ready button
A server-rendered page can display a button immediately, yet the button remains inactive until hydration finishes. Frustrated users may click repeatedly; when JavaScript takes over, multiple actions can fire. section 5.2.1
Hydration exposes the trade-off between fast content and usable interaction. Richer pages can accumulate longer hydration work, so fast rendering metrics alone do not guarantee responsive experiences. section 5.2.1
Table 5.1 Web rendering approaches
|
Rendering approach
|
Category
|
Waits for
|
Trade-offs
|
|
Server-Side Rendering
|
All-at-once
|
All data before sending HTML
|
Response blocked by server’s slowest data source
|
|
Client-Side Rendering
|
All-at-once
|
All JavaScript before rendering
|
User sees blank screen or loading indicator
|
|
Streaming SSR
|
Progressive
|
Nothing; sends chunks as ready
|
Added complexity
|
|
Islands
|
Progressive
|
Nothing; hydrates components independently
|
Architectural constraints
|
Compare hydration’s SSR context with client-side rendering, streaming SSR, and independently hydrated islands. section 5.2.1


