GenerateStaticParams for static paths in NextJS - Performance & Optimization

Performance: GenerateStaticParams for static paths

MEDIUM IMPACT

This affects the build time and initial page load speed by pre-generating static pages for known paths.

Pre-generating static pages for dynamic routes

NextJS

export async function generateStaticParams() {
  const res = await fetch('https://api.example.com/popular-items');
  const data = await res.json();
  return data.map(item => ({ id: item.id.toString() }));
}

// Only generates static pages for popular items, reducing build time and bundle size.

Limits static generation to important paths, balancing build time and load speed.

📈 Performance GainBuild time reduced by 70-90% depending on dataset size; faster deploys and smaller output.

Pre-generating static pages for dynamic routes

NextJS

export async function generateStaticParams() {
  const res = await fetch('https://api.example.com/all-items');
  const data = await res.json();
  return data.map(item => ({ id: item.id.toString() }));
}

// This fetches all items including rarely visited ones, generating thousands of pages.

Generates too many static pages, causing long build times and large build output.

📉 Performance CostBuild time increases linearly with number of pages; can add minutes or hours for large datasets.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Generate all paths statically	N/A (build time cost)	N/A	N/A	[X] Bad for large datasets
Generate only popular paths statically	N/A	N/A	N/A	[OK] Good balance
No static generation, fully dynamic	N/A	N/A	N/A	[!] OK but slower initial load

Rendering Pipeline

During build, Next.js uses generateStaticParams to create static HTML for each path. This reduces server work at runtime and speeds up initial page load.

→Build Time

→Initial Load

→Cache Usage

⚠️ BottleneckBuild Time when generating many static pages

Core Web Vital Affected

LCP

This affects the build time and initial page load speed by pre-generating static pages for known paths.

Optimization Tips

1Generate static paths only for frequently visited or critical pages.

2Avoid generating thousands of static pages to keep build times manageable.

3Use incremental static regeneration or dynamic rendering for less common paths.

Performance Quiz - 3 Questions

What is the main performance benefit of using generateStaticParams in Next.js?

A It reduces JavaScript bundle size on the client

B It improves runtime API response times

C Pre-generating pages reduces server work and speeds up initial load

D It automatically caches API data on the client

DevTools: Network and Performance panels

How to check: Use Network panel to verify static pages are served from cache or CDN. Use Performance panel to measure initial load speed.

What to look for: Look for fast first contentful paint and no server delays on static pages.

Practice

1. What is the main purpose of generateStaticParams in Next.js?

easy

A. To tell Next.js which dynamic routes to pre-render at build time

B. To fetch data on every user request

C. To handle client-side navigation between pages

D. To define API routes in Next.js

Solution

1. Step 1: Understand the role of generateStaticParams

   This function is used to specify dynamic route parameters for static generation.

2. Step 2: Compare with other Next.js features

   Unlike client-side navigation or API routes, generateStaticParams runs at build time to pre-build pages.

3. Final Answer:

   To tell Next.js which dynamic routes to pre-render at build time -> Option A

4. Quick Check:

   generateStaticParams = pre-render dynamic routes [OK]

Hint: Remember: generateStaticParams runs at build time for static pages [OK]

Common Mistakes:

• Confusing generateStaticParams with client-side data fetching
• Thinking it runs on every request
• Mixing it up with API route definitions

2. Which of the following is the correct syntax for generateStaticParams in a Next.js dynamic route file?

easy

A. export function generateStaticParams() { return ['1', '2']; }

B. export async function generateStaticParams() { return [{ id: '1' }, { id: '2' }]; }

C. export async function getStaticPaths() { return [{ params: { id: '1' } }]; }

D. export default function generateStaticParams() { return { paths: ['1', '2'] }; }

Solution

1. Step 1: Recall the correct return format

   generateStaticParams returns an array of objects with route parameters as keys.

2. Step 2: Check syntax correctness

   export async function generateStaticParams() { return [{ id: '1' }, { id: '2' }]; } correctly exports an async function returning [{ id: '1' }, { id: '2' }]. Others have wrong return types or use getStaticPaths.

3. Final Answer:

   export async function generateStaticParams() { return [{ id: '1' }, { id: '2' }]; } -> Option B

4. Quick Check:

   Return array of param objects = export async function generateStaticParams() { return [{ id: '1' }, { id: '2' }]; } [OK]

Hint: generateStaticParams returns array of objects with params keys [OK]

Common Mistakes:

• Using getStaticPaths instead of generateStaticParams
• Returning array of strings instead of objects
• Not exporting the function properly

3. Given this generateStaticParams function, what static paths will Next.js generate?

export async function generateStaticParams() {
  return [
    { slug: 'home' },
    { slug: 'about' },
    { slug: 'contact' }
  ];
}

medium

A. /home, /about, /contact

B. /slug/home, /slug/about, /slug/contact

C. /, /about, /contact

D. /home, /about, /contact, /blog

Solution

1. Step 1: Understand the returned params

   The function returns an array with slug keys: 'home', 'about', 'contact'.

2. Step 2: Map params to URLs

   Next.js uses these slugs as dynamic route parts, so paths are /home, /about, /contact.

3. Final Answer:

   /home, /about, /contact -> Option A

4. Quick Check:

   Params slug values = generated paths [OK]

Hint: Params keys map directly to URL segments in static paths [OK]

Common Mistakes:

• Adding extra path segments like /slug/
• Assuming root path / is included automatically
• Including paths not returned by generateStaticParams

4. Identify the error in this generateStaticParams function:

export async function generateStaticParams() {
  return [
    { id: 1 },
    { id: 2 },
    { id: 3 }
  ]
}

medium

A. There is no error; this is correct syntax

B. The function must return an object, not an array

C. The function must be named getStaticPaths instead

D. The id values should be strings, not numbers

Solution

1. Step 1: Check parameter types

   Route parameters in Next.js must be strings because URLs are strings.

2. Step 2: Identify type mismatch

   Here, id values are numbers (1, 2, 3), which can cause build errors or unexpected behavior.

3. Final Answer:

   The id values should be strings, not numbers -> Option D

4. Quick Check:

   Route params must be strings [OK]

Hint: Always use strings for route parameters in generateStaticParams [OK]

Common Mistakes:

• Returning numbers instead of strings for params
• Confusing generateStaticParams with getStaticPaths
• Returning object instead of array

5. You want to statically generate blog post pages with slugs from an API. Which generateStaticParams implementation correctly fetches slugs and returns them for static generation?

async function fetchSlugs() {
  return ['post-1', 'post-2', 'post-3'];
}

Choose the correct code:

hard

A. export async function generateStaticParams() {
const slugs = await fetchSlugs();
return slugs;
}

B. export async function generateStaticParams() {
const slugs = await fetchSlugs();
return { paths: slugs };
}

C. export async function generateStaticParams() {
const slugs = await fetchSlugs();
return slugs.map(slug => ({ slug }));
}

D. export async function generateStaticParams() {
const slugs = await fetchSlugs();
return slugs.map(slug => ({ params: { slug } }));
}

Solution

1. Step 1: Understand expected return format

   generateStaticParams expects an array of objects with route params keys directly, e.g. [{ slug: 'post-1' }].

2. Step 2: Analyze each option

   export async function generateStaticParams() { const slugs = await fetchSlugs(); return slugs.map(slug => ({ slug })); } returns slugs mapped to objects with slug keys correctly. export async function generateStaticParams() { const slugs = await fetchSlugs(); return { paths: slugs }; } returns an object, not array. export async function generateStaticParams() { const slugs = await fetchSlugs(); return slugs; } returns array of strings, not objects. export async function generateStaticParams() { const slugs = await fetchSlugs(); return slugs.map(slug => ({ params: { slug } })); } adds extra params key, which is incorrect for generateStaticParams.

3. Final Answer:

   export async function generateStaticParams() { const slugs = await fetchSlugs(); return slugs.map(slug => ({ slug })); } -> Option C

4. Quick Check:

   Return array of param objects without extra nesting [OK]

Hint: Map slugs to objects with keys matching route params [OK]

Common Mistakes:

• Returning object with paths key instead of array
• Returning array of strings instead of objects
• Adding extra nesting like { params: { slug } }