Managing large applications in React - Performance & Optimization

Performance: Managing large applications

HIGH IMPACT

This affects initial page load speed, bundle size, and runtime responsiveness in large React apps.

Loading a large React application all at once

React

import React, { Suspense, lazy } from 'react';

const BigComponentA = lazy(() => import('./BigComponentA'));
const BigComponentB = lazy(() => import('./BigComponentB'));

export default function App() {
  return (
    <>
      <Suspense fallback={<div>Loading A...</div>}>
        <BigComponentA />
      </Suspense>
      <Suspense fallback={<div>Loading B...</div>}>
        <BigComponentB />
      </Suspense>
    </>
  );
}

Loads components only when needed, reducing initial bundle size and speeding up first paint.

📈 Performance GainReduces initial bundle size by 30-70%, improving LCP and INP significantly.

Loading a large React application all at once

React

import { BigComponentA } from './BigComponentA';
import { BigComponentB } from './BigComponentB';

export default function App() {
  return (
    <>
      <BigComponentA />
      <BigComponentB />
    </>
  );
}

Imports all large components upfront, increasing bundle size and blocking initial render.

📉 Performance CostBlocks rendering until entire bundle loads, increasing LCP by 1-3 seconds on slow networks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Import all components upfront	High (all nodes loaded)	Multiple reflows on load	High paint cost	[X] Bad
Lazy load components with React.lazy	Reduced initial nodes	Single reflow on load	Lower paint cost	[OK] Good
Prop drilling global state	Many re-renders	Many reflows on state change	High paint cost	[X] Bad
Use React Context for global state	Fewer re-renders	Fewer reflows	Lower paint cost	[OK] Good
Inline event handlers per item	Many function recreations	No direct reflow but high CPU	Higher paint cost due to CPU	[X] Bad
Memoized shared event handler	Single function instance	No extra reflows	Lower paint cost	[OK] Good

Rendering Pipeline

Managing large apps affects how much JavaScript the browser must parse and execute before painting. Lazy loading reduces initial JavaScript parsing. Using context and memoization reduces React re-renders, lowering layout and paint costs.

→JavaScript Parsing

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckJavaScript Parsing and Layout due to large bundles and frequent re-renders.

Core Web Vital Affected

LCP, INP

This affects initial page load speed, bundle size, and runtime responsiveness in large React apps.

Optimization Tips

1Split large React apps with lazy loading to reduce initial bundle size.

2Use React Context to manage global state and avoid prop drilling.

3Memoize event handlers to reduce memory usage and improve responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using React.lazy for large components?

A It prevents any re-renders in the app.

B It automatically caches all components in memory.

C It reduces the initial JavaScript bundle size, speeding up first paint.

D It disables JavaScript parsing for those components.

DevTools: Performance

How to check: Record a performance profile while loading the app and interacting. Look for long scripting tasks and frequent layout recalculations.

What to look for: High scripting time and many layout events indicate poor code splitting or excessive re-renders.

Practice

1. What is a common way to organize a large React application to keep it manageable?

easy

A. Use only class components to keep consistency

B. Write all code in a single file for easy access

C. Avoid using components and write plain JavaScript

D. Split the app into smaller components and folders

Solution

1. Step 1: Understand component-based design

   React encourages breaking UI into small, reusable components.

2. Step 2: Organize code in folders

   Grouping related components and files in folders helps maintain large apps.

3. Final Answer:

   Split the app into smaller components and folders -> Option D

4. Quick Check:

   Component + folder structure = A [OK]

Hint: Think modular: small parts in folders make apps manageable [OK]

Common Mistakes:

• Putting all code in one file makes it hard to maintain
• Ignoring components loses React's main advantage
• Using only class components is outdated

2. Which of the following is the correct way to import a component named Header from a file in React?

easy

A. import Header from './Header';

B. require Header from './Header';

C. import { Header } from './Header.js';

D. include Header from './Header';

Solution

1. Step 1: Recognize ES6 import syntax

   React uses ES6 modules, so import Header from './Header'; is correct for default exports.

2. Step 2: Check other options

   require is CommonJS, not standard in React apps; include is invalid; named import { Header } requires named export.

3. Final Answer:

   import Header from './Header'; -> Option A

4. Quick Check:

   Default import uses import X from [OK]

Hint: Use ES6 import syntax: import Component from 'path' [OK]

Common Mistakes:

• Using require instead of import in React
• Confusing default and named imports
• Using invalid keywords like include

3. Given this React component structure:

src/
  components/
    Navbar.js
  pages/
    Home.js
    About.js
  App.js

Which statement best describes how routing helps manage this app?

medium

A. Routing allows switching between Home and About pages without reloading

B. Routing bundles all components into one file for faster loading

C. Routing automatically converts components to class components

D. Routing disables navigation to keep app simple

Solution

1. Step 1: Understand routing purpose

   Routing lets users move between different views (pages) in a React app without full page reloads.

2. Step 2: Apply to given structure

   Home.js and About.js are pages; routing switches between them smoothly.

3. Final Answer:

   Routing allows switching between Home and About pages without reloading -> Option A

4. Quick Check:

   Routing = page switching without reload [OK]

Hint: Routing changes views without refreshing the whole page [OK]

Common Mistakes:

• Thinking routing bundles files together
• Believing routing changes component types
• Assuming routing disables navigation

4. You have this React code snippet:

function App() {
  const [count, setCount] = useState(0)

  return (
    <div>
      <button onClick="setCount(count + 1)">Increment</button>
      <p>Count: {count}</p>
    </div>
  )
}

What is the main error preventing the button from working?

medium

A. setCount should be called without parentheses

B. Missing import of React

C. Using double quotes instead of curly braces for onClick handler

D. State variable count is not initialized

Solution

1. Step 1: Check onClick syntax

   In JSX, event handlers must be passed as functions inside curly braces, not strings in quotes.

2. Step 2: Identify the error

   Here, onClick="setCount(count + 1)" uses quotes, so React treats it as a string, not a function.

3. Final Answer:

   Using double quotes instead of curly braces for onClick handler -> Option C

4. Quick Check:

   JSX event handlers need curly braces [OK]

Hint: Use curly braces for event handlers, not quotes [OK]

Common Mistakes:

• Using quotes instead of curly braces for onClick
• Forgetting to import React (less common in new versions)
• Calling setCount incorrectly

5. In a large React app, you want to keep UI components separate from business logic for easier teamwork. Which approach best supports this?

hard

A. Avoid using hooks and manage state globally only

B. Use container components to handle logic and presentational components for UI

C. Write all logic inside UI components to keep code together

D. Put all components and logic in one file to reduce imports

Solution

1. Step 1: Understand separation of concerns

   Separating UI and logic helps teams work independently and keeps code clean.

2. Step 2: Apply container and presentational pattern

   Container components manage data and logic; presentational components focus on UI rendering.

3. Final Answer:

   Use container components to handle logic and presentational components for UI -> Option B

4. Quick Check:

   Separate logic and UI with containers and presentational components [OK]

Hint: Split logic (containers) and UI (presentational) components [OK]

Common Mistakes:

• Mixing logic inside UI components makes maintenance hard
• Avoiding hooks limits React's power
• Putting everything in one file causes confusion