Avoiding prop drilling in React - Performance & Optimization

Performance: Avoiding prop drilling

MEDIUM IMPACT

This affects interaction responsiveness and rendering speed by reducing unnecessary component re-renders and deep prop passing.

Passing data through many nested components

React

const CountContext = React.createContext();
function Parent() {
  const [count, setCount] = React.useState(0);
  return (
    <CountContext.Provider value={{ count, setCount }}>
      <Child1 />
    </CountContext.Provider>
  );
}
function Child1() {
  return <Child2 />;
}
function Child2() {
  return <Child3 />;
}
function Child3() {
  const { count, setCount } = React.useContext(CountContext);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

Using context avoids passing props through intermediate components, reducing unnecessary re-renders.

📈 Performance GainReduces re-renders to only components consuming context, improving input responsiveness (INP).

Passing data through many nested components

React

function Parent() {
  const [count, setCount] = React.useState(0);
  return <Child1 count={count} setCount={setCount} />;
}
function Child1({ count, setCount }) {
  return <Child2 count={count} setCount={setCount} />;
}
function Child2({ count, setCount }) {
  return <Child3 count={count} setCount={setCount} />;
}
function Child3({ count, setCount }) {
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

Passing props through many layers causes all intermediate components to re-render even if they don't use the data directly.

📉 Performance CostTriggers multiple re-renders and increases interaction latency (INP) as each component updates.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Prop drilling through many components	No extra DOM nodes	Multiple re-renders of intermediate components	Increased paint due to re-renders	[X] Bad
Using React Context to share data	No extra DOM nodes	Re-renders only consuming components	Reduced paint cost	[OK] Good

Rendering Pipeline

Prop drilling causes many components to re-render and recalculate styles and layout unnecessarily. Using context limits updates to only components that consume the data.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution due to many component re-renders

Core Web Vital Affected

INP

This affects interaction responsiveness and rendering speed by reducing unnecessary component re-renders and deep prop passing.

Optimization Tips

1Avoid passing props through many nested components to reduce re-renders.

2Use React Context or state management to share data efficiently.

3Limit component re-renders to improve input responsiveness (INP).

Performance Quiz - 3 Questions

What is a main performance problem caused by prop drilling in React?

A Unnecessary re-renders of intermediate components

B Adding extra DOM nodes

C Slower CSS selector matching

D Blocking network requests

DevTools: React DevTools and Performance panel

How to check: Use React DevTools Profiler to record interactions and see which components re-render. Use Performance panel to check scripting time during interactions.

What to look for: Look for many unnecessary re-renders in intermediate components and long scripting times indicating slow input responsiveness.

Practice

1. What is the main problem that prop drilling causes in React applications?

easy

A. Not using hooks properly in functional components

B. Using too many state variables in a single component

C. Rendering components multiple times unnecessarily

D. Passing props through many layers even if intermediate components don't need them

Solution

1. Step 1: Understand what prop drilling means

   Prop drilling happens when props are passed down through many components that don't use them, just to reach a deeply nested component.

2. Step 2: Identify the main issue caused by prop drilling

   This makes the code harder to maintain and understand because many components receive props they don't need.

3. Final Answer:

   Passing props through many layers even if intermediate components don't need them -> Option D

4. Quick Check:

   Prop drilling = Passing props through many layers [OK]

Hint: Prop drilling means unnecessary passing props down layers [OK]

Common Mistakes:

• Confusing prop drilling with state management issues
• Thinking prop drilling is about rendering performance
• Believing prop drilling is caused by hooks misuse

2. Which of the following is the correct way to create a React Context to avoid prop drilling?

easy

A. const MyContext = React.useContext();

B. const MyContext = React.createContext();

C. const MyContext = React.useState();

D. const MyContext = React.useEffect();

Solution

1. Step 1: Recall the React API for creating context

   React provides createContext to create a context object for sharing data.

2. Step 2: Identify the correct syntax

   The correct syntax is const MyContext = React.createContext();. The other options are hooks used for different purposes.

3. Final Answer:

   const MyContext = React.createContext(); -> Option B

4. Quick Check:

   createContext() creates context [OK]

Hint: Use createContext() to make a context object [OK]

Common Mistakes:

• Using useContext() to create context instead of consume it
• Confusing useState() or useEffect() with context creation
• Missing parentheses after createContext

3. Given this code snippet, what will be the output inside Child component?

const MyContext = React.createContext('default');

function Parent() {
  return (
    
      
    
  );
}

function Child() {
  const value = React.useContext(MyContext);
  return <div>{value}</div>;
}

medium

A. <div>hello</div>

B. <div>default</div>

C. <div>undefined</div>

D. Error: useContext must be inside a Provider

Solution

1. Step 1: Understand the context default and provider value

   The context default is 'default', but the Parent component provides the value 'hello' via MyContext.Provider.

2. Step 2: Determine what useContext returns inside Child

   The Child component uses useContext(MyContext), so it receives the nearest provider's value, which is 'hello'.

3. Final Answer:

   <div>hello</div> -> Option A

4. Quick Check:

   useContext returns nearest Provider value [OK]

Hint: useContext gets nearest Provider value, not default [OK]

Common Mistakes:

• Assuming default value is always used
• Thinking useContext returns undefined without explicit value
• Confusing Provider value with component props

4. Identify the error in this code that tries to avoid prop drilling using React Context:

const MyContext = React.createContext();

function Parent() {
  const value = 'data';
  return <Child />;
}

function Child() {
  const value = React.useContext(MyContext);
  return <div>{value}</div>;
}

medium

A. MyContext.Provider is missing around Child component

B. useContext is used incorrectly inside Child

C. createContext must have a default value

D. Parent should pass value as a prop to Child

Solution

1. Step 1: Check if Provider wraps components needing context

   The Parent component returns <Child /> without wrapping it in MyContext.Provider.

2. Step 2: Understand useContext requires Provider to get value

   Without a Provider, useContext(MyContext) returns the default value, which is undefined here, likely not intended.

3. Final Answer:

   MyContext.Provider is missing around Child component -> Option A

4. Quick Check:

   Provider missing = context value undefined [OK]

Hint: Always wrap consumers with Provider to supply context [OK]

Common Mistakes:

• Thinking createContext must have default value
• Believing useContext works without Provider
• Confusing prop passing with context usage

5. You have a deeply nested component tree where ThemeContext provides a theme string. You want to avoid prop drilling and also allow components to update the theme. Which approach correctly combines context and state to achieve this?

hard

A. Use multiple contexts for theme and setTheme separately and pass them as props

B. Pass theme as a prop from top to bottom and use useState only in the deepest component

C. Create ThemeContext with createContext, provide {theme, setTheme} from a state in a top-level component, and consume both in nested components

D. Store theme in a global variable and read it directly in nested components

Solution

1. Step 1: Understand how to share state and updater via context

   To avoid prop drilling and allow updates, the context should provide both the current value and a function to update it.

2. Step 2: Use createContext and provide state and setter from top-level

   Create a context with createContext(), then in a top-level component use useState to hold theme and pass both theme and setTheme in the Provider's value.

3. Step 3: Consume both theme and setTheme in nested components

   Nested components use useContext to get both and can read or update the theme without prop drilling.

4. Final Answer:

   Create ThemeContext with createContext, provide {theme, setTheme} from a state in a top-level component, and consume both in nested components -> Option C

5. Quick Check:

   Context with state and setter avoids prop drilling [OK]

Hint: Provide state and setter in context value to update data [OK]

Common Mistakes:

• Passing only value without setter in context
• Using global variables instead of React state
• Passing props through many layers instead of context