Parallel routes (@slot) in NextJS - Performance & Optimization

Performance: Parallel routes (@slot)

MEDIUM IMPACT

Parallel routes with @slot affect how quickly multiple UI sections load and render simultaneously, improving perceived page speed and interaction readiness.

Loading multiple independent UI sections on the same page

NextJS

export default function Page({ sidebar, mainContent, footer }) {
  return (
    <>
      {sidebar}
      {mainContent}
      {footer}
    </>
  )
}

Loads sidebar, main content, and footer routes in parallel, allowing browser to render visible parts faster and independently.

📈 Performance GainReduces LCP by 150-400ms by parallelizing data fetching and rendering, improving perceived load speed.

Loading multiple independent UI sections on the same page

NextJS

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

All components load sequentially in the main route, blocking rendering until each finishes, delaying Largest Contentful Paint.

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

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Sequential route loading	Single DOM tree built after all data loads	Multiple reflows as components mount sequentially	High paint cost due to delayed content	[X] Bad
Parallel routes with @slot	Multiple smaller DOM trees built independently	Fewer reflows as components render in parallel	Lower paint cost with faster visible content	[OK] Good

Rendering Pipeline

Parallel routes split the page into multiple route segments that fetch and render independently. This allows the browser to start painting visible UI parts sooner without waiting for all data or components to load.

→Data Fetching

→Rendering

→Paint

→Composite

⚠️ BottleneckRendering stage can be blocked if routes load sequentially or depend on each other.

Core Web Vital Affected

LCP

Parallel routes with @slot affect how quickly multiple UI sections load and render simultaneously, improving perceived page speed and interaction readiness.

Optimization Tips

1Use @slot to define parallel routes for independent UI sections.

2Parallel routes reduce blocking time and improve Largest Contentful Paint.

3Avoid sequential loading of large components to prevent render delays.

Performance Quiz - 3 Questions

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

A By delaying rendering until all data is fetched sequentially

B By combining all components into a single large bundle

C By loading multiple UI sections concurrently, reducing blocking time

D By removing all CSS to speed up painting

DevTools: Performance

How to check: Record a page load in DevTools Performance panel. Look for multiple network requests and rendering tasks happening concurrently rather than sequentially.

What to look for: Shorter gaps between first content paint and Largest Contentful Paint, and overlapping network and rendering tasks indicating parallel loading.

Practice

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

easy

A. To display multiple UI parts simultaneously in different route segments

B. To fetch data from an API endpoint

C. To define server-side rendering behavior

D. To create dynamic API routes

Solution

1. Step 1: Understand the role of @slot

   @slot is used to show multiple UI parts at once by matching route segments.

2. Step 2: Identify the purpose in parallel routes

   It allows different UI sections to render in parallel, improving layout flexibility.

3. Final Answer:

   To display multiple UI parts simultaneously in different route segments -> Option A

4. Quick Check:

   Parallel routes use @slot to show multiple UI parts [OK]

Hint: Remember: @slot shows multiple UI parts at once [OK]

Common Mistakes:

• Confusing @slot with data fetching
• Thinking @slot controls API routes
• Assuming @slot is for server rendering only

2. Which of the following is the correct syntax to define a parallel route slot named sidebar in Next.js?

easy

A. export const @slot sidebar = () => <div>Sidebar</div>;

B. export const slot_sidebar = () => <div>Sidebar</div>;

C. export const sidebar = () => <div>Sidebar</div>;

D. export const SidebarSlot = () => <div>Sidebar</div>;

Solution

1. Step 1: Recall parallel route slot syntax

   Slots are exported as named exports matching the slot name, e.g., export const sidebar.

2. Step 2: Check each option

   export const sidebar = () => <div>Sidebar</div>; correctly exports a constant named sidebar as a React component.

3. Final Answer:

   export const sidebar = () => <div>Sidebar</div>; -> Option C

4. Quick Check:

   Slot name matches export const name [OK]

Hint: Export slot as named const matching slot name [OK]

Common Mistakes:

• Using @slot keyword in export
• Prefixing slot name incorrectly
• Using PascalCase instead of slot name

3. Given this Next.js parallel route layout code:

export const header = () => <header>Header</header>;
export const footer = () => <footer>Footer</footer>;

export default function Page() {
  return <main>Main Content</main>;
}

What will be rendered on the page?

medium

A. Only <main>Main Content</main> is rendered

B. <header>Header</header>, <main>Main Content</main>, and <footer>Footer</footer> are all rendered

C. Only <header>Header</header> and <footer>Footer</footer> are rendered

D. Syntax error due to missing @slot usage

Solution

1. Step 1: Understand parallel route slots rendering

   Slots like header and footer render alongside the default export component.

2. Step 2: Combine all parts

   The page renders header, main content, and footer together as parallel UI parts.

3. Final Answer:

   <header>Header</header>, <main>Main Content</main>, and <footer>Footer</footer> are all rendered -> Option B

4. Quick Check:

   Parallel routes render all slots plus default [OK]

Hint: Slots and default export render together [OK]

Common Mistakes:

• Thinking only default export renders
• Assuming slots need explicit @slot tags in JSX
• Confusing syntax error with missing @slot

4. You wrote this code for a parallel route slot:

export const sidebar = () => <div>Sidebar</div>;

export default function Page() {
  return <main>Main</main>;
}

But the sidebar does not appear on the page. What is the likely cause?

medium

A. The slot name sidebar does not match any route segment

B. You forgot to import React

C. The default export must be named sidebar

D. Parallel routes require class components, not functions

Solution

1. Step 1: Check slot name and route segment matching

   Slots render only if their name matches a parallel route segment in the folder structure.

2. Step 2: Identify mismatch issue

   If no route segment named sidebar exists, the slot won't render.

3. Final Answer:

   The slot name sidebar does not match any route segment -> Option A

4. Quick Check:

   Slot name must match route segment [OK]

Hint: Match slot name exactly to route segment folder [OK]

Common Mistakes:

• Assuming React import is required in Next.js 13+
• Thinking default export must be slot named
• Believing only class components work for slots

5. You want to create a layout with parallel routes showing a nav bar and a content area side by side. Which folder structure and code setup correctly implements this using @slot?

hard

A. Folders: app/(nav)/page.tsx and app/(content)/page.tsx with export const nav = () => <nav>Nav</nav>; in nav folder and export default function Page() { return <main>Content</main>; } in content folder

B. Folders: app/(nav)/page.tsx and app/(content)/page.tsx with export default function Nav() { return <nav>Nav</nav>; } and export default function Content() { return <main>Content</main>; }

C. Folders: app/nav/page.tsx and app/content/page.tsx with export default function Nav() { return <nav>Nav</nav>; } and export default function Content() { return <main>Content</main>; }

D. Folders: app/nav/page.tsx and app/content/page.tsx with export const nav = () => <nav>Nav</nav>; in nav folder and export default function Page() { return <main>Content</main>; } in content folder

Solution

1. Step 1: Understand parallel route folder naming

   Parallel routes use folder names without parentheses to define slots, e.g., nav and content.

2. Step 2: Match slot export and default export

   In nav folder, export export const nav for the slot; in content folder, export default the main content.

3. Step 3: Verify options

   Folders: app/nav/page.tsx and app/content/page.tsx with export const nav = () => <nav>Nav</nav>; in nav folder and export default function Page() { return <main>Content</main>; } in content folder correctly uses folders app/nav and app/content with proper exports.

4. Final Answer:

   Folders: app/nav/page.tsx and app/content/page.tsx with export const nav and default export in content -> Option D

5. Quick Check:

   Folder names match slot names without parentheses [OK]

Hint: Use folder names matching slot names without parentheses [OK]

Common Mistakes:

• Using parentheses in folder names for slots
• Exporting slots as default exports
• Mixing slot export and default export roles