Revalidation after mutation in NextJS - Performance & Optimization

Performance: Revalidation after mutation

MEDIUM IMPACT

This affects how quickly updated data appears on the page after a user changes it, impacting perceived responsiveness and freshness.

Updating data and showing fresh content immediately

NextJS

import { mutate } from 'swr';

async function handleUpdate() {
  await fetch('/api/update', { method: 'POST', body: JSON.stringify(data) });
  mutate('/api/data', updatedData, false);
}

Using mutate from SWR or React Query updates cache instantly without full re-fetch, enabling immediate UI update.

📈 Performance Gainnon-blocking UI update, reduces re-fetch latency by 100-300ms

Updating data and showing fresh content immediately

NextJS

async function handleUpdate() {
  await fetch('/api/update', { method: 'POST', body: JSON.stringify(data) });
  router.refresh();
}

Calling router.refresh() reloads the entire page data, causing a full re-fetch and blocking rendering until complete.

📉 Performance Costblocks rendering for 200-500ms depending on data size and network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full router.refresh() after mutation	High (full page data reload)	Multiple reflows due to layout recalculation	High paint cost due to full content update	[X] Bad
Cache mutation with mutate() after mutation	Low (only updated nodes)	Single reflow or none	Low paint cost with partial update	[OK] Good

Rendering Pipeline

After mutation, the browser either triggers a full data re-fetch causing layout recalculation and paint delays, or updates cache directly allowing fast paint without layout thrashing.

→Data Fetch

→Layout

→Paint

→Composite

⚠️ BottleneckData Fetch and Layout when full revalidation occurs

Core Web Vital Affected

INP

This affects how quickly updated data appears on the page after a user changes it, impacting perceived responsiveness and freshness.

Optimization Tips

1Avoid full page refreshes after data mutation to reduce blocking rendering.

2Use cache mutation methods like mutate() to update UI instantly.

3Monitor revalidation impact on interaction responsiveness (INP).

Performance Quiz - 3 Questions

What is the main performance drawback of calling router.refresh() after a data mutation in Next.js?

A It triggers a full page data re-fetch causing blocking rendering.

B It skips updating the UI causing stale data display.

C It only updates local cache without network request.

D It reduces bundle size but increases CPU usage.

DevTools: Performance

How to check: Record a profile while performing the mutation and revalidation. Look for long tasks and layout shifts after mutation.

What to look for: Long blocking times and multiple reflows indicate bad pattern; quick paint with minimal layout changes indicates good pattern.

Practice

1. What is the main purpose of revalidation after mutation in Next.js App Router?

easy

A. To update the page data after a change so the UI shows fresh information

B. To prevent any data changes from being saved

C. To reload the entire website from scratch

D. To disable user interactions temporarily

Solution

1. Step 1: Understand mutation effect

   When data changes (mutation), the UI might show old data if not updated.

2. Step 2: Purpose of revalidation

   Revalidation reloads or refreshes data so the UI reflects the latest changes.

3. Final Answer:

   To update the page data after a change so the UI shows fresh information -> Option A

4. Quick Check:

   Revalidation updates data = A [OK]

Hint: Revalidation means refreshing data after changes [OK]

Common Mistakes:

• Thinking revalidation stops data saving
• Confusing revalidation with full page reload
• Believing it disables user actions

2. Which Next.js App Router method is used to trigger revalidation after a mutation?

easy

A. router.replace()

B. router.reload()

C. router.push()

D. router.refresh()

Solution

1. Step 1: Identify method for revalidation

   Next.js App Router provides router.refresh() to reload data without full page reload.

2. Step 2: Differentiate from other methods

   router.reload() reloads whole page, router.push() and router.replace() change routes.

3. Final Answer:

   router.refresh() -> Option D

4. Quick Check:

   Revalidation uses router.refresh() = A [OK]

Hint: Use router.refresh() to reload data after mutation [OK]

Common Mistakes:

• Using router.reload() which reloads full page
• Confusing route navigation methods with revalidation
• Trying to use router.replace() for data refresh

3. Given this code snippet in a Next.js component:

import { useRouter } from 'next/navigation';

export default function UpdateButton() {
  const router = useRouter();

  async function handleClick() {
    await fetch('/api/update', { method: 'POST' });
    router.refresh();
  }

  return Update;
}

What happens when the button is clicked?

medium

A. The API is called, then the page data refreshes without full reload

B. Nothing happens because router.refresh() is incorrect

C. The page reloads completely, losing state

D. The button click causes a navigation to /api/update

Solution

1. Step 1: Analyze handleClick function

   It calls the API with POST, then calls router.refresh() to reload data.

2. Step 2: Understand router.refresh() effect

   This refreshes the current route's data without a full page reload or navigation.

3. Final Answer:

   The API is called, then the page data refreshes without full reload -> Option A

4. Quick Check:

   API call + router.refresh() updates data = C [OK]

Hint: router.refresh() updates data without full reload [OK]

Common Mistakes:

• Thinking router.refresh() reloads entire page
• Assuming router.refresh() navigates to API route
• Believing nothing happens due to syntax error

4. Identify the error in this Next.js code snippet that tries to revalidate after mutation:

import { useRouter } from 'next/navigation';

export default function DeleteButton() {
  const router = useRouter;

  async function handleDelete() {
    await fetch('/api/delete', { method: 'DELETE' });
    router.refresh();
  }

  return Delete;
}

medium

A. Button onClick should be onSubmit

B. fetch method DELETE is invalid in Next.js

C. router is not called as a function, so router.refresh() fails

D. handleDelete should not be async

Solution

1. Step 1: Check router initialization

   Code uses const router = useRouter; missing parentheses, so router is a function reference, not the router object.

2. Step 2: Effect on router.refresh()

   Calling router.refresh() fails because router is not an object but a function reference.

3. Final Answer:

   router is not called as a function, so router.refresh() fails -> Option C

4. Quick Check:

   useRouter missing () causes error = D [OK]

Hint: Always call useRouter() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on useRouter()
• Thinking DELETE method is invalid
• Confusing onClick with onSubmit

5. You have a Next.js page showing a list of items fetched from the server. After adding a new item via a mutation API call, you want the list to update automatically. Which approach correctly ensures the list refreshes with the new data without a full page reload?

hard

A. Call router.push('/current-page') after mutation to reload the page

B. Call router.refresh() after mutation to revalidate and update data

C. Reload the browser window with window.location.reload()

D. Do nothing; the list updates automatically without any code

Solution

1. Step 1: Understand goal

   After mutation, the UI must show updated list without full reload or navigation.

2. Step 2: Evaluate options

   router.push('/current-page') navigates and reloads route, window.location.reload() reloads full page, and doing nothing won't update data.

3. Step 3: Correct method

   router.refresh() triggers Next.js to revalidate data and update UI efficiently.

4. Final Answer:

   Call router.refresh() after mutation to revalidate and update data -> Option B

5. Quick Check:

   Use router.refresh() to update data after mutation = B [OK]

Hint: Use router.refresh() to update data without full reload [OK]

Common Mistakes:

• Using router.push() causing unnecessary navigation
• Reloading full page losing state
• Assuming UI updates automatically without refresh