Progressive Hydration
What you'll learn: How to hydrate server-rendered components in priority order based on visibility and user interaction rather than all at once.
The Core Idea
When a server-rendered page loads, progressive hydration means intelligently deciding when to hydrate each component instead of hydrating everything immediately. You prioritize components that are visible or likely to be interacted with first, and defer hydration of less critical components until they're actually needed.
Think of it like opening a restaurant: you don't need to heat up every dish on the menu before opening the doors. Instead, you prepare popular items first and cook special requests only when someone orders them.
How It Works
With standard hydration, all components become interactive simultaneously after the JavaScript loads—even components "below the fold" or hidden in collapsed sections. Progressive hydration breaks this work into chunks:
- Above-the-fold content hydrates immediately (visible on page load)
- Below-the-fold components hydrate when scrolled into view
- Collapsed or hidden sections hydrate only when expanded
- Low-priority widgets hydrate during idle time or on user interaction
This approach significantly reduces the Time to Interactive (TTI) metric you learned about earlier, because critical interactive elements become functional faster while less important ones wait their turn.
Practical Benefits
Progressive hydration addresses the performance cost of hydration by spreading the JavaScript execution over time. Instead of blocking the main thread for several hundred milliseconds hydrating everything, you deliver interactivity incrementally—making your app feel faster even if the total work remains the same.
Key Takeaway: Progressive hydration improves perceived performance by prioritizing which components become interactive based on visibility and user needs, rather than hydrating everything at once.