Why Astro excels at performance - Performance Evidence

Performance: Why Astro excels at performance

CRITICAL IMPACT

Astro improves page load speed and interaction responsiveness by sending less JavaScript to the browser and rendering mostly static HTML.

Building a fast website with minimal JavaScript

Astro

---
const message = 'Hello';
---
<html><body><h1>{message}</h1></body></html>

Renders static HTML at build time with zero client JavaScript by default.

📈 Performance Gainsaves 100-200kb, faster LCP, non-blocking rendering

Building a fast website with minimal JavaScript

Astro

<script type="module">import React from 'react'; export default function App() { return <div>Hello</div>; }</script>
<script type="module">import ReactDOM from 'react-dom'; ReactDOM.render(<App />, document.getElementById('root'));</script>

Loads full React runtime and JavaScript on the client even if the page is mostly static.

📉 Performance Costadds 100-200kb to bundle, blocks rendering until JS loads

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full client-side React app	Many nodes created dynamically	Multiple reflows during hydration	High paint cost due to JS-driven updates	[X] Bad
Astro static HTML with partial hydration	Static DOM nodes from server	Single reflow on initial load	Low paint cost, minimal JS	[OK] Good

Rendering Pipeline

Astro pre-renders HTML during build, so the browser receives ready-to-display content. JavaScript is only loaded if needed, reducing style calculation, layout, and paint delays.

→HTML Parsing

→Style Calculation

→Layout

→Paint

→JavaScript Execution

⚠️ BottleneckJavaScript Execution when client JS is large

Core Web Vital Affected

LCP, INP

Astro improves page load speed and interaction responsiveness by sending less JavaScript to the browser and rendering mostly static HTML.

Optimization Tips

1Pre-render static HTML to reduce JavaScript sent to the browser.

2Use partial hydration to load JS only for interactive components.

3Minimize client-side JavaScript to improve Largest Contentful Paint.

Performance Quiz - 3 Questions

How does Astro reduce the amount of JavaScript sent to the browser?

A By running all JavaScript on the server at runtime

B By pre-rendering static HTML and only loading JS when needed

C By bundling all JavaScript into one large file

D By using inline styles instead of CSS files

DevTools: Performance

How to check: Record page load and interaction in DevTools Performance panel; look for long scripting tasks and layout shifts.

What to look for: Short scripting times, minimal layout shifts, and fast time to first contentful paint indicate good Astro performance.

Practice

1. Why does Astro send less code to the browser compared to other frameworks?

easy

A. Because it uses server-side rendering only without any client code

B. Because it compiles code into a single large JavaScript file

C. Because it only sends the HTML and CSS needed, not all JavaScript by default

D. Because it disables CSS to reduce code size

Solution

1. Step 1: Understand Astro's code sending strategy

   Astro sends only the HTML and CSS needed for the page, avoiding unnecessary JavaScript by default.

2. Step 2: Compare with other options

   Other frameworks often send all JavaScript upfront or disable CSS, which is not true for Astro.

3. Final Answer:

   Because it only sends the HTML and CSS needed, not all JavaScript by default -> Option C

4. Quick Check:

   Less code sent = only needed HTML/CSS sent [OK]

Hint: Astro sends minimal code by default, mainly HTML and CSS [OK]

Common Mistakes:

• Thinking Astro sends all JavaScript upfront
• Believing Astro disables CSS to reduce size
• Confusing Astro with frameworks that bundle all code

2. Which of the following is the correct way to load JavaScript only when needed in Astro?

easy

A. ...

B.

C.

D. ...

Solution

1. Step 1: Identify Astro's client directives

   Astro uses client directives like client:load or client:visible to load JavaScript only when needed.

2. Step 2: Match correct syntax

   <MyComponent client:visible>...</MyComponent> is the correct way to load JS when the component becomes visible.

3. Final Answer:

   <MyComponent client:visible>...</MyComponent> -> Option A

4. Quick Check:

   Use client directives to load JS only when needed [OK]

Hint: Look for components with client:visible directive to defer JS [OK]

Common Mistakes:

• Using plain <script> tags without defer or client directives
• Confusing import inside <script> as lazy loading
• Using client:always which loads JS immediately

3. Given this Astro component snippet:

<MyWidget client:idle />

What happens to the JavaScript for MyWidget?

medium

A. It loads only when the browser is idle

B. It loads immediately when the page loads

C. It never loads, only HTML is sent

D. It loads only when the user clicks the widget

Solution

1. Step 1: Understand client:idle directive

   The client:idle directive tells Astro to load the JavaScript when the browser is idle, not immediately.

2. Step 2: Compare other options

   Loading immediately is client:load, never loading is incorrect, and loading on click is client:click.

3. Final Answer:

   It loads only when the browser is idle -> Option A

4. Quick Check:

   client:idle means load JS when browser is idle [OK]

Hint: client:idle defers JS until browser is free [OK]

Common Mistakes:

• Assuming client:idle loads JS immediately
• Confusing client:idle with client:click
• Thinking JS never loads with client:idle

4. You wrote this Astro code:

<MyComponent client:load />

But the JavaScript never loads on the client. What is the likely problem?

medium

A. Astro does not support client-side JavaScript

B. client:load is not a valid directive in Astro

C. You need to add defer attribute to the script tag

D. You forgot to import MyComponent in the Astro file

Solution

1. Step 1: Check if MyComponent is imported

   Astro requires components to be imported before usage; missing import means no JS bundle is generated.

2. Step 2: Validate client:load directive

   client:load is a valid directive, so the issue is not the directive itself.

3. Final Answer:

   You forgot to import MyComponent in the Astro file -> Option D

4. Quick Check:

   Missing import means JS won't load [OK]

Hint: Always import components before using client directives [OK]

Common Mistakes:

• Thinking client:load is invalid
• Assuming Astro disables client JS
• Adding defer attribute manually instead of using directives

5. You want to build a blog with Astro that loads JavaScript only for interactive widgets when visible, and sends static HTML for the rest. Which approach best achieves this?

hard

A. Use <script> tags with defer for all widgets

B. Use <MyWidget client:visible /> for widgets and normal Astro components for static content

C. Disable JavaScript globally and use only server rendering

D. Wrap all components in <AstroIsland client:load> to load JS immediately

Solution

1. Step 1: Identify how to load JS only when widgets are visible

   The client:visible directive loads JavaScript only when the widget scrolls into view, saving resources.

2. Step 2: Use normal Astro components for static content

   Static content can be rendered as plain HTML without JavaScript, improving performance.

3. Final Answer:

   Use <MyWidget client:visible /> for widgets and normal Astro components for static content -> Option B

4. Quick Check:

   client:visible loads JS on visibility, static content stays HTML [OK]

Hint: Use client:visible for widgets, normal components for static parts [OK]

Common Mistakes:

• Loading all JS immediately wastes resources
• Disabling JS globally breaks interactivity
• Using plain <script> tags misses Astro's lazy loading