When to hydrate vs keep static in Astro - When to Use Which

The Big Idea

Discover how to make your website lightning fast by smartly choosing when to add JavaScript!

The Scenario

Imagine building a website where every interactive button and form needs JavaScript to work. You try adding scripts manually to each part, but it quickly becomes a mess to manage and slows down your page.

The Problem

Manually adding JavaScript to every element means loading lots of code even when users don't need it. This makes pages slow to load and can confuse browsers, causing bugs and poor user experience.

The Solution

Astro lets you choose when to add JavaScript to your components: hydrate them only when needed for interactivity, or keep them static if they don't require scripts. This keeps pages fast and smooth.

Before vs After

✗ Before

Add scripts to every component regardless of need, causing slow load times.

✓ After

<Component client:load /> to hydrate only interactive parts, <Component /> to keep static parts without extra scripts.

What It Enables

This choice lets you build fast websites that only use JavaScript where it truly matters, improving speed and user experience.

Real Life Example

A blog page where static articles load instantly, and only the comment form hydrates JavaScript when a user wants to interact.

Key Takeaways

Manually adding JavaScript everywhere slows down pages.

Hydration means adding scripts only to interactive parts.

Keeping components static saves resources and speeds up loading.

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