Multiple effects in a component in React - Performance & Optimization

Performance: Multiple effects in a component

MEDIUM IMPACT

This affects the interaction responsiveness and rendering speed by controlling how many times React runs side effects and triggers updates.

Running multiple side effects in a React component

React

function MyComponent() {
  React.useEffect(() => {
    // fetch data
    // update document title
    // add event listener
  }, []);
  return <div>Content</div>;
}

Combining related effects into one reduces the number of effect executions and reflows.

📈 Performance GainSingle effect execution and 1 reflow on mount

Running multiple side effects in a React component

React

function MyComponent() {
  React.useEffect(() => {
    // fetch data
  }, []);
  React.useEffect(() => {
    // update document title
  }, []);
  React.useEffect(() => {
    // add event listener
  }, []);
  return <div>Content</div>;
}

All effects run independently and may cause multiple re-renders and layout recalculations, increasing CPU and rendering cost.

📉 Performance CostTriggers 3 effect executions and potentially 3 reflows on mount

Performance Comparison

Pattern	Effect Executions	Reflows	Paint Cost	Verdict
Multiple separate useEffect calls	3	3	High	[X] Bad
Single combined useEffect call	1	1	Low	[OK] Good

Rendering Pipeline

React runs effects after rendering. Multiple effects cause multiple effect callbacks, each potentially triggering state updates and reflows.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckMultiple effect executions causing repeated layout recalculations

Core Web Vital Affected

INP

This affects the interaction responsiveness and rendering speed by controlling how many times React runs side effects and triggers updates.

Optimization Tips

1Limit the number of useEffect hooks by combining related logic.

2Use dependency arrays to avoid unnecessary effect runs.

3Avoid side effects that trigger layout changes multiple times on mount.

Performance Quiz - 3 Questions

What is a performance downside of having many separate useEffect hooks in a React component?

A They reduce the bundle size significantly.

B They can cause multiple reflows and slow down rendering.

C They improve initial load time by parallelizing effects.

D They prevent any re-rendering after mount.

DevTools: Performance

How to check: Record a performance profile while mounting the component and look for multiple effect callbacks and layout recalculations.

What to look for: Multiple 'useEffect' callbacks and repeated 'Layout' events indicate inefficiency.

Practice

1. What is the main benefit of using multiple useEffect hooks in a React component?

easy

A. It combines all side effects into one function for faster execution.

B. It separates different side effects for better readability and maintenance.

C. It prevents the component from rendering multiple times.

D. It automatically optimizes the component's performance.

Solution

1. Step 1: Understand the purpose of multiple useEffect hooks

   Multiple useEffect hooks allow you to separate different side effects logically in a component.

2. Step 2: Recognize the benefit of separation

   This separation makes the component easier to read and maintain because each effect handles a specific task.

3. Final Answer:

   It separates different side effects for better readability and maintenance. -> Option B

4. Quick Check:

   Multiple effects = separation and clarity [OK]

Hint: Multiple effects separate tasks for clarity and easier updates [OK]

Common Mistakes:

• Thinking multiple effects combine tasks into one
• Believing multiple effects prevent re-renders
• Assuming multiple effects auto-optimize performance

2. Which of the following is the correct syntax to use two separate useEffect hooks in a React functional component?

easy

A. useEffect(() => { /* effect 1 */ }, []); useEffect(() => { /* effect 2 */ }, []);

B. useEffect(() => { /* effect 1 */ }, []) useEffect(() => { /* effect 2 */ }, []);

C. useEffect(() => { /* effect 1 */ } useEffect(() => { /* effect 2 */ });

D. useEffect(() => { /* effect 1 */ }, [] && []) useEffect(() => { /* effect 2 */ }, []);

Solution

1. Step 1: Recall correct useEffect syntax

   The useEffect hook takes a function and a dependency array as arguments, separated by a comma.

2. Step 2: Identify correct separation of two hooks

   Two separate useEffect hooks should be called one after another, each with its own function and dependency array, ending with semicolons.

3. Final Answer:

   useEffect(() => { /* effect 1 */ }, []); useEffect(() => { /* effect 2 */ }, []); -> Option A

4. Quick Check:

   Separate hooks with own deps and semicolons [OK]

Hint: Each useEffect needs its own function and dependency array [OK]

Common Mistakes:

• Using commas instead of semicolons between hooks
• Combining dependency arrays incorrectly
• Omitting dependency arrays causing unwanted runs

3. Consider this React component code:

function Example({ count }) {
  useEffect(() => {
    console.log('Effect A:', count);
  }, [count]);

  useEffect(() => {
    console.log('Effect B: component mounted');
  }, []);

  return <div>Count: {count}</div>;
}

What will be logged when the component first mounts with count = 5?

medium

A. Effect B: component mounted only

B. Effect B: component mountedEffect A: 5

C. Effect A: 5 only

D. Effect A: 5Effect B: component mounted

Solution

1. Step 1: Understand useEffect execution order on mount

   All useEffect hooks run after the first render. They run in the order they appear in code.

2. Step 2: Identify the order of console logs

   The first useEffect logs 'Effect A: 5', the second logs 'Effect B: component mounted'. So logs appear in code order.

3. Final Answer:

   Effect A: 5
   Effect B: component mounted -> Option D

4. Quick Check:

   Effects run in code order on mount [OK]

Hint: Effects run in code order after first render [OK]

Common Mistakes:

• Assuming effects run in reverse order
• Thinking effects run before render
• Confusing dependency arrays impact on first run

4. What is wrong with this React component using multiple effects?

function Demo({ value }) {
  useEffect(() => {
    console.log('Effect 1:', value);
  }, [value]);

  useEffect(() => {
    console.log('Effect 2');
  });

  return <div>Value: {value}</div>;
}

medium

A. The first useEffect should not have a dependency array.

B. You cannot use two useEffect hooks in one component.

C. The second useEffect has no dependency array, so it runs after every render.

D. The console.log statements are invalid inside useEffect.

Solution

1. Step 1: Check dependency arrays in useEffect hooks

   The first useEffect has a dependency array [value], so it runs only when value changes.

2. Step 2: Analyze second useEffect without dependency array

   The second useEffect has no dependency array, so it runs after every render, which might be unintended.

3. Final Answer:

   The second useEffect has no dependency array, so it runs after every render. -> Option C

4. Quick Check:

   Missing deps means effect runs every render [OK]

Hint: Always add dependency array to control effect runs [OK]

Common Mistakes:

• Thinking multiple useEffects are not allowed
• Ignoring missing dependency arrays
• Believing console.log is invalid inside useEffect

5. You want to fetch user data when the component mounts and also update the document title whenever the user's name changes. How should you organize your useEffect hooks?

hard

A. Use two separate useEffect hooks: one with empty deps for fetch, one with [user.name] for title.

B. Use one useEffect to fetch data and update title together with both dependencies.

C. Use one useEffect with no dependencies to do both tasks on every render.

D. Use two useEffect hooks both with empty dependency arrays.

Solution

1. Step 1: Separate concerns with multiple useEffect hooks

   Fetching data should happen once on mount, so useEffect with empty dependency array is best.

2. Step 2: Update document title when user.name changes

   Use a separate useEffect with [user.name] dependency to update title only when name changes.

3. Final Answer:

   Use two separate useEffect hooks: one with empty deps for fetch, one with [user.name] for title. -> Option A

4. Quick Check:

   Separate effects by task and dependencies [OK]

Hint: Separate effects by when and why they run [OK]

Common Mistakes:

• Combining unrelated tasks in one effect
• Missing dependencies causing stale updates
• Running fetch on every render unintentionally