Dynamic routes with parameters in Astro - Performance & Optimization

Performance: Dynamic routes with parameters

MEDIUM IMPACT

This affects the page load speed and server response time by determining how routes are matched and content is generated dynamically.

Creating dynamic routes that accept parameters for content rendering

Astro

src/pages/[slug].astro
---
export async function getStaticPaths() {
  const res = await fetch('https://api.example.com/all-slugs');
  const slugs = await res.json();
  return slugs.map(slug => ({ params: { slug } }));
}

const { slug } = Astro.params;
const data = await fetch(`https://api.example.com/data/${slug}`);
const json = await data.json();
---
<html><body><h1>{json.title}</h1></body></html>

Pre-generating pages at build time avoids runtime data fetching, reducing server response time and improving load speed.

📈 Performance GainReduces blocking time to near zero on page load, improving LCP significantly

Creating dynamic routes that accept parameters for content rendering

Astro

src/pages/[slug].astro
---
const { slug } = Astro.params;
const data = await fetch(`https://api.example.com/data/${slug}`);
const json = await data.json();
---
<html><body><h1>{json.title}</h1></body></html>

Fetching data inside the page component on every request causes blocking server-side rendering and delays the first contentful paint.

📉 Performance CostBlocks rendering for 200-400ms depending on API response time

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Runtime data fetching in dynamic route	Minimal DOM nodes	0 reflows	Blocks paint until data arrives	[X] Bad
Static generation with pre-built dynamic routes	Minimal DOM nodes	0 reflows	Paints immediately with preloaded data	[OK] Good

Rendering Pipeline

Dynamic routes with parameters first match the URL pattern, then fetch or generate content based on parameters. This affects server-side rendering and client hydration.

→Server-side Rendering

→Data Fetching

→HTML Generation

→Client Hydration

⚠️ BottleneckData Fetching during server-side rendering is the most expensive stage.

Core Web Vital Affected

LCP

This affects the page load speed and server response time by determining how routes are matched and content is generated dynamically.

Optimization Tips

1Avoid runtime data fetching in dynamic routes to reduce server blocking.

2Use static generation with getStaticPaths for dynamic routes.

3Monitor server response times to optimize LCP for dynamic pages.

Performance Quiz - 3 Questions

What is the main performance drawback of fetching data at runtime in dynamic routes?

A It blocks server-side rendering and delays first contentful paint

B It increases the number of DOM nodes unnecessarily

C It causes excessive client-side JavaScript execution

D It reduces CSS selector efficiency

DevTools: Performance

How to check: Record a page load with a dynamic route parameter, then analyze the waterfall for server response and scripting blocking times.

What to look for: Look for long server response times and scripting blocking before first contentful paint indicating slow data fetching.

Practice

1. What does a filename like [id].astro represent in Astro?

easy

A. A dynamic route that captures the id parameter from the URL

B. A static page named literally [id]

C. A component that cannot receive parameters

D. A special Astro configuration file

Solution

1. Step 1: Understand dynamic route syntax

   In Astro, square brackets in filenames like [id].astro define a dynamic route parameter named id.

2. Step 2: Recognize the purpose of the parameter

   This parameter captures part of the URL, allowing the page to change based on the URL segment.

3. Final Answer:

   A dynamic route that captures the id parameter from the URL -> Option A

4. Quick Check:

   Dynamic route = filename with [param] [OK]

Hint: Look for square brackets in filename for dynamic parameters [OK]

Common Mistakes:

• Thinking [id].astro is a static file
• Confusing parameter with component name
• Assuming parameters are optional by default

2. Which is the correct way to access a dynamic route parameter named slug inside an Astro component?

easy

A. Astro.query.slug

B. Astro.route.slug

C. Astro.params.slug

D. Astro.props.slug

Solution

1. Step 1: Recall Astro parameter access

   Astro provides dynamic route parameters inside the component via Astro.params.

2. Step 2: Use the parameter name as key

   To get the value of slug, use Astro.params.slug.

3. Final Answer:

   Astro.params.slug -> Option C

4. Quick Check:

   Access params with Astro.params.[name] [OK]

Hint: Use Astro.params to get dynamic route values [OK]

Common Mistakes:

• Using Astro.route or Astro.query instead of Astro.params
• Trying to access parameters via props
• Forgetting to use the exact parameter name

3. Given a file named src/pages/blog/[post].astro with this code snippet:

---
const postId = Astro.params.post;
---
Post ID: {postId}

What will be rendered when visiting /blog/42?

medium

A. Post ID: 42

B. Post ID: post

C. Post ID:

D. 404 Not Found

Solution

1. Step 1: Identify dynamic parameter value

   The URL /blog/42 matches the dynamic route [post].astro, so Astro.params.post is '42'.

2. Step 2: Render the parameter in the template

   The component outputs <h1>Post ID: {postId}</h1>, so it shows Post ID: 42.

3. Final Answer:

   <h1>Post ID: 42</h1> -> Option A

4. Quick Check:

   URL segment fills param = rendered value [OK]

Hint: URL segment replaces [param] and shows in Astro.params [OK]

Common Mistakes:

• Expecting literal 'post' instead of parameter value
• Assuming empty or missing parameter
• Confusing 404 with dynamic route handling

4. You have a dynamic route file named [user].astro but when visiting /john you get a runtime error: Cannot read property 'user' of undefined. What is the likely cause?

medium

A. Astro.params is only available in server components

B. You forgot to use Astro.params.user and accessed Astro.params directly

C. Dynamic routes cannot have parameters named 'user'

D. The filename should be {user}.astro instead of [user].astro

Solution

1. Step 1: Understand the error message

   The error says Cannot read property 'user' of undefined, meaning Astro.params is undefined or not accessed properly.

2. Step 2: Check parameter access syntax

   Accessing Astro.params.user is correct. If code tries to access Astro.params.user but Astro.params is undefined, it means Astro.params was not used or imported correctly.

3. Final Answer:

   You forgot to use Astro.params.user and accessed Astro.params directly -> Option B

4. Quick Check:

   Always use Astro.params.[param] to avoid undefined errors [OK]

Hint: Always access parameters via Astro.params.[name] [OK]

Common Mistakes:

• Using curly braces instead of square brackets in filename
• Assuming Astro.params is always defined globally
• Misnaming the parameter in code

5. You want to create a nested dynamic route in Astro to handle URLs like /products/electronics/123. Which file structure and parameter access is correct?

hard

A. Create src/pages/products/[category]/id.astro and access with Astro.params.id

B. Create src/pages/products/[category-id].astro and access with Astro.params['category-id']

C. Create src/pages/products/category/id.astro and access with Astro.params.category and Astro.params.id

D. Create src/pages/products/[category]/[id].astro and access with Astro.params.category and Astro.params.id

Solution

1. Step 1: Understand nested dynamic routes

   To match URLs like /products/electronics/123, you need nested folders with dynamic parameters: [category] and [id].

2. Step 2: Correct file structure and parameter access

   The correct structure is src/pages/products/[category]/[id].astro. Inside, access parameters as Astro.params.category and Astro.params.id.

3. Final Answer:

   Create src/pages/products/[category]/[id].astro and access with Astro.params.category and Astro.params.id -> Option D

4. Quick Check:

   Nested folders with [param] = nested params [OK]

Hint: Use nested folders with [param] for multi-level dynamic routes [OK]

Common Mistakes:

• Combining multiple params in one filename incorrectly
• Using static folder names instead of dynamic
• Accessing parameters that don't exist in the route