Context provider in React - Performance & Optimization

Performance: Context provider

MEDIUM IMPACT

This affects interaction responsiveness and rendering speed by controlling how many components re-render when context changes.

Sharing global state with many components

React

const MyContext = React.createContext();

function App() {
  const [count, setCount] = React.useState(0);
  const value = React.useMemo(() => ({ count, setCount }), [count, setCount]);

  return (
    <MyContext.Provider value={value}>
      <ComponentA />
      <ComponentB />
    </MyContext.Provider>
  );
}

Memoizing the context value prevents unnecessary re-renders of consumers when unrelated state changes occur.

📈 Performance GainReduces re-renders to only when count changes, improving INP and reducing CPU work.

Sharing global state with many components

React

const MyContext = React.createContext();

function App() {
  const [count, setCount] = React.useState(0);
  const value = { count, setCount };

  return (
    <MyContext.Provider value={value}>
      <ComponentA />
      <ComponentB />
    </MyContext.Provider>
  );
}

// ComponentA and ComponentB consume context
// but value object is recreated on every render

The context value object is recreated on every render causing all consumers to re-render even if count did not change.

📉 Performance CostTriggers re-render of all consumers on every parent render, increasing INP and CPU usage.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Context value recreated every render	Many re-renders of consumers	Multiple reflows if layout changes	High paint cost due to frequent updates	[X] Bad
Memoized context value with stable reference	Re-renders only on actual value change	Minimal reflows	Lower paint cost	[OK] Good

Rendering Pipeline

When context value changes, React schedules re-render for all consuming components. If the value changes frequently or unnecessarily, it causes many re-renders, increasing layout and paint work.

→React Reconciliation

→Layout

→Paint

⚠️ BottleneckReact Reconciliation due to excessive re-renders triggered by context value changes

Core Web Vital Affected

INP

This affects interaction responsiveness and rendering speed by controlling how many components re-render when context changes.

Optimization Tips

1Memoize context value objects to avoid unnecessary re-renders.

2Split context into smaller providers to limit consumer updates.

3Avoid passing new object or function references as context value on every render.

Performance Quiz - 3 Questions

What causes unnecessary re-renders in React context consumers?

A Recreating the context value object on every render

B Using useMemo to memoize the context value

C Passing primitive values as context

D Using React.StrictMode

DevTools: React DevTools Profiler

How to check: Record a profiling session while interacting with the app. Look for frequent re-renders of context consumers when no visible changes occur.

What to look for: Excessive re-renders of components consuming context indicate poor context value memoization.

Practice

1. What is the main purpose of a Context.Provider in React?

easy

A. To share data with all components inside its tree without passing props manually

B. To create a new React component

C. To handle component state locally

D. To style components globally

Solution

1. Step 1: Understand what Context.Provider does

   It allows sharing data to all nested components without passing props down manually.

2. Step 2: Compare options

   Only To share data with all components inside its tree without passing props manually describes this sharing behavior correctly; others describe unrelated tasks.

3. Final Answer:

   To share data with all components inside its tree without passing props manually -> Option A

4. Quick Check:

   Context.Provider shares data = A [OK]

Hint: Context.Provider shares data down component tree [OK]

Common Mistakes:

• Thinking Provider creates components
• Confusing Provider with state management
• Assuming Provider styles components

2. Which of the following is the correct way to create a context and provide a value in React?

easy

A. const MyContext = React.createContext(); ...

B. const MyContext = React.useContext(); ...

C. const MyContext = React.createProvider(); ...

D. const MyContext = React.createContext(); ...

Solution

1. Step 1: Identify correct context creation method

   React.createContext() is the correct method to create a context.

2. Step 2: Confirm correct usage of Provider

   Provider uses a value prop to share data; Consumer does not accept value prop directly.

3. Final Answer:

   const MyContext = React.createContext(); <MyContext.Provider value={data}>...</MyContext.Provider> -> Option D

4. Quick Check:

   createContext + Provider with value = D [OK]

Hint: Use React.createContext() and Provider with value prop [OK]

Common Mistakes:

• Using React.useContext() to create context
• Trying React.createProvider() which doesn't exist
• Passing value to Consumer instead of Provider

3. Given the code below, what will be rendered inside DisplayUser component?

const UserContext = React.createContext();

function DisplayUser() {
  const user = React.useContext(UserContext);
  return <div>Hello, {user.name}!</div>;
}

function App() {
  return (
    <UserContext.Provider value={{ name: 'Alice' }}>
      <DisplayUser />
    </UserContext.Provider>
  );
}

medium

A. Hello, undefined!

B. Error: useContext must be inside a Provider

C. Hello, Alice!

D. Hello, {user.name}!

Solution

1. Step 1: Check Provider value

   The Provider passes an object with name 'Alice' as value.

2. Step 2: useContext reads the value

   DisplayUser uses useContext to get the user object and accesses user.name which is 'Alice'.

3. Final Answer:

   Hello, Alice! -> Option C

4. Quick Check:

   useContext reads Provider value = B [OK]

Hint: useContext gets value from nearest Provider [OK]

Common Mistakes:

• Assuming useContext returns undefined without Provider
• Thinking useContext returns the whole context object, not value
• Confusing JSX output with raw code

4. Identify the error in the following React code using Context Provider:

const ThemeContext = React.createContext();

function App() {
  return (
    <ThemeContext.Provider>
      <Content />
    </ThemeContext.Provider>
  );
}

function Content() {
  const theme = React.useContext(ThemeContext);
  return <div>Theme is {theme}</div>;
}

medium

A. Provider is missing the required value prop

B. useContext is used incorrectly outside Provider

C. ThemeContext should be created with React.useContext()

D. Content component should not use useContext

Solution

1. Step 1: Check Provider usage

   The Provider must have a value prop to supply data to consumers.

2. Step 2: Identify missing value prop

   In the code, <ThemeContext.Provider> lacks value, so useContext gets undefined.

3. Final Answer:

   Provider is missing the required value prop -> Option A

4. Quick Check:

   Provider needs value prop = C [OK]

Hint: Provider always needs a value prop [OK]

Common Mistakes:

• Forgetting to pass value to Provider
• Confusing createContext with useContext
• Thinking useContext can't be inside Provider tree

5. You want to share a user object and a function to update it across many components using React Context. Which approach correctly combines these in a single context provider?

hard

A. Create two separate contexts, one for user and one for setUser; use two Providers

B. Create context with React.createContext(); provide value={{ user, setUser }}; consume with useContext

C. Pass user as value and call setUser directly inside components without context

D. Use useState inside each component instead of context

Solution

1. Step 1: Understand combining data and updater in context

   Context value can be an object holding both user data and setUser function.

2. Step 2: Confirm correct usage

   Providing value={{ user, setUser }} allows any component to read user and update it via setUser.

3. Final Answer:

   Create context with React.createContext(); provide value={{ user, setUser }}; consume with useContext -> Option B

4. Quick Check:

   Combine data and updater in one context value = A [OK]

Hint: Put data and updater together in context value object [OK]

Common Mistakes:

• Creating multiple contexts unnecessarily
• Calling setUser without context
• Using local state instead of shared context