Enabling SSR in Astro - Performance & Optimization

Performance: Enabling SSR in Astro

HIGH IMPACT

Enabling SSR affects how quickly the main content appears by rendering HTML on the server before sending it to the browser.

Rendering page content quickly for better user experience

Astro

---astro.config.mjs---
export default {
  output: 'server'
};

---Page.astro---
---
const data = await fetchData();
---
<html>
  <body>
    <div>{data.content}</div>
  </body>
</html>

Rendering HTML on the server sends ready content to the browser, so users see meaningful content faster.

📈 Performance GainReduces LCP by 30-70% depending on network, avoids waiting for JS to render main content.

Rendering page content quickly for better user experience

Astro

export default function Page() {
  return (
    <div>
      <ClientOnlyComponent />
    </div>
  );
}

// ClientOnlyComponent fetches data and renders only on client side

Rendering content only on the client delays visible content until JavaScript loads and runs, causing slower LCP.

📉 Performance CostBlocks LCP until JS loads and executes, increasing time to interactive by 1-3 seconds on slow networks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Client-side only rendering	Many DOM nodes created after JS loads	Multiple reflows as content loads	High paint cost due to delayed content	[X] Bad
Server-side rendering (SSR)	DOM nodes created immediately from HTML	Single reflow on initial paint	Lower paint cost with immediate content	[OK] Good

Rendering Pipeline

With SSR enabled, the server generates full HTML before sending it to the browser. The browser can paint content immediately without waiting for JavaScript to run.

→HTML Generation

→Network Transfer

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork Transfer and HTML Generation on server

Core Web Vital Affected

LCP

Enabling SSR affects how quickly the main content appears by rendering HTML on the server before sending it to the browser.

Optimization Tips

1Enable SSR to send fully rendered HTML for faster initial content display.

2Avoid client-only rendering for main content to reduce LCP delays.

3Cache server responses to speed up HTML generation and delivery.

Performance Quiz - 3 Questions

How does enabling SSR in Astro mainly improve page load performance?

A By increasing JavaScript bundle size for faster parsing

B By delaying HTML rendering until all client scripts load

C By sending fully rendered HTML to the browser before JavaScript runs

D By removing CSS to speed up painting

DevTools: Performance

How to check: Record page load and look for Largest Contentful Paint (LCP) timing. Compare times with and without SSR enabled.

What to look for: Faster LCP and earlier content paint indicate good SSR performance.

Practice

1. What does adding export const ssr = true; in an Astro component do?

easy

A. Turns off all rendering for the component

B. Disables client-side JavaScript for the component

C. Makes the component load only on the client

D. Enables server-side rendering for that component

Solution

1. Step 1: Understand the purpose of ssr in Astro

   Setting export const ssr = true; tells Astro to render the component on the server before sending it to the browser.

2. Step 2: Compare with other options

   The other options describe disabling or client-only behavior, which is not what ssr = true does.

3. Final Answer:

   Enables server-side rendering for that component -> Option D

4. Quick Check:

   SSR enabled = export const ssr = true [OK]

Hint: Remember: ssr=true means server renders HTML first [OK]

Common Mistakes:

• Thinking ssr disables JavaScript
• Confusing SSR with client-only rendering
• Assuming ssr=true stops rendering

2. Which of the following is the correct way to enable SSR in an Astro component?

easy

A. export const ssr = true;

B. export const ssr = false;

C. const ssr = true;

D. enableSSR(true);

Solution

1. Step 1: Identify correct syntax for SSR in Astro

   The correct syntax is to export a constant named ssr with value true to enable SSR.

2. Step 2: Check each option

   export const ssr = false; disables SSR. const ssr = true; misses export. enableSSR(true); is not valid Astro syntax.

3. Final Answer:

   export const ssr = true; -> Option A

4. Quick Check:

   Correct SSR syntax = export const ssr = true [OK]

Hint: Look for 'export const ssr = true;' exactly [OK]

Common Mistakes:

• Forgetting to export the ssr constant
• Using a function call instead of export
• Setting ssr to false by mistake

3. Given this Astro component code:

---
export const ssr = true;
const time = new Date().toISOString();
---
Current time: {time}

What will the user see when they load this page?

medium

A. The current time when the page was requested (fresh time)

B. The current time when the page was built (static time)

C. An error because ssr cannot be true

D. No time displayed because SSR disables variables

Solution

1. Step 1: Understand SSR effect on data

   With ssr = true, the page is rendered on the server at request time, so new Date() runs fresh each request.

2. Step 2: Compare options

   The current time when the page was built (static time) is static build time (no SSR). An error because ssr cannot be true is false; SSR=true is valid. No time displayed because SSR disables variables is incorrect; SSR does not disable variables.

3. Final Answer:

   The current time when the page was requested (fresh time) -> Option A

4. Quick Check:

   SSR renders fresh data on each request [OK]

Hint: SSR runs code fresh on server per request [OK]

Common Mistakes:

• Thinking SSR uses build time data
• Assuming SSR disables JavaScript variables
• Confusing SSR with static site generation

4. You wrote this Astro component:

---
ssr = true;
---
Hello world

Why does this cause an error?

medium

A. Because ssr must be a function, not a variable

B. Because ssr cannot be set to true

C. Because ssr must be exported with export const

D. Because ssr must be set inside the HTML, not script

Solution

1. Step 1: Check correct SSR syntax

   SSR must be enabled by exporting a constant: export const ssr = true;. Just assigning ssr = true; is invalid.

2. Step 2: Analyze error cause

   Without export const, Astro does not recognize the SSR flag, causing an error.

3. Final Answer:

   Because ssr must be exported with export const -> Option C

4. Quick Check:

   SSR requires export const ssr = true [OK]

Hint: Always use 'export const ssr = true;' to enable SSR [OK]

Common Mistakes:

• Forgetting to export ssr
• Setting ssr without const
• Trying to set ssr inside HTML

5. You want to create an Astro page that shows a user's profile with fresh data on every request. Which approach correctly enables SSR and fetches fresh data?

---
// Fill in the missing code
---
User Profile
Name: {user.name}
Age: {user.age}

hard

A. const ssr = true;
const user = fetchUserFromAPI();

B. export const ssr = true;
const user = await fetchUserFromAPI();

C. export const ssr = false;
const user = await fetchUserFromAPI();

D. export const ssr = true;
const user = fetchUserFromAPI();

Solution

1. Step 1: Enable SSR correctly

   Use export const ssr = true; to enable server-side rendering so data is fresh on each request.

2. Step 2: Fetch data asynchronously

   Use await to fetch user data asynchronously before rendering the page.

3. Step 3: Analyze options

   export const ssr = false; const user = await fetchUserFromAPI(); disables SSR, so data won't be fresh. const ssr = true; const user = fetchUserFromAPI(); misses export and await. export const ssr = true; const user = fetchUserFromAPI(); misses await, so user is a Promise, causing error.

4. Final Answer:

   export const ssr = true; const user = await fetchUserFromAPI(); -> Option B

5. Quick Check:

   SSR + await fetch = fresh data per request [OK]

Hint: Use 'export const ssr = true;' and await data fetch [OK]

Common Mistakes:

• Not exporting ssr constant
• Forgetting to await async data fetch
• Disabling SSR by setting ssr to false