When to hydrate vs keep static in Astro - Performance Comparison

Performance: When to hydrate vs keep static

HIGH IMPACT

This concept affects page load speed and interaction responsiveness by deciding when JavaScript activates on the page.

Rendering a mostly static page with a few interactive widgets

Astro

import MyWidget from './MyWidget.astro';
<MyWidget client:idle />

Delays hydration until browser is idle, allowing main content to paint faster and reducing input delay.

📈 Performance Gainimproves LCP by 20-40%, reduces JS execution blocking time

Rendering a mostly static page with a few interactive widgets

Astro

import MyWidget from './MyWidget.astro';
<MyWidget client:load />

Hydrating the entire widget immediately loads and runs JavaScript even if user doesn't interact, delaying main content paint.

📉 Performance Costblocks rendering for 100-200ms on slow devices, increases JS bundle size by 30kb

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Hydrate entire page immediately	High (many nodes hydrated)	Multiple reflows	High paint cost due to JS	[X] Bad
Hydrate interactive widgets on idle	Moderate (only widgets)	Single reflow	Lower paint cost	[OK] Good
Keep static content without hydration	Low (static DOM)	No reflows from JS	Minimal paint cost	[OK] Good

Rendering Pipeline

Hydration adds JavaScript execution after HTML is parsed, triggering style recalculations and layout updates. Static content skips this, allowing faster paint.

→HTML Parsing

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution and Layout

Core Web Vital Affected

LCP, INP

This concept affects page load speed and interaction responsiveness by deciding when JavaScript activates on the page.

Optimization Tips

1Hydrate only interactive parts of the page to reduce JavaScript execution.

2Keep non-interactive content static to speed up initial paint and reduce layout shifts.

3Use deferred hydration strategies like client:idle to improve user experience.

Performance Quiz - 3 Questions

What is the main performance benefit of keeping content static without hydration?

A More interactive features available immediately

B Larger JavaScript bundle size

C Faster initial paint and less JavaScript execution

D Triggers more layout recalculations

DevTools: Performance

How to check: Record a performance profile while loading the page. Look for long JavaScript execution blocks and layout shifts after initial paint.

What to look for: Long JS tasks delaying LCP indicate overhydration; minimal JS and stable layout indicate good static usage.

Practice

1. Which situation is best for keeping a component static in Astro?

easy

A. When the component only displays information and has no user interaction

B. When the component needs to update frequently based on user input

C. When the component requires real-time data fetching

D. When the component has buttons that trigger events

Solution

1. Step 1: Understand static components

   Static components do not need to respond to user actions or update dynamically.

2. Step 2: Identify when to keep static

   If a component only shows fixed information without interactivity, it should remain static for better performance.

3. Final Answer:

   When the component only displays information and has no user interaction -> Option A

4. Quick Check:

   Static = no interactivity [OK]

Hint: Static means no user interaction needed [OK]

Common Mistakes:

• Thinking all components must hydrate
• Hydrating components without user actions
• Confusing static with dynamic updates

2. Which Astro syntax correctly hydrates a component only on client load?

easy

A. <MyComponent />

B. <MyComponent client:idle />

C. <MyComponent client:visible />

D. <MyComponent client:load />

Solution

1. Step 1: Recall hydration directives

   Astro uses client:load to hydrate a component immediately after the page loads.

2. Step 2: Match syntax to behavior

   client:load hydrates on load, client:idle waits for idle, client:visible hydrates when visible, and no directive means no hydration.

3. Final Answer:

   <MyComponent client:load /> -> Option D

4. Quick Check:

   client:load = hydrate on load [OK]

Hint: client:load hydrates immediately after page load [OK]

Common Mistakes:

• Using client:idle when immediate hydration is needed
• Omitting hydration directive expecting auto hydration
• Confusing client:visible with client:load

3. Given this Astro component usage:

<Counter client:idle />

What happens when the page loads?

medium

A. The Counter component hydrates immediately and is interactive

B. The Counter component never hydrates and stays static

C. The Counter component hydrates only when the browser is idle

D. The Counter component hydrates only when visible on screen

Solution

1. Step 1: Understand client:idle behavior

   The client:idle directive delays hydration until the browser is idle, improving performance.

2. Step 2: Predict component behavior on load

   On page load, the component is static until the browser has free time, then it hydrates and becomes interactive.

3. Final Answer:

   The Counter component hydrates only when the browser is idle -> Option C

4. Quick Check:

   client:idle = hydrate on idle [OK]

Hint: client:idle waits for browser idle before hydrating [OK]

Common Mistakes:

• Assuming immediate hydration with client:idle
• Thinking client:idle means no hydration
• Confusing client:idle with client:visible

4. You wrote this Astro code:

<Button client:load>Click</Button>

But the button is not interactive. What is the likely problem?

medium

A. You forgot to import the Button component

B. You used client:load on a static HTML element

C. You did not export the Button component properly

D. You need to add client:visible instead of client:load

Solution

1. Step 1: Check hydration on static elements

   Hydration directives like client:load only work on Astro components, not plain HTML elements.

2. Step 2: Identify the problem in code

   Using client:load on a native HTML tag like <Button> (instead of a component) does nothing, so no interactivity.

3. Final Answer:

   You used client:load on a static HTML element -> Option B

4. Quick Check:

   Hydrate only Astro components, not plain HTML [OK]

Hint: Hydrate only Astro components, not HTML tags [OK]

Common Mistakes:

• Assuming hydration works on native HTML tags
• Not importing components correctly
• Confusing client:load with client:visible

5. You have a dashboard with a live chat and a static news feed. How should you hydrate these in Astro for best performance?

hard

A. Keep news feed static and hydrate chat with client:visible

B. Hydrate news feed with client:idle and chat static

C. Hydrate both chat and news feed immediately with client:load

D. Keep both static and add hydration later if needed

Solution

1. Step 1: Analyze component interactivity needs

   The live chat requires interactivity, so it needs hydration. The news feed is static content and does not need hydration.

2. Step 2: Choose hydration strategy for performance

   Hydrating chat with client:visible delays hydration until visible, improving load speed. Keeping news feed static avoids unnecessary hydration.

3. Final Answer:

   Keep news feed static and hydrate chat with client:visible -> Option A

4. Quick Check:

   Hydrate interactive only, keep static content static [OK]

Hint: Hydrate interactive parts only, keep static parts static [OK]

Common Mistakes:

• Hydrating static content unnecessarily
• Delaying hydration of interactive parts too long
• Hydrating everything immediately hurting performance