Parallel routes concept in NextJS - Performance & Optimization

Performance: Parallel routes concept

MEDIUM IMPACT

Parallel routes affect how quickly different parts of a page load and render by allowing multiple UI segments to load simultaneously.

Loading multiple UI sections on a page without blocking each other

NextJS

// File structure:
// app/dashboard/@main/page.tsx     (MainContent)
// app/dashboard/@sidebar/page.tsx  (Sidebar)
// app/dashboard/@footer/page.tsx   (Footer)
// app/dashboard/layout.tsx (below)

import { ReactNode } from 'react';

export default function Layout({
  main,
  sidebar,
  footer
}: {
  main: ReactNode;
  sidebar: ReactNode;
  footer: ReactNode;
}) {
  return (
    <>
      {main}
      {sidebar}
      {footer}
    </>
  );
}

Loads each route segment independently and in parallel, allowing faster rendering of visible content and reducing blocking.

📈 Performance GainReduces LCP by 150-300ms by parallelizing route loading and rendering

Loading multiple UI sections on a page without blocking each other

NextJS

export default function Page() {
  return (
    <>
      <MainContent />
      <Sidebar />
      <Footer />
    </>
  )
}

All components load sequentially in the same route, causing slower overall load and blocking rendering of some parts until others finish.

📉 Performance CostBlocks rendering until all components load, increasing LCP by 200-400ms depending on content size

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single route loading all UI	Single DOM tree with all nodes	Multiple reflows as components mount sequentially	Higher paint cost due to delayed rendering	[X] Bad
Parallel routes loading UI segments	Multiple smaller DOM trees loaded independently	Fewer reflows per route, can happen concurrently	Lower paint cost with faster visible content	[OK] Good

Rendering Pipeline

Parallel routes split the UI into independent segments that the browser can fetch and render simultaneously, reducing blocking in the critical rendering path.

→Network Fetch

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckNetwork Fetch and JavaScript Execution when routes load sequentially

Core Web Vital Affected

LCP

Parallel routes affect how quickly different parts of a page load and render by allowing multiple UI segments to load simultaneously.

Optimization Tips

1Split UI into parallel routes to load multiple parts simultaneously.

2Avoid loading all UI in a single route to prevent blocking and slow LCP.

3Use parallel routes to improve perceived load speed and responsiveness.

Performance Quiz - 3 Questions

How do parallel routes improve page load performance in Next.js?

A By loading multiple UI segments at the same time without waiting for others

B By combining all UI segments into one large bundle

C By delaying rendering until all data is fetched

D By disabling JavaScript on the page

DevTools: Performance

How to check: Record a page load and look at the flame chart to see if multiple route segments load and render concurrently or sequentially.

What to look for: Look for overlapping network requests and JavaScript execution for route segments indicating parallel loading, which improves LCP.

Practice

1. What is the main purpose of parallel routes in Next.js?

easy

A. To disable navigation between pages

B. To load pages sequentially one after another

C. To replace client-side routing with server-side only

D. To display multiple parts of a page simultaneously

Solution

1. Step 1: Understand what parallel routes do

   Parallel routes allow showing multiple UI sections at the same time on a page.

2. Step 2: Compare options with this understanding

   Only To display multiple parts of a page simultaneously correctly describes this purpose; others describe unrelated behaviors.

3. Final Answer:

   To display multiple parts of a page simultaneously -> Option D

4. Quick Check:

   Parallel routes = show multiple parts [OK]

Hint: Parallel routes show multiple page parts at once [OK]

Common Mistakes:

• Thinking parallel routes load pages one after another
• Confusing parallel routes with disabling navigation
• Assuming parallel routes replace client-side routing

2. Which folder naming pattern is used to define a parallel route in Next.js?

easy

A. Using parentheses like (route)

B. Using square brackets like [route]

C. Using curly braces like {route}

D. Using angle brackets like <route>

Solution

1. Step 1: Recall folder naming for parallel routes

   Next.js uses parentheses around folder names to mark parallel routes.

2. Step 2: Match options to this rule

   Only Using parentheses like (route) uses parentheses, which is correct for parallel routes.

3. Final Answer:

   Using parentheses like (route) -> Option A

4. Quick Check:

   Parallel routes folder = parentheses [OK]

Hint: Parallel routes folders use parentheses ( ) [OK]

Common Mistakes:

• Using square brackets which are for dynamic routes
• Confusing with curly braces or angle brackets
• Not using any special characters for parallel routes

3. Given this folder structure in Next.js:

app/
  (sidebar)/
    page.jsx
  (content)/
    page.jsx
  layout.jsx

What will happen when the app renders layout.jsx with parallel routes?

medium

A. Both sidebar and content pages render side by side inside layout

B. Only the sidebar page renders, content is ignored

C. Only the content page renders, sidebar is ignored

D. Neither sidebar nor content pages render automatically

Solution

1. Step 1: Understand parallel routes folder names

   Folders named with parentheses define parallel routes that render simultaneously.

2. Step 2: Apply to given structure

   Both (sidebar) and (content) are parallel routes, so their pages render side by side inside layout.

3. Final Answer:

   Both sidebar and content pages render side by side inside layout -> Option A

4. Quick Check:

   Parallel routes render all named folders simultaneously [OK]

Hint: Parentheses folders render together inside layout [OK]

Common Mistakes:

• Thinking only one parallel route renders at a time
• Assuming parallel routes need manual import to render
• Confusing parallel routes with nested routes

4. You have this code in your layout.jsx to render parallel routes:

import { Slot } from 'next/navigation';

export default function Layout() {
  return (
    

      <Slot name="sidebar" />
      <Slot name="content" />
    
  );
}

Why does this code cause an error?

medium

A. Because Slot must be imported from 'next/navigation' as a named import

B. Because <Slot /> should be self-closing JSX tags, not string literals

C. Because parallel routes cannot use Slot components

D. Because Slot requires a default export, not named

Solution

1. Step 1: Check JSX syntax in return statement

   The code uses <Slot name="sidebar" /> as a string literal, not as JSX tags.

2. Step 2: Correct JSX usage

   It should be <Slot name="sidebar" /> without quotes, as a self-closing JSX component.

3. Final Answer:

   Because <Slot /> should be self-closing JSX tags, not string literals -> Option B

4. Quick Check:

   JSX tags must not be strings [OK]

Hint: Use JSX tags, not strings, for [OK]

Common Mistakes:

• Writing JSX tags as strings inside return
• Importing Slot incorrectly
• Thinking Slot can't be used in parallel routes

5. You want to create a page with a sidebar and main content using parallel routes. Which folder structure and code snippet correctly implements this in Next.js?

app/
  (sidebar)/
    page.jsx
  (main)/
    page.jsx
  layout.jsx

And in layout.jsx:

export default function Layout() {
  return (
    

      {/* What goes here? */}
    
  );
}

hard

A. <Slot />

B. <Slot name="content" />
<Slot name="sidebar" />

C. <Slot name="sidebar" />
<Slot name="main" />

D. <Outlet name="sidebar" />
<Outlet name="main" />

Solution

1. Step 1: Match folder names to Slot names

   Folders are named (sidebar) and (main), so Slots must use these exact names.

2. Step 2: Check code snippet for correct Slot usage

   <Slot name="sidebar" /> <Slot name="main" /> uses <Slot name="sidebar" /> and <Slot name="main" />, matching folder names and correct JSX syntax.

3. Final Answer:

   <Slot name="sidebar" /> <Slot name="main" /> -> Option C

4. Quick Check:

   Slot names = folder names [OK]

Hint: Slot names must match parallel route folder names [OK]

Common Mistakes:

• Using wrong Slot names that don't match folders
• Using instead of
• Using only one Slot for multiple parallel routes