Hybrid rendering (static + server) in Astro - Performance & Optimization

Performance: Hybrid rendering (static + server)

MEDIUM IMPACT

This affects page load speed by balancing static content delivery and server-rendered dynamic content, improving initial load and interactivity.

Rendering a webpage with both static and dynamic content

Astro

Pre-render static parts at build time and fetch dynamic data on server only for needed parts.

export const prerender = true;

export async function getServerSideProps() {
  const dynamicData = await fetchDynamicData();
  return { props: { dynamicData } };
}

function Page({ dynamicData }) {
  return <div>
    <StaticHeader />
    <DynamicContent data={dynamicData} />
  </div>;
}

Static parts load instantly from CDN, dynamic parts load on demand, reducing server load and improving LCP.

📈 Performance GainFaster initial paint; reduces server CPU usage; improves LCP and INP metrics.

Rendering a webpage with both static and dynamic content

Astro

Render entire page on server for every request, including static parts.

export async function getServerSideProps() {
  const data = await fetchData();
  return { props: { data } };
}

function Page({ data }) {
  return <div>{data.content}</div>;
}

Server renders whole page on every request, causing slower load times and higher server load.

📉 Performance CostBlocks rendering until server responds; increases Time to First Byte (TTFB); higher CPU usage on server.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full server rendering every request	High (full DOM rebuild)	Multiple reflows per request	High paint cost due to full page update	[X] Bad
Hybrid static + server rendering	Low for static parts, moderate for dynamic parts	Single reflow for dynamic updates	Lower paint cost, faster visible content	[OK] Good

Rendering Pipeline

Static content is pre-built and served immediately, skipping server rendering on request. Dynamic content triggers server rendering only for changing parts, reducing full page reflows and delays.

→HTML Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckServer rendering stage for dynamic content

Core Web Vital Affected

LCP, INP

This affects page load speed by balancing static content delivery and server-rendered dynamic content, improving initial load and interactivity.

Optimization Tips

1Pre-render static content at build time to serve instantly.

2Render only dynamic parts on the server to reduce load and delay.

3Cache static output and minimize server rendering scope for best performance.

Performance Quiz - 3 Questions

What is the main performance benefit of hybrid rendering in Astro?

A Fetching all data on the client side after page load

B Serving static content instantly while dynamically rendering only changing parts

C Rendering the entire page on the client after loading

D Rendering everything on the server for every request

DevTools: Performance

How to check: Record page load and interaction; look for server response times and paint timings; check if static content appears immediately.

What to look for: Short Time to First Byte (TTFB), fast Largest Contentful Paint (LCP), and quick Interaction to Next Paint (INP) for dynamic parts.

Practice

1. What is the main benefit of using hybrid rendering in Astro?

easy

A. It only renders pages fully on the client side.

B. It combines fast static content with fresh server data.

C. It disables server-side rendering completely.

D. It requires no data fetching at all.

Solution

1. Step 1: Understand hybrid rendering purpose

   Hybrid rendering mixes static and server-rendered content to get the best of both worlds: speed and fresh data.

2. Step 2: Compare options

   Only 'It combines fast static content with fresh server data.' correctly describes this benefit. The other options misunderstand hybrid rendering.

3. Final Answer:

   It combines fast static content with fresh server data. -> Option B

4. Quick Check:

   Hybrid rendering = fast + fresh [OK]

Hint: Hybrid means mixing static speed with server freshness [OK]

Common Mistakes:

• Thinking hybrid disables server rendering
• Assuming hybrid is client-only rendering
• Believing hybrid needs no data fetching

2. Which Astro syntax correctly fetches data on the server side for hybrid rendering?

easy

A. fetch('https://api.example.com').then(data => setData(data))

B. const data = fetch('https://api.example.com')

C. ---
const data = await fetch('https://api.example.com')
---

D. useEffect(() => { fetch('https://api.example.com') })

Solution

1. Step 1: Identify Astro frontmatter usage

   Astro uses frontmatter (---) to run server-side code before rendering.

2. Step 2: Check options for server-side fetch

   --- const data = await fetch('https://api.example.com') --- uses frontmatter with await fetch, which is correct. The other options lack frontmatter or use client-side hooks.

3. Final Answer:

   ---\nconst data = await fetch('https://api.example.com')\n--- -> Option C

4. Quick Check:

   Server fetch = frontmatter + await [OK]

Hint: Use frontmatter (---) with await for server fetch [OK]

Common Mistakes:

• Omitting frontmatter for server code
• Using client hooks like useEffect in Astro
• Not awaiting fetch in server code

3. Given this Astro component code, what will be rendered?

---
const time = new Date().toLocaleTimeString();
---

  
    
Current Time:
    
{time}
  

medium

A. The time when the page was built (static time).

B. The current time updated every second.

C. An error because {time} is invalid syntax.

D. Nothing, because time is not defined.

Solution

1. Step 1: Understand Astro frontmatter timing

   Code inside frontmatter runs once at build or server render time, so time is fixed then.

2. Step 2: Check rendering behavior

   The rendered page shows the time captured during rendering, not live updates. So The time when the page was built (static time). is correct.

3. Final Answer:

   The time when the page was built (static time). -> Option A

4. Quick Check:

   Frontmatter time = fixed render time [OK]

Hint: Frontmatter runs once; time is static, not live [OK]

Common Mistakes:

• Thinking time updates live on client
• Confusing Astro syntax with React JSX
• Assuming {time} causes error

4. What is wrong with this Astro code snippet for hybrid rendering?

---
const data = fetch('https://api.example.com/data');
---
{data.json()}

medium

A. fetch is not awaited, so data is a Promise, causing an error.

B. Using fetch inside frontmatter is not allowed.

C. The <p> tag cannot contain JavaScript expressions.

D. data.json() returns a string, which cannot be rendered.

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise; without await, data is a Promise, not the response.

2. Step 2: Understand rendering error

   Calling data.json() on a Promise causes an error because data is not resolved yet.

3. Final Answer:

   fetch is not awaited, so data is a Promise, causing an error. -> Option A

4. Quick Check:

   Always await fetch in frontmatter [OK]

Hint: Always await fetch to get response, not Promise [OK]

Common Mistakes:

• Forgetting to await fetch
• Misunderstanding frontmatter fetch rules
• Thinking data.json() returns string directly

5. You want to build a blog page in Astro that shows static posts but also displays the current number of visitors fetched live from the server. Which approach best uses hybrid rendering?

hard

A. Render everything statically with no data fetching.

B. Fetch both posts and visitor count inside frontmatter only.

C. Fetch posts on client side with useEffect, visitor count in frontmatter.

D. Fetch posts in frontmatter for static build, then fetch visitor count inside a server component.

Solution

1. Step 1: Separate static and dynamic data

   Posts are mostly static, so fetching them in frontmatter for static build is efficient.

2. Step 2: Use server component for live data

   Visitor count changes often, so fetching it in a server component ensures fresh data on each request.

3. Step 3: Evaluate options

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. correctly mixes static and server rendering. The other options do not use hybrid rendering properly.

4. Final Answer:

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. -> Option D

5. Quick Check:

   Static + server fetch = hybrid rendering [OK]

Hint: Static data in frontmatter, dynamic in server component [OK]

Common Mistakes:

• Fetching all data statically losing freshness
• Fetching static data on client unnecessarily
• Not separating static and dynamic concerns