Component organization in React - Performance & Optimization

Performance: Component organization

MEDIUM IMPACT

This affects the rendering speed and responsiveness by controlling how React updates and re-renders components.

Splitting UI into components to improve rendering performance

React

function StaticText() {
  return <p>Some static text that never changes</p>;
}

function Counter({ count, onIncrement }) {
  return (
    <>
      <h1>Counter: {count}</h1>
      <button onClick={onIncrement}>Increment</button>
    </>
  );
}

function App() {
  const [count, setCount] = React.useState(0);
  return (
    <div>
      <Counter count={count} onIncrement={() => setCount(count + 1)} />
      <StaticText />
    </div>
  );
}

Separates static and dynamic parts so only Counter re-renders on state change, StaticText stays untouched.

📈 Performance GainReduces re-render scope, lowering paint cost and improving interaction responsiveness

Splitting UI into components to improve rendering performance

React

function App() {
  const [count, setCount] = React.useState(0);
  return (
    <div>
      <h1>Counter: {count}</h1>
      <button onClick={() => setCount(count + 1)}>Increment</button>
      <p>Some static text that never changes</p>
    </div>
  );
}

All UI is in one component, so any state change causes the entire component to re-render, including static parts.

📉 Performance CostTriggers full component re-render and repaint on every state update

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single large component	Many nodes updated on state change	Multiple reflows per update	High paint cost due to full re-render	[X] Bad
Small focused components	Only changed components update DOM	Single or minimal reflows	Lower paint cost, faster updates	[OK] Good

Rendering Pipeline

When state changes, React reconciles the component tree. Smaller, well-organized components limit the number of nodes React must diff and update, reducing layout and paint work.

→Reconciliation

→Layout

→Paint

⚠️ BottleneckReconciliation and Paint stages due to large component re-renders

Core Web Vital Affected

INP

This affects the rendering speed and responsiveness by controlling how React updates and re-renders components.

Optimization Tips

1Split UI into small, focused components to limit re-render scope.

2Keep static UI separate from dynamic parts to avoid unnecessary updates.

3Use React DevTools Profiler to find and fix excessive re-renders.

Performance Quiz - 3 Questions

Why is splitting UI into smaller components better for React performance?

A It limits re-rendering to only components that need updating

B It increases the number of DOM nodes, making updates faster

C It forces React to re-render the entire app every time

D It reduces the bundle size significantly

DevTools: React DevTools and Chrome Performance panel

How to check: Use React DevTools Profiler to record interactions and see which components re-render. Use Chrome Performance to check paint and layout times.

What to look for: Look for minimal component re-renders on state changes and low paint/layout times indicating efficient updates.

Practice

1. What is the main benefit of organizing React components by their role or feature?

easy

A. It makes the app run faster

B. It automatically fixes bugs in the code

C. It reduces the size of the final app bundle

D. It keeps the code clean and easier to maintain

Solution

1. Step 1: Understand component organization purpose

   Organizing components by role or feature helps keep the codebase structured and clean.

2. Step 2: Identify the main benefit

   This organization makes the code easier to read, maintain, and update over time.

3. Final Answer:

   It keeps the code clean and easier to maintain -> Option D

4. Quick Check:

   Clean code = B [OK]

Hint: Think about code clarity and maintenance benefits [OK]

Common Mistakes:

• Confusing organization with app speed
• Assuming organization reduces bundle size
• Believing organization fixes bugs automatically

2. Which of the following is the correct way to define a simple functional React component named Button?

easy

A. function Button() { return Click me; }

B. class Button extends React.Component { render() { return Click me; } }

C. const Button = () => { Click me }

D. function Button() { Click me }

Solution

1. Step 1: Check functional component syntax

   A functional component returns JSX inside the function body using return statement.

2. Step 2: Identify correct syntax

   function Button() { return Click me; } correctly defines a function returning JSX. const Button = () => { Click me } misses return. class Button extends React.Component { render() { return Click me; } } is a class component, not functional.

3. Final Answer:

   function Button() { return <button>Click me</button>; } -> Option A

4. Quick Check:

   Functional component needs return [OK]

Hint: Functional components must return JSX explicitly [OK]

Common Mistakes:

• Omitting return statement in arrow functions
• Confusing class and functional component syntax
• Not returning JSX from the function

3. Given the code below, what will be rendered on the screen?

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

function App() {
  return <Greeting name="Alice" />;
}

medium

A. Error: name is undefined

B. Hello, name!

C. Hello, Alice!

D.

Solution

1. Step 1: Understand props usage in Greeting

   The Greeting component receives a prop called name and uses it inside JSX to display a greeting.

2. Step 2: Check how App uses Greeting

   App passes the string "Alice" as the name prop, so Greeting renders <h1>Hello, Alice!</h1>.

3. Final Answer:

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

4. Quick Check:

   Props passed correctly = C [OK]

Hint: Props replace placeholders with actual values [OK]

Common Mistakes:

• Thinking props are not passed automatically
• Expecting literal 'name' string instead of value
• Confusing JSX tags with strings

4. Identify the error in this React component organization:

function Header() {
  return <header>Welcome</header>;
}

function App() {
  return (
    <div>
      <Header />
      <Footer />
    </div>
  );
}

medium

A. Footer component is used but not defined or imported

B. Header component should be a class component

C. App component must return a single element without div

D. Header component should not use semantic tags

Solution

1. Step 1: Check component usage in App

   App uses <Header /> and <Footer /> components inside a div.

2. Step 2: Verify component definitions

   Header is defined, but Footer is neither defined nor imported, causing an error.

3. Final Answer:

   Footer component is used but not defined or imported -> Option A

4. Quick Check:

   Undefined component usage = A [OK]

Hint: All used components must be defined or imported [OK]

Common Mistakes:

• Assuming class components are required
• Thinking multiple elements need no wrapper
• Believing semantic tags cause errors

5. You want to organize a React app with a main Dashboard component that uses smaller components like Sidebar, Content, and Footer. Which approach best follows good component organization?

hard

A. Put all JSX for Sidebar, Content, and Footer inside Dashboard's single file

B. Create separate files for Sidebar, Content, and Footer components and import them into Dashboard

C. Write Sidebar, Content, and Footer as functions inside Dashboard component function

D. Combine Sidebar and Footer into one component and Content separately, all in Dashboard file

Solution

1. Step 1: Understand component reusability and clarity

   Separating components into their own files makes code easier to read, reuse, and maintain.

2. Step 2: Evaluate options for organization

   Create separate files for Sidebar, Content, and Footer components and import them into Dashboard creates separate files and imports them, which is best practice. Other options mix concerns or reduce clarity.

3. Final Answer:

   Create separate files for Sidebar, Content, and Footer components and import them into Dashboard -> Option B

4. Quick Check:

   Separate files for components = A [OK]

Hint: Separate components into files for clarity and reuse [OK]

Common Mistakes:

• Putting all code in one file making it messy
• Defining components inside other components unnecessarily
• Combining unrelated components reducing modularity