Conditional routes in NextJS - Performance & Optimization

Performance: Conditional routes

MEDIUM IMPACT

Conditional routes affect page load speed and interaction responsiveness by controlling which pages or components load based on conditions.

Loading pages conditionally based on user authentication

NextJS

import dynamic from 'next/dynamic';
const Dashboard = dynamic(() => import('./Dashboard'));
const Login = dynamic(() => import('./Login'));

export default function Page() {
  if (user.isLoggedIn) {
    return <Dashboard />;
  } else {
    return <Login />;
  }
}

Dynamic imports load only the needed component, reducing initial bundle size and speeding up page load.

📈 Performance GainSaves 100-200KB in initial bundle, reducing LCP by up to 300ms.

Loading pages conditionally based on user authentication

NextJS

export default function Page() {
  if (user.isLoggedIn) {
    return <Dashboard />;
  } else {
    return <Login />;
  }
}

Both Dashboard and Login components are imported and bundled regardless of user state, increasing bundle size and slowing initial load.

📉 Performance CostAdds unnecessary KBs to bundle, increasing LCP by 200-300ms on slow networks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Static import of all routes	Low to medium (depends on components)	1 per route render	Medium due to larger bundle	[X] Bad
Dynamic import with conditional rendering	Low (only needed components)	1 per route render	Low due to smaller bundle	[OK] Good

Rendering Pipeline

Conditional routes affect the loading and rendering stages by controlling which components are fetched and rendered based on conditions, impacting the critical rendering path.

→JavaScript Parsing

→Code Fetching

→Layout

→Paint

⚠️ BottleneckJavaScript Parsing and Code Fetching due to unnecessary component loading

Core Web Vital Affected

LCP

Conditional routes affect page load speed and interaction responsiveness by controlling which pages or components load based on conditions.

Optimization Tips

1Use dynamic imports to load route components only when needed.

2Avoid importing all routes statically to keep bundles small.

3Test route loading impact with DevTools Performance and Network panels.

Performance Quiz - 3 Questions

What is the main performance benefit of using dynamic imports for conditional routes in Next.js?

A Reduces initial bundle size by loading only needed components

B Improves CSS loading speed

C Eliminates all JavaScript parsing

D Preloads all routes to avoid delays

DevTools: Performance

How to check: Record a page load in DevTools Performance panel, then check the 'Main' thread for scripting and rendering times. Use the Network panel to see which JS chunks load.

What to look for: Look for large JS bundles loading unnecessarily and long scripting times that delay LCP.

Practice

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

easy

A. To create static pages only

B. To style pages differently

C. To fetch data from an API

D. To control access and redirect users based on conditions

Solution

1. Step 1: Understand conditional routes concept

   Conditional routes let you decide which users can see certain pages or redirect them elsewhere.

2. Step 2: Identify the purpose in Next.js

   Next.js uses conditional routes mainly to protect pages or redirect users based on login or roles.

3. Final Answer:

   To control access and redirect users based on conditions -> Option D

4. Quick Check:

   Conditional routes = control access [OK]

Hint: Think: Who should see this page? Redirect if no permission. [OK]

Common Mistakes:

• Confusing conditional routes with styling or data fetching
• Thinking conditional routes create static pages
• Believing conditional routes only fetch data

2. Which Next.js hook is commonly used to perform client-side redirects in conditional routes?

easy

A. useState

B. useEffect

C. useRouter

D. useContext

Solution

1. Step 1: Identify hooks for routing

   Next.js provides useRouter to access routing methods like push for redirects.

2. Step 2: Confirm redirect usage

   While useEffect runs side effects, useRouter is needed to actually change routes.

3. Final Answer:

   useRouter -> Option C

4. Quick Check:

   Redirects use useRouter [OK]

Hint: Redirects need router methods, so useRouter is key. [OK]

Common Mistakes:

• Using useState to redirect (it manages state only)
• Confusing useEffect as the hook that changes routes
• Thinking useContext handles routing

3. Given this Next.js component, what will happen if isLoggedIn is false?

import { useRouter } from 'next/router';
import { useEffect } from 'react';

export default function Dashboard() {
  const router = useRouter();
  const isLoggedIn = false;

  useEffect(() => {
    if (!isLoggedIn) {
      router.push('/login');
    }
  }, [isLoggedIn]);

  return <h1>Dashboard</h1>;
}

medium

A. The user is redirected to the /login page

B. The page reloads infinitely

C. The page shows an error

D. The user stays on the Dashboard page

Solution

1. Step 1: Analyze the useEffect condition

   The effect checks if isLoggedIn is false, then calls router.push('/login').

2. Step 2: Understand router.push behavior

   This causes a client-side redirect to the login page when not logged in.

3. Final Answer:

   The user is redirected to the /login page -> Option A

4. Quick Check:

   False login triggers redirect [OK]

Hint: False login triggers router.push to /login. [OK]

Common Mistakes:

• Thinking the user stays on Dashboard despite redirect
• Assuming an error occurs without redirect
• Believing infinite reload happens here

4. Identify the error in this Next.js conditional route code:

import { useRouter } from 'next/router';
import { useEffect } from 'react';

export default function Profile() {
  const router = useRouter();
  const isAuthorized = false;

  if (!isAuthorized) {
    router.push('/unauthorized');
  }

  return <h1>Profile</h1>;
}

medium

A. Calling router.push inside the component body causes an error

B. Missing dependency array in useEffect

C. useRouter is not imported correctly

D. The component returns invalid JSX

Solution

1. Step 1: Check where router.push is called

   router.push is called directly inside the component body, which runs on every render and is not allowed.

2. Step 2: Correct usage with useEffect

   Redirects should be inside useEffect to avoid infinite loops or errors.

3. Final Answer:

   Calling router.push inside the component body causes an error -> Option A

4. Quick Check:

   Redirects must be inside useEffect [OK]

Hint: Put router.push inside useEffect, not directly in component body. [OK]

Common Mistakes:

• Calling router.push directly in component body
• Ignoring useEffect for side effects
• Assuming missing import causes error here

5. You want to create a Next.js page that only logged-in users can access. If the user is not logged in, redirect them to '/login'. Which is the best approach?

1. Use useRouter and useEffect to check login and redirect client-side.
2. Use Next.js middleware to check authentication before rendering.
3. Render a loading state while checking login status.
4. Avoid rendering protected content until login is confirmed.

Which combination correctly applies conditional routing best practice?

hard

A. Only 1 and 2

B. All 1, 2, 3, and 4

C. Only 2 and 4

D. Only 1, 3, and 4

Solution

1. Step 1: Understand client-side and server-side checks

   Client-side redirect with useRouter/useEffect (1) is common, but middleware (2) adds server-side protection.

2. Step 2: Consider user experience

   Showing a loading state (3) and avoiding rendering protected content before login confirmation (4) improve UX and prevent flicker.

3. Step 3: Combine all for best practice

   Using all four ensures secure, smooth conditional routing in Next.js.

4. Final Answer:

   All 1, 2, 3, and 4 -> Option B

5. Quick Check:

   Best practice = all steps combined [OK]

Hint: Combine client, server checks and loading states for best routing. [OK]

Common Mistakes:

• Relying only on client-side redirects
• Skipping loading states causing flicker
• Ignoring server-side middleware protection