Rehydration For Client-Side Or Server-Side Rendering

Rehydration, or more simply ‘hydration,’ is a term that often comes up when we look at SPAs and server-side rendering. This process is used in single-page applications (SPAs) alongside server-side rendering, which allows for a quicker First Contentful Paint (FCP), and client-side content is “hydrated” for the Largest Contentful Paint (LCP). Progressive Rehydration ExplainedProgressive rehydration optimizes the rendering and interactivity of individual components, and involves both server-side rendering and client-side rendering (CSR) as pieces of a page are booted over time. Another form of rehydration, partial rehydration, allows for the selective hydration of JavaScript components – or, more specifically, ‘islands’ – without having to hydrate all components. The streaming server-side rendering ensures the necessary content is sent to search engines.