Revalidation patterns in NextJS - Performance & Optimization

Performance: Revalidation patterns

MEDIUM IMPACT

This affects how quickly updated content appears on the page and how often the server regenerates pages, impacting load speed and server response.

Updating static pages with fresh data in Next.js

NextJS

export async function getStaticProps() {
  const data = await fetch('https://api.example.com/data');
  return {
    props: { data },
    revalidate: 60 // revalidates every 60 seconds
  };
}

Less frequent revalidation reduces server load and speeds up response, improving LCP.

📈 Performance GainReduces server regenerations by 60x, lowering CPU use and improving load speed.

Updating static pages with fresh data in Next.js

NextJS

export async function getStaticProps() {
  const data = await fetch('https://api.example.com/data');
  return {
    props: { data },
    revalidate: 1 // revalidates every 1 second
  };
}

Revalidating every second causes frequent server regeneration, increasing server load and slowing response times.

📉 Performance CostTriggers server regeneration on nearly every request, increasing server CPU and delaying LCP.

Performance Comparison

Pattern	Server Regenerations	Network Delay	LCP Impact	Verdict
Revalidate every 1 second	High (every request)	High	High delay	[X] Bad
Revalidate every 60 seconds	Low (once per minute)	Low	Low delay	[OK] Good
No revalidation	None	Low	Stale content hurts UX	[! ] OK
On-demand revalidation	Only on content change	Low	Fast fresh content	[OK] Good

Rendering Pipeline

Revalidation affects the server-side generation stage before the browser rendering pipeline. When a page is revalidated, the server regenerates HTML and JSON data, which then impacts how quickly the browser receives fresh content to paint.

→Server-side Rendering

→Network Transfer

→Browser Paint

⚠️ BottleneckServer-side regeneration delays the initial HTML response, impacting LCP.

Core Web Vital Affected

LCP

This affects how quickly updated content appears on the page and how often the server regenerates pages, impacting load speed and server response.

Optimization Tips

1Avoid very short revalidation intervals to reduce server load and improve LCP.

2Use on-demand revalidation to update pages only when content changes.

3Balance freshness and performance by choosing appropriate revalidation timing.

Performance Quiz - 3 Questions

What is the main performance risk of setting a very short revalidation interval in Next.js?

A Browser caching is disabled

B Pages become stale and outdated

C Increased server load causing slower page loads

D Client-side JavaScript bundle size increases

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the timing of the HTML document and JSON data fetches. Look for fast server responses and fresh content timestamps.

What to look for: Look for quick server response times and verify if content updates after revalidation triggers without full rebuild delays.

Practice

1. What does the revalidate export in Next.js control?

easy

A. How often a cached page updates after initial generation

B. The maximum number of pages to cache

C. The delay before a page is first generated

D. The priority of server-side rendering

Solution

1. Step 1: Understand the role of revalidate

   The revalidate export sets the time in seconds for Next.js to update a cached page after it was first generated.

2. Step 2: Compare options with this behavior

   Only How often a cached page updates after initial generation correctly describes this update frequency control. Other options describe unrelated concepts.

3. Final Answer:

   How often a cached page updates after initial generation -> Option A

4. Quick Check:

   Revalidate controls update frequency = D [OK]

Hint: Remember revalidate sets cache update time in seconds [OK]

Common Mistakes:

• Confusing revalidate with cache size
• Thinking revalidate delays first page generation
• Mixing revalidate with rendering priority

2. Which of the following is the correct syntax to set a page to revalidate every 60 seconds in Next.js?

easy

A. export revalidate = 60;

B. export const revalidate = 60;

C. const revalidate = 60 export;

D. export const revalidate(60);

Solution

1. Step 1: Recall correct export syntax in Next.js

   To export a constant, the syntax is export const name = value;.

2. Step 2: Match this with revalidate usage

   export const revalidate = 60; matches this pattern exactly. Other options have syntax errors or misplaced keywords.

3. Final Answer:

   export const revalidate = 60; -> Option B

4. Quick Check:

   Correct export syntax = A [OK]

Hint: Use 'export const' to export revalidate value [OK]

Common Mistakes:

• Omitting 'const' keyword
• Using parentheses incorrectly
• Placing export keyword after variable

3. Given this Next.js page code snippet:

export const revalidate = 10;

export default function Page() {
  return <div>Time: {Date.now()}</div>;
}

What will happen if you visit this page multiple times within 10 seconds?

medium

A. The page updates the timestamp on every visit immediately

B. The page never updates after the first visit

C. The page throws an error because Date.now() is not allowed

D. The page shows the same timestamp for 10 seconds before updating

Solution

1. Step 1: Understand revalidate timing effect

   With revalidate = 10, Next.js caches the page and only regenerates it after 10 seconds.

2. Step 2: Predict page behavior on multiple visits

   Within 10 seconds, the cached page is served, so the timestamp stays the same. After 10 seconds, it updates.

3. Final Answer:

   The page shows the same timestamp for 10 seconds before updating -> Option D

4. Quick Check:

   Revalidate caches page for 10 seconds = B [OK]

Hint: Revalidate delays page update by set seconds [OK]

Common Mistakes:

• Assuming Date.now() updates on every visit
• Thinking revalidate disables page updates
• Confusing revalidate with client-side rendering

4. You wrote this code in a Next.js page:

export const revalidate = '30';

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

What is the problem with this code?

medium

A. revalidate must be a number, not a string

B. Page component must be async to use revalidate

C. You cannot export revalidate in a page component

D. The return statement is missing parentheses

Solution

1. Step 1: Check the type of revalidate value

   The revalidate export expects a number representing seconds, not a string.

2. Step 2: Identify the error caused by wrong type

   Using a string will cause Next.js to ignore or error on revalidation timing.

3. Final Answer:

   revalidate must be a number, not a string -> Option A

4. Quick Check:

   revalidate requires number type = A [OK]

Hint: Use number, not quotes, for revalidate seconds [OK]

Common Mistakes:

• Using quotes around the number
• Thinking revalidate needs async function
• Misunderstanding export rules

5. You want a Next.js page to show fresh data but also improve performance by caching for 5 minutes. Which revalidation pattern should you use?

export const revalidate = ?;

Choose the best value and explain why.

hard

A. 60, to update every minute for fresher data

B. 0, to disable caching and always fetch fresh data

C. 300, because 300 seconds equals 5 minutes, balancing freshness and caching

D. Infinity, to cache forever and never update

Solution

1. Step 1: Convert 5 minutes to seconds

   5 minutes equals 300 seconds, so revalidate should be set to 300.

2. Step 2: Understand caching vs freshness tradeoff

   Setting revalidate to 300 caches the page for 5 minutes, improving performance but still updating regularly.

3. Step 3: Evaluate other options

   0 disables caching (no performance gain), 60 updates too often, Infinity never updates (stale data).

4. Final Answer:

   300, because 300 seconds equals 5 minutes, balancing freshness and caching -> Option C

5. Quick Check:

   5 minutes = 300 seconds revalidate [OK]

Hint: Set revalidate to seconds matching desired cache time [OK]

Common Mistakes:

• Using 0 thinking it improves performance
• Choosing too short or too long revalidate values
• Confusing minutes with seconds