Cache invalidation strategies in NextJS - Performance & Optimization

Performance: Cache invalidation strategies

HIGH IMPACT

This affects page load speed by controlling how fresh content is served and how often the browser or server must fetch new data.

Serving updated content without stale data

NextJS

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

Using Next.js ISR (Incremental Static Regeneration) allows fresh content without full rebuilds, improving load speed and freshness.

📈 Performance GainReduces unnecessary full rebuilds; improves LCP by serving fresh content quickly.

Serving updated content without stale data

NextJS

export async function getStaticProps() {
  const data = await fetch('https://api.example.com/data').then(res => res.json());
  return { props: { data } };
}

// No revalidation or cache control, content can become stale indefinitely

No cache invalidation means users may see outdated content until a manual rebuild happens.

📉 Performance CostBlocks LCP improvements due to stale content; users may reload to get fresh data.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No cache invalidation	Minimal	0	Low but stale content delays perceived load	[X] Bad
ISR with revalidate	Minimal	0	Low with fresh content	[OK] Good
Client fetch without cache	Minimal	0	Blocks interaction due to network delay	[X] Bad
Client fetch with cache	Minimal	0	Fast response improves interaction	[OK] Good
Static assets no cache headers	N/A	N/A	High due to repeated downloads	[X] Bad
Static assets with long cache	N/A	N/A	Low, instant load on repeat visits	[OK] Good

Rendering Pipeline

Cache invalidation affects how quickly fresh content is available to the browser, impacting the critical rendering path by controlling network requests and resource freshness.

→Network Request

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork Request stage is most expensive due to fetching fresh or stale resources.

Core Web Vital Affected

LCP

This affects page load speed by controlling how fresh content is served and how often the browser or server must fetch new data.

Optimization Tips

1Use ISR with revalidate in Next.js to serve fresh static content efficiently.

2Set long cache lifetimes with immutable headers for static assets to speed up repeat visits.

3Leverage client-side caching strategies like force-cache to improve responsiveness.

Performance Quiz - 3 Questions

Which cache invalidation strategy helps Next.js serve fresh content without a full rebuild?

A Incremental Static Regeneration (ISR) with revalidate

B No caching, always fetch fresh data

C Client-side caching without revalidation

D Disabling cache headers on static assets

DevTools: Network

How to check: Open DevTools > Network tab > Reload page > Look for cache status column and response headers like Cache-Control and Age.

What to look for: Check if resources are served from cache (status 304 or 'from disk cache') and if cache headers indicate proper expiration or revalidation.

Practice

1. In Next.js, which method allows you to update static pages after a certain time interval to keep data fresh without rebuilding the entire site?

easy

A. getServerSideProps without caching

B. Manually clearing browser cache

C. Using client-side useEffect to fetch data

D. getStaticProps with revalidate

Solution

1. Step 1: Understand Next.js data fetching methods

   getStaticProps generates static pages at build time, but with revalidate, it can update pages after a set interval.

2. Step 2: Compare with other methods

   getServerSideProps fetches fresh data on every request but does not use caching or revalidation intervals.

3. Final Answer:

   getStaticProps with revalidate -> Option D

4. Quick Check:

   Incremental Static Regeneration = getStaticProps + revalidate [OK]

Hint: Remember: revalidate updates static pages periodically [OK]

Common Mistakes:

• Confusing getServerSideProps with revalidation
• Thinking client-side fetching is cache invalidation
• Assuming manual browser cache clearing affects server cache

2. Which of the following is the correct way to set a revalidation time of 10 seconds in getStaticProps?

easy

A. return { props: {}, revalidate: 10 }

B. return { props: {}, revalidateTime: 10 }

C. return { props: {}, cache: 10 }

D. return { props: {}, refresh: 10 }

Solution

1. Step 1: Recall the correct property name for revalidation

   The Next.js documentation specifies revalidate as the property to set seconds for incremental static regeneration.

2. Step 2: Check the return object structure

   The return object from getStaticProps must include props and optionally revalidate with a number value.

3. Final Answer:

   return { props: {}, revalidate: 10 } -> Option A

4. Quick Check:

   Property name is revalidate [OK]

Hint: Use exact property name 'revalidate' in return object [OK]

Common Mistakes:

• Using incorrect property names like 'revalidateTime' or 'refresh'
• Placing revalidate outside the return object
• Setting revalidate as a string instead of a number

3. Consider this Next.js code snippet:

export async function getStaticProps() {
  return {
    props: { time: Date.now() },
    revalidate: 5
  };
}

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

medium

A. The page will throw an error due to Date.now() in getStaticProps

B. The page will show the same timestamp for all visits within 5 seconds

C. The page will update the timestamp on every visit

D. The page will never update the timestamp

Solution

1. Step 1: Understand revalidate behavior

   The revalidate: 5 means Next.js will regenerate the page at most every 5 seconds.

2. Step 2: Predict output within 5 seconds

   Within 5 seconds, the cached page is served, so the timestamp remains the same for all visits.

3. Final Answer:

   The page will show the same timestamp for all visits within 5 seconds -> Option B

4. Quick Check:

   Revalidate interval caches page for 5 seconds [OK]

Hint: Revalidate caches page until interval expires [OK]

Common Mistakes:

• Assuming timestamp updates on every visit
• Thinking Date.now() causes errors in static props
• Believing revalidate disables caching

4. You wrote this code in Next.js:

export async function getStaticProps() {
  return {
    props: { data: await fetchData() },
    revalidate: '10'
  };
}

Why does this cause a problem?

medium

A. Because revalidate must be a number, not a string

B. Because fetchData cannot be awaited in getStaticProps

C. Because props must be a function, not an object

D. Because revalidate cannot be used with getStaticProps

Solution

1. Step 1: Check the type of revalidate

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

2. Step 2: Understand impact of wrong type

   Passing a string causes Next.js to throw a type error or ignore the revalidation, breaking cache invalidation.

3. Final Answer:

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

4. Quick Check:

   Revalidate value type = number [OK]

Hint: Use number type for revalidate seconds [OK]

Common Mistakes:

• Passing revalidate as a string
• Thinking async/await is disallowed in getStaticProps
• Confusing props structure requirements

5. You want to always serve fresh data on every request in Next.js without caching. Which method should you use and why?

hard

A. Use getStaticProps without revalidate

B. Use getStaticProps with revalidate: 0

C. Use getServerSideProps because it runs on every request

D. Use client-side fetching only with useEffect

Solution

1. Step 1: Identify method for fresh data every request

   getServerSideProps runs on the server for every page request, ensuring fresh data.

2. Step 2: Compare with static methods

   getStaticProps generates static pages at build time or with revalidation intervals, so it does not guarantee fresh data every request.

3. Final Answer:

   Use getServerSideProps because it runs on every request -> Option C

4. Quick Check:

   Fresh data every request = getServerSideProps [OK]

Hint: Always fresh data? Use getServerSideProps [OK]

Common Mistakes:

• Using revalidate: 0 expecting no caching
• Relying only on client-side fetching for SEO
• Confusing static and server-side methods