Error.tsx for route errors in NextJS - Performance & Optimization

Performance: Error.tsx for route errors

MEDIUM IMPACT

This affects how quickly error pages render during route failures, impacting user experience during navigation errors.

Handling route errors with an error component

NextJS

'use client';

export default function Error({error, reset}) {
  return (
    <div role="alert" aria-live="assertive">
      An error occurred. <button onClick={reset}>Please try again later.</button>
    </div>
  );
}

Static error UI renders immediately without blocking or extra data fetching, improving responsiveness.

📈 Performance GainNon-blocking render, reduces INP by 50-100 ms

Handling route errors with an error component

NextJS

'use client';

export default function Error({error, reset}) {
  // Heavy logic inside error component
  let data = 0;
  for(let i = 0; i < 10000000; i++) {
    data += i;
  }
  return <div>Error occurred: {data}</div>;
}

Running heavy synchronous logic inside the error component blocks rendering and delays error display.

📉 Performance CostBlocks rendering for 100+ ms depending on computation time, increases INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous logic in Error.tsx	Increased DOM nodes if rendering fetched data	Multiple reflows due to async updates	High paint cost due to delayed rendering	[X] Bad
Static, simple Error.tsx with ARIA roles	Minimal DOM nodes	Single reflow on initial render	Low paint cost with immediate display	[OK] Good

Rendering Pipeline

When a route error occurs, the Error.tsx component is rendered. If it contains heavy synchronous logic, it delays Style Calculation and Layout, blocking Paint and Composite stages.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckBlocking JavaScript execution delays Paint and Composite stages.

Core Web Vital Affected

INP

This affects how quickly error pages render during route failures, impacting user experience during navigation errors.

Optimization Tips

1Avoid heavy synchronous logic inside Error.tsx to prevent blocking rendering.

2Keep error components simple and static for fast display.

3Use ARIA roles like role="alert" and aria-live="assertive" for accessibility and immediate screen reader notification.

Performance Quiz - 3 Questions

What is the main performance issue with heavy logic inside Error.tsx for route errors?

A It improves Largest Contentful Paint.

B It reduces bundle size.

C It blocks rendering and delays error display.

D It decreases DOM node count.

DevTools: Performance

How to check: Record a session navigating to a route that triggers Error.tsx. Look for scripting time and time to first paint of the error component.

What to look for: Long scripting blocks before paint indicate blocking logic; quick paint with minimal scripting shows good performance.

Practice

1. What is the main purpose of the Error.tsx file in a Next.js route?

easy

A. To define the main layout of the application

B. To display a friendly message when a route fails or an error occurs

C. To handle user authentication and login

D. To fetch data from an API for the route

Solution

1. Step 1: Understand the role of Error.tsx in Next.js

   Error.tsx is designed to catch errors in routes and show a user-friendly message instead of a broken page.

2. Step 2: Compare with other options

   Layouts, authentication, and data fetching are handled elsewhere, not in Error.tsx.

3. Final Answer:

   To display a friendly message when a route fails or an error occurs -> Option B

4. Quick Check:

   Error.tsx shows friendly error messages [OK]

Hint: Error.tsx shows errors, not layouts or data [OK]

Common Mistakes:

• Confusing Error.tsx with layout or data files
• Thinking Error.tsx handles authentication
• Assuming Error.tsx fetches API data

2. Which of the following is the correct way to export a default Error component in Error.tsx for Next.js?

easy

A. export function Error() { return Error occurred; }

B. function Error() { return Error occurred; }

C. export default function Error() { return Error occurred; }

D. default export function Error() { return Error occurred; }

Solution

1. Step 1: Recall correct default export syntax in React/Next.js

   The correct syntax is to declare the function and export it as default in one statement.

2. Step 2: Identify syntax errors in other options

   function Error() { return
   Error occurred; } misses export, C exports a named function, D has invalid syntax.

3. Final Answer:

   export default function Error() { return <div>Error occurred</div>; } -> Option C

4. Quick Check:

   Default export uses 'export default function' [OK]

Hint: Default export needs 'export default function' [OK]

Common Mistakes:

• Forgetting to export the component
• Using named export instead of default
• Incorrect export syntax like 'default export'

3. Given this Error.tsx component, what will be rendered when an error occurs?

export default function Error() {
  return (
    <main role="alert" aria-live="assertive">
      <h1>Oops! Something went wrong.</h1>
      <button onClick={() => window.location.reload()}>Try Again</button>
    </main>
  );
}

medium

A. A heading with an error message and a button to reload the page

B. A blank page with no content

C. Only a button that does nothing

D. An error stack trace displayed to the user

Solution

1. Step 1: Analyze the JSX returned by the Error component

   The component returns a main element with a heading and a button that reloads the page on click.

2. Step 2: Understand the button behavior

   The button triggers window.location.reload(), so it reloads the current page when clicked.

3. Final Answer:

   A heading with an error message and a button to reload the page -> Option A

4. Quick Check:

   Error component shows message + reload button [OK]

Hint: Look for JSX elements and button onClick behavior [OK]

Common Mistakes:

• Assuming no content renders
• Thinking button does nothing
• Expecting error stack trace to show

4. What is wrong with this Error.tsx component code?

export default function Error() {
  return (
    <div>
      <h1>Error!</h1>
      <button onClick={reloadPage}>Reload</button>
    </div>
  );
}

function reloadPage() {
  location.reload;
}

medium

A. The reloadPage function does not call location.reload() correctly

B. The button should not have an onClick handler

C. The component must use a <main> tag instead of <div>

D. The function reloadPage should be inside the component

Solution

1. Step 1: Check the reloadPage function implementation

   location.reload is a function and must be called with parentheses: location.reload()

2. Step 2: Verify other parts

   The button can have onClick, using div is allowed, and reloadPage can be outside the component.

3. Final Answer:

   The reloadPage function does not call location.reload() correctly -> Option A

4. Quick Check:

   Call functions with parentheses to execute [OK]

Hint: Check if functions are called with () [OK]

Common Mistakes:

• Forgetting parentheses on function calls
• Thinking onClick is invalid on button
• Believing HTML tags must be <main>

5. You want to improve accessibility in your Error.tsx component by adding ARIA roles and live regions. Which of these changes is best practice?

hard

A. Use a <div> with aria-hidden="true" around the error message

B. Remove all ARIA attributes to keep it simple

C. Add tabindex="-1" to the button only

D. Wrap the error message in a <main> with role="alert" and aria-live="assertive"

Solution

1. Step 1: Understand ARIA roles for error messages

   Using role="alert" and aria-live="assertive" notifies screen readers immediately about errors.

2. Step 2: Evaluate other options

   aria-hidden="true" hides content from screen readers, tabindex="-1" on button is unrelated, removing ARIA reduces accessibility.

3. Final Answer:

   Wrap the error message in a <main> with role="alert" and aria-live="assertive" -> Option D

4. Quick Check:

   Use role="alert" and aria-live for error accessibility [OK]

Hint: Use role="alert" and aria-live="assertive" for errors [OK]

Common Mistakes:

• Hiding error messages from screen readers
• Misusing tabindex on unrelated elements
• Removing ARIA attributes thinking they are optional