Modal pattern with intercepting routes in NextJS - Performance & Optimization

Performance: Modal pattern with intercepting routes

MEDIUM IMPACT

This pattern affects page load speed and interaction responsiveness by controlling when modals load and how routes update without full page reloads.

Displaying a modal dialog triggered by navigation without full page reload

NextJS

import { useRouter } from 'next/navigation';

function Page() {
  const router = useRouter();
  const openModal = () => {
    router.push('/page/modal'); // Intercepting route opens modal overlay
  };
  return <button onClick={openModal}>Open Modal</button>;
}

// Modal is a separate route segment rendered as overlay without full reload

Uses Next.js intercepting routes to load modal as overlay, avoiding full page reload and improving responsiveness.

📈 Performance GainReduces blocking time to under 50ms, improves INP by avoiding full reload

Displaying a modal dialog triggered by navigation without full page reload

NextJS

import { useRouter, useSearchParams } from 'next/navigation';

function Page() {
  const router = useRouter();
  const searchParams = useSearchParams();
  const modalOpen = searchParams.get('modal') === 'true';

  return (
    <>
      <button onClick={() => router.push('/page?modal=true')}>Open Modal</button>
      {modalOpen && <Modal />}
    </>
  );
}

function Modal() {
  return <div>Modal Content</div>;
}

// Navigation triggers client navigation/re-render to show modal content
// e.g., /page?modal=true causes navigation and re-render

Triggers full page reload on modal open, causing slower interaction and higher load times.

📉 Performance CostBlocks rendering for 300-500ms depending on network, increases LCP and INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full page reload modal	High (reloads entire DOM)	Multiple reflows	High paint cost	[X] Bad
Intercepting route modal overlay	Low (adds overlay nodes)	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

Intercepting routes load modal content as a client-side overlay, avoiding full page reload and reducing layout recalculations.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint due to full page reload in bad pattern

Core Web Vital Affected

INP

This pattern affects page load speed and interaction responsiveness by controlling when modals load and how routes update without full page reloads.

Optimization Tips

1Use intercepting routes to load modals as overlays without full page reloads.

2Avoid adding heavy DOM changes inside modal overlays to reduce reflows.

3Measure interaction responsiveness (INP) to verify modal performance.

Performance Quiz - 3 Questions

What is the main performance benefit of using intercepting routes for modals in Next.js?

A Improves SEO by hiding modal content from crawlers

B Reduces JavaScript bundle size by removing modal code

C Avoids full page reloads, improving interaction speed

D Automatically caches modal content on the server

DevTools: Performance

How to check: Record a user interaction opening the modal. Compare time between click and next paint. Look for full page reload events.

What to look for: Long main thread blocking and multiple layout recalculations indicate bad pattern; short interaction time and minimal layout changes indicate good pattern.

Practice

1. What is the main benefit of using the modal pattern with intercepting routes in Next.js?

easy

A. It automatically reloads the entire page when opening a modal.

B. It allows showing a popup without leaving the current page.

C. It disables keyboard navigation while the modal is open.

D. It prevents any URL changes when interacting with the modal.

Solution

1. Step 1: Understand modal with intercepting routes

   This pattern lets you open a modal that overlays the current page content without navigating away.

2. Step 2: Identify the benefit

   Because the modal is shown on top, the user stays on the same page, improving user experience.

3. Final Answer:

   It allows showing a popup without leaving the current page. -> Option B

4. Quick Check:

   Modal pattern = popup without page change [OK]

Hint: Modals with intercepting routes keep you on the same page [OK]

Common Mistakes:

• Thinking the page reloads when modal opens
• Assuming URL never changes
• Believing keyboard navigation is disabled

2. Which Next.js feature is commonly used to control modal visibility with intercepting routes?

easy

A. Using URL query parameters to toggle modal state

B. Using React class components with state

C. Using server-side rendering to open modals

D. Using CSS hover effects to show modals

Solution

1. Step 1: Identify modal control method

   Next.js modals with intercepting routes often use URL query parameters to track if modal is open or closed.

2. Step 2: Eliminate incorrect options

   React class components are outdated; server-side rendering doesn't control modal visibility dynamically; CSS hover is unrelated to routing.

3. Final Answer:

   Using URL query parameters to toggle modal state -> Option A

4. Quick Check:

   Modal visibility = URL query param [OK]

Hint: Modal open state is often in URL query parameters [OK]

Common Mistakes:

• Confusing client state with URL state
• Using class components instead of hooks
• Relying on CSS hover for modal control

3. Given this Next.js snippet controlling a modal with query param ?modal=open:

const router = useRouter();
const isModalOpen = router.query.modal === 'open';

return (
  <>
    {isModalOpen && <ModalComponent />}
    <MainPageContent />
  </>
);

What happens when the URL changes from /page to /page?modal=open?

medium

A. The page reloads and shows a blank screen.

B. The main page content is replaced by the modal component.

C. Nothing changes because query parameters don't affect rendering.

D. The modal component appears over the main page content.

Solution

1. Step 1: Understand the code logic

   The code checks if the query parameter 'modal' equals 'open'. If yes, it renders the modal component alongside the main content.

2. Step 2: Analyze URL change effect

   Changing URL to include '?modal=open' sets isModalOpen true, so modal appears over the main page without replacing it.

3. Final Answer:

   The modal component appears over the main page content. -> Option D

4. Quick Check:

   Query param 'modal=open' = modal visible [OK]

Hint: Query param 'modal=open' triggers modal display [OK]

Common Mistakes:

• Thinking modal replaces main content
• Ignoring query parameters in rendering
• Assuming page reloads on query change

4. Consider this Next.js modal code snippet:

const router = useRouter();
const isModalOpen = router.query.modal === 'open';

function closeModal() {
  router.push('/page');
}

return (
  <>
    {isModalOpen && <Modal onClose={closeModal} />}
    <PageContent />
  </>
);

What is a likely bug in this code regarding accessibility?

medium

A. The URL does not update when the modal opens.

B. The modal never closes because router.push is incorrect.

C. Keyboard focus is not moved to the modal when it opens.

D. The modal content is rendered outside the React tree.

Solution

1. Step 1: Review modal accessibility needs

   When a modal opens, keyboard focus should move inside it for screen reader and keyboard users.

2. Step 2: Check code for focus management

   The code changes URL and renders modal but does not handle moving keyboard focus to modal.

3. Final Answer:

   Keyboard focus is not moved to the modal when it opens. -> Option C

4. Quick Check:

   Modal accessibility = move keyboard focus [OK]

Hint: Always move keyboard focus into modal on open [OK]

Common Mistakes:

• Ignoring keyboard focus management
• Assuming URL push closes modal automatically
• Confusing rendering with accessibility

5. You want to implement a modal in Next.js that opens on /gallery?modal=photo123 and closes by removing the query param, without losing the gallery scroll position. Which approach best achieves this?

hard

A. Use router.push with shallow: true to update URL without full reload and keep scroll.

B. Use router.replace without shallow to reload page and reset scroll.

C. Use window.location.href to change URL and force reload.

D. Use CSS to hide modal and ignore URL changes.

Solution

1. Step 1: Understand shallow routing in Next.js

   Shallow routing updates the URL without running data fetching methods or reloading the page, preserving scroll and state.

2. Step 2: Apply shallow routing to modal open/close

   Using router.push with shallow: true changes query params to open/close modal without losing scroll position.

3. Final Answer:

   Use router.push with shallow: true to update URL without full reload and keep scroll. -> Option A

4. Quick Check:

   Shallow routing = URL change without reload [OK]

Hint: Use shallow routing to keep scroll when changing URL [OK]

Common Mistakes:

• Using router.replace without shallow reloads page
• Using window.location.href causes full reload
• Ignoring URL for modal state control