Passing props to components in React - Performance & Optimization

Performance: Passing props to components

MEDIUM IMPACT

Passing props affects rendering speed and update efficiency of React components.

Passing all props including unused ones to child components

React

function Parent() {
  const name = 'Alice';
  return <Child name={name} />;
}

function Child({name}) {
  return <div>{name}</div>;
}

Passing only needed props reduces re-render triggers and CPU usage.

📈 Performance Gainreduces re-renders and improves input responsiveness (INP)

Passing all props including unused ones to child components

React

function Parent() {
  const data = {name: 'Alice', age: 30, city: 'NYC'};
  return <Child {...data} />;
}

function Child(props) {
  return <div>{props.name}</div>;
}

Passing all props causes Child to re-render even if only some props are used or changed.

📉 Performance Costtriggers unnecessary re-renders and increases CPU work on updates

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Passing all props indiscriminately	Same DOM nodes reused	Multiple re-renders triggered	Paint cost depends on re-rendered nodes	[X] Bad
Passing only necessary props	Same DOM nodes reused	Minimal re-renders	Lower paint cost due to fewer updates	[OK] Good

Rendering Pipeline

Props flow from parent to child components triggering React's render and reconciliation process. Unnecessary or large props cause more frequent and heavier renders.

→React Reconciliation

→Render

→Commit

⚠️ BottleneckReact Reconciliation stage where props changes cause re-rendering

Core Web Vital Affected

INP

Passing props affects rendering speed and update efficiency of React components.

Optimization Tips

1Pass only the props a component needs to avoid extra re-renders.

2Avoid passing new object or function props unless necessary or memoized.

3Use React.memo or useCallback to optimize prop-driven re-renders.

Performance Quiz - 3 Questions

What is a performance benefit of passing only necessary props to a React component?

A Triggers more layout shifts

B Increases bundle size

C Reduces unnecessary re-renders and improves responsiveness

D Blocks rendering longer

DevTools: React DevTools Profiler

How to check: Record interactions and look for unnecessary re-renders of components when props change.

What to look for: Components re-rendering without prop changes or with unchanged relevant props indicate inefficiency.

Practice

1. What is the main purpose of props in React components?

easy

A. To handle user events like clicks

B. To store local state inside a component

C. To pass data from a parent component to a child component

D. To style components with CSS

Solution

1. Step 1: Understand the role of props

   Props are used to send data from one component to another, specifically from parent to child.

2. Step 2: Differentiate props from other React features

   State stores local data, events handle interactions, and CSS styles components, but props specifically pass data down.

3. Final Answer:

   To pass data from a parent component to a child component -> Option C

4. Quick Check:

   Props = data passing [OK]

Hint: Props always send data down from parent to child [OK]

Common Mistakes:

• Confusing props with state
• Thinking props handle events
• Believing props style components

2. Which of the following is the correct way to pass a prop named title with value "Hello" to a component Header?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall JSX prop syntax

   Props are passed like HTML attributes: name="value" or name={expression}.

2. Step 2: Check each option

   uses correct string syntax.

   misses quotes around string.

   uses invalid quotes.

   uses colon which is invalid in JSX.

3. Final Answer:

   <Header title="Hello" /> -> Option B

4. Quick Check:

   Props look like HTML attributes [OK]

Hint: Use quotes for string props in JSX [OK]

Common Mistakes:

• Omitting quotes for string values
• Using colons instead of equals
• Adding extra quotes around prop names

3. What will be rendered by this React component?

function Greeting(props) {
  return <h1>Hello, {props.name}!</h1>;
}

// Usage:
<Greeting name="Alice" />

medium

A. Hello, Alice!

B. Hello, {props.name}!

C. Hello, name!

D. Error: props is undefined

Solution

1. Step 1: Understand how props are used inside the component

   The component receives props and accesses props.name to display the name.

2. Step 2: Check the usage of the component

   The component is called with name="Alice", so props.name is "Alice".

3. Final Answer:

   <h1>Hello, Alice!</h1> -> Option A

4. Quick Check:

   props.name = Alice [OK]

Hint: Props values replace placeholders inside JSX [OK]

Common Mistakes:

• Printing literal {props.name} instead of value
• Forgetting to pass the prop
• Assuming props is undefined

4. Identify the error in this code snippet:

function Welcome(props) {
  return <h2>Welcome, {props.user}!</h2>;
}

// Usage:
<Welcome user=John />

medium

A. Missing quotes around string prop value 'John'

B. Props object is not passed correctly

C. Component name should be lowercase

D. JSX tags are not closed properly

Solution

1. Step 1: Check the prop usage in JSX

   In JSX, string prop values must be quoted, e.g., user="John".

2. Step 2: Identify the error in usage

   The code uses user=John without quotes, causing a syntax error.

3. Final Answer:

   Missing quotes around string prop value 'John' -> Option A

4. Quick Check:

   String props need quotes [OK]

Hint: Always quote string props in JSX [OK]

Common Mistakes:

• Omitting quotes for string props
• Using lowercase component names
• Leaving JSX tags unclosed

5. Given this parent and child component code, what will be the output?

function Child({ message }) {
  return <p>Message: {message || 'No message'}</p>;
}

function Parent() {
  const msg = '';
  return <Child message={msg} />;
}

hard

A. Message:

B. Error: message prop missing

C. Message: undefined

D. Message: No message

Solution

1. Step 1: Analyze the prop value passed

   The parent passes msg which is an empty string '' as the message prop.

2. Step 2: Understand the child component's rendering logic

   The child uses {message || 'No message'}. Since empty string is falsy, it falls back to 'No message'.

3. Final Answer:

   <p>Message: No message</p> -> Option D

4. Quick Check:

   Falsy empty string triggers fallback [OK]

Hint: Falsy props like '' use fallback values in JSX [OK]

Common Mistakes:

• Assuming empty string is truthy
• Expecting empty string to display as is
• Thinking missing prop causes error here