Shared state across layouts in NextJS - Performance & Optimization

Performance: Shared state across layouts

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by how state is managed and shared between layouts and pages.

Sharing user authentication state across multiple layouts in a Next.js app

NextJS

import { createContext, useContext, useState, useEffect } from 'react';

const UserContext = createContext(null);

export function UserProvider({ children }) {
  const [user, setUser] = useState(null);
  useEffect(() => {
    fetch('/api/auth').then(res => res.json()).then(data => setUser(data.user));
  }, []);
  return <UserContext.Provider value={user}>{children}</UserContext.Provider>;
}

// Wrap root layout with <UserProvider> and consume user via useContext in nested layouts

Centralizes user state fetching and sharing via React Context, avoiding repeated fetches and re-renders.

📈 Performance GainSingle data fetch and fewer re-renders improve INP and reduce blocking during interactions.

Sharing user authentication state across multiple layouts in a Next.js app

NextJS

import { useState, useEffect } from 'react';

export default function Layout({ children }) {
  const [user, setUser] = useState(null);
  useEffect(() => {
    fetch('/api/auth').then(res => res.json()).then(data => setUser(data.user));
  }, []);
  return <>{children}</>;
}

// Each layout fetches user separately causing repeated requests

Each layout fetches and manages user state independently, causing repeated network requests and multiple re-renders.

📉 Performance CostTriggers multiple data fetches and re-renders, increasing INP and blocking interaction responsiveness.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Independent state per layout	Multiple fetches and state updates	Multiple reflows per layout	Higher paint cost due to repeated updates	[X] Bad
Centralized shared state via Context	Single fetch and state update	Single reflow for shared state change	Lower paint cost with fewer updates	[OK] Good

Rendering Pipeline

Shared state flows from the root provider through React context to nested layouts, minimizing repeated data fetching and re-rendering.

→JavaScript Execution

→React Reconciliation

→Paint

→Composite

⚠️ BottleneckReact Reconciliation due to unnecessary re-renders when state is duplicated or fetched multiple times.

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by how state is managed and shared between layouts and pages.

Optimization Tips

1Centralize shared state to avoid repeated data fetching.

2Use React Context or server components to share state efficiently.

3Minimize re-renders by keeping shared state at the highest common ancestor.

Performance Quiz - 3 Questions

What is the main performance problem when each layout fetches shared state independently?

A Multiple network requests and repeated re-renders

B Too many DOM nodes created

C CSS selector complexity increases

D JavaScript bundle size grows significantly

DevTools: Performance

How to check: Record a performance profile while navigating layouts; look for repeated data fetching and multiple React renders.

What to look for: Multiple network requests for the same data and repeated React component renders indicate poor shared state management.

Practice

1. What is the main benefit of sharing state across layouts in Next.js?

easy

A. It allows multiple layouts and pages to access the same data easily.

B. It improves the styling of components automatically.

C. It speeds up the server response time by caching data.

D. It prevents users from navigating between pages.

Solution

1. Step 1: Understand the purpose of shared state

   Shared state means multiple parts of the app can use the same data without duplication.

2. Step 2: Identify the benefit in Next.js layouts

   Sharing state across layouts lets pages and layouts access common data easily, improving consistency.

3. Final Answer:

   It allows multiple layouts and pages to access the same data easily. -> Option A

4. Quick Check:

   Shared state = common data access [OK]

Hint: Shared state means one data source for many layouts [OK]

Common Mistakes:

• Confusing shared state with styling or caching
• Thinking shared state blocks navigation
• Assuming shared state only affects server speed

2. Which of the following is the correct way to provide shared state in Next.js layouts using React Context?

easy

A. Import state from a CSS file and use it in layouts.

B. Wrap the root layout with a Context Provider component.

C. Use getServerSideProps to pass state to layouts.

D. Add state variables directly inside each layout without a provider.

Solution

1. Step 1: Recall React Context usage

   React Context requires wrapping components with a Provider to share state.

2. Step 2: Apply to Next.js layouts

   Wrapping the root layout with the Provider shares state across all nested layouts and pages.

3. Final Answer:

   Wrap the root layout with a Context Provider component. -> Option B

4. Quick Check:

   Provider wraps root layout = shared state [OK]

Hint: Always wrap root layout with Provider for shared state [OK]

Common Mistakes:

• Trying to add state without a Provider
• Using server props instead of Context for shared state
• Confusing CSS imports with state management

3. Given this code snippet in a Next.js app, what will be the output when clicking the button in any nested layout?

const CountContext = React.createContext();

function CountProvider({ children }) {
  const [count, setCount] = React.useState(0);
  return (
    <CountContext.Provider value={{ count, setCount }}>
      {children}
    </CountContext.Provider>
  );
}

function Button() {
  const { count, setCount } = React.useContext(CountContext);
  return <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>;
}

// Root layout wraps children with <CountProvider>

medium

A. Clicking the button increases the count visible in all layouts sharing the context.

B. Clicking the button only updates the count inside the Button component itself.

C. Clicking the button causes a runtime error because context is not provided.

D. Clicking the button resets the count to zero every time.

Solution

1. Step 1: Understand context sharing

   The CountProvider shares count state via context to all nested components.

2. Step 2: Analyze button behavior

   Clicking the button calls setCount to increase count, updating all components using the context.

3. Final Answer:

   Clicking the button increases the count visible in all layouts sharing the context. -> Option A

4. Quick Check:

   Context state update = shared count change [OK]

Hint: Context updates reflect everywhere wrapped by Provider [OK]

Common Mistakes:

• Thinking state updates are local to Button only
• Assuming missing Provider causes error here
• Believing count resets on each click

4. You have wrapped your root layout with a Context Provider, but nested layouts cannot access the shared state. What is the most likely cause?

medium

A. You placed the Provider inside a nested layout instead of the root layout.

B. You used React.useState instead of React.useContext in the root layout.

C. You forgot to use the custom hook or React.useContext inside nested layouts.

D. You imported the context from a CSS file instead of a JavaScript file.

Solution

1. Step 1: Check how nested layouts access context

   Nested layouts must use React.useContext or a custom hook to read shared state.

2. Step 2: Identify common mistake

   Forgetting to call useContext means no access to the shared data, even if Provider is correct.

3. Final Answer:

   You forgot to use the custom hook or React.useContext inside nested layouts. -> Option C

4. Quick Check:

   Missing useContext call = no access [OK]

Hint: Use useContext hook inside nested layouts to access shared state [OK]

Common Mistakes:

• Placing Provider too deep, not at root
• Confusing useState with useContext
• Importing context incorrectly from non-JS files

5. You want to share a user authentication state across multiple layouts in Next.js. Which approach correctly combines shared state with server-side data fetching to keep the user logged in?

hard

A. Use local component state in each layout to store user info fetched from the server on mount.

B. Store user data only in getServerSideProps and pass it as props to each layout without using Context.

C. Save user info in a CSS variable and read it in layouts for shared state.

D. Wrap the root layout with a Context Provider that holds user state, and update it client-side after fetching user info in a server action or API route.

Solution

1. Step 1: Understand combining server data with shared state

   User info fetched server-side should be stored in a shared client state for consistent access.

2. Step 2: Use Context Provider at root layout

   Wrapping root layout with a Provider holding user state allows all layouts to access and update it.

3. Step 3: Update state client-side after server fetch

   Fetching user info via server actions or API routes and updating context keeps user logged in across layouts.

4. Final Answer:

   Wrap the root layout with a Context Provider that holds user state, and update it client-side after fetching user info in a server action or API route. -> Option D

5. Quick Check:

   Context + server fetch = shared auth state [OK]

Hint: Use Context Provider plus server fetch to share auth state [OK]

Common Mistakes:

• Passing user data only via props without shared state
• Using local state per layout causing inconsistent user info
• Trying to store user info in CSS or non-JS files