Hydration, explained
Frameworks such as React can render a page to HTML on the server. The browser shows that quickly. It then downloads the JavaScript, runs the components again and connects click handlers.
The cost can be high. A page may look finished but not respond until hydration ends, and all that JavaScript has to run on the visitor's device. On slower phones this hurts responsiveness, measured by INP.
Several ideas aim to reduce this. Astro's islands hydrate only the interactive parts and leave the rest as plain HTML. React Server Components keep some components out of the browser.
You may also see hydration errors in a console. These happen when the server HTML and the first browser render do not match, for example with dates or random values.



