Single Page Application concept in React - Performance & Optimization

Performance: Single Page Application concept

MEDIUM IMPACT

This concept affects initial page load speed and interaction responsiveness by loading content dynamically without full page reloads.

Loading new content on user navigation

React

import { useNavigate } from 'react-router-dom';
function LoadPage() {
  const navigate = useNavigate();
  navigate('/about');
}

// Or inside a component:
// const navigate = useNavigate();
// navigate('/about');

Uses client-side routing to update URL and content without full reload, preserving state.

📈 Performance GainSingle reflow, faster interaction (under 100ms), no full page reload.

Loading new content on user navigation

React

function loadPage() {
  window.location.href = '/about';
}

Triggers full page reload causing slow load and loss of app state.

📉 Performance CostBlocks rendering for 500-1000ms depending on network; triggers full reflow and repaint.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full page reload on navigation	High (reloads entire DOM)	Multiple (full reflow)	High (full repaint)	[X] Bad
Client-side routing with React Router	Low (updates part of DOM)	Single or none	Low (partial repaint)	[OK] Good
Loading entire app bundle upfront	N/A	N/A	Blocks rendering during JS parse	[X] Bad
Code splitting with lazy loading	N/A	N/A	Non-blocking JS load	[OK] Good

Rendering Pipeline

SPAs load a shell HTML and JS bundle first, then dynamically update the DOM via JavaScript without full reloads.

→Script Parsing

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckScript Parsing and Execution

Core Web Vital Affected

LCP, INP

This concept affects initial page load speed and interaction responsiveness by loading content dynamically without full page reloads.

Optimization Tips

1Avoid full page reloads by using client-side routing.

2Use code splitting to reduce initial JavaScript bundle size.

3Monitor scripting time in DevTools to catch performance bottlenecks.

Performance Quiz - 3 Questions

What is a main performance benefit of using client-side routing in a SPA?

A It eliminates the need for CSS styles.

B It reduces the total JavaScript bundle size automatically.

C It avoids full page reloads, improving interaction speed.

D It guarantees zero layout shifts on navigation.

DevTools: Performance

How to check: Record a session while navigating SPA routes; look for long scripting tasks and layout shifts.

What to look for: Check for long scripting times blocking main thread and absence of full page reloads.

Practice

1. What is the main advantage of a Single Page Application (SPA) compared to traditional multi-page websites?

easy

A. It uses only server-side rendering without JavaScript.

B. It loads the page once and updates content dynamically without full reloads.

C. It requires a new page load for every user action.

D. It does not support navigation between different views.

Solution

1. Step 1: Understand SPA behavior

   SPAs load a single HTML page and dynamically update content without reloading the entire page.

2. Step 2: Compare with traditional websites

   Traditional sites reload the whole page on navigation, causing slower user experience.

3. Final Answer:

   It loads the page once and updates content dynamically without full reloads. -> Option B

4. Quick Check:

   SPA = dynamic content update without reload [OK]

Hint: SPAs avoid full page reloads for faster user experience [OK]

Common Mistakes:

• Thinking SPAs reload pages on every action
• Confusing SPAs with server-only rendering
• Believing SPAs don't support navigation

2. Which React library is commonly used to manage navigation and URL paths in a Single Page Application?

easy

A. Styled Components

B. Redux

C. Axios

D. React Router

Solution

1. Step 1: Identify navigation management in React

   React Router is designed to handle routing and URL paths in SPAs.

2. Step 2: Differentiate other libraries

   Redux manages state, Axios handles HTTP requests, Styled Components manage styling.

3. Final Answer:

   React Router -> Option D

4. Quick Check:

   Routing in React SPA = React Router [OK]

Hint: React Router controls SPA navigation and URLs [OK]

Common Mistakes:

• Confusing Redux with routing
• Thinking Axios manages navigation
• Assuming styling libraries handle routing

3. Given this React SPA code snippet using React Router:

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path='/' element=<Home /> />
        <Route path='/about' element=<About /> />
      </Routes>
    </BrowserRouter>
  );
}

What happens when the user navigates to /about URL?

medium

A. Nothing happens because routes are not defined correctly.

B. The browser reloads the entire page and shows About component.

C. The About component renders without a full page reload.

D. The Home component renders instead of About.

Solution

1. Step 1: Analyze React Router setup

   The Route with path '/about' renders the About component inside BrowserRouter.

2. Step 2: Understand SPA navigation

   React Router updates the view without reloading the whole page when navigating to '/about'.

3. Final Answer:

   The About component renders without a full page reload. -> Option C

4. Quick Check:

   React Router navigation = no full reload [OK]

Hint: React Router changes views without reloading page [OK]

Common Mistakes:

• Assuming full page reload on route change
• Thinking routes are not matched correctly
• Confusing Home and About components

4. Identify the error in this React SPA routing code:

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path='/' component={Home} />
        <Route path='/profile' element=<Profile /> />
      </Routes>
    </BrowserRouter>
  );
}

medium

A. The first Route uses 'component' prop instead of 'element'.

B. The BrowserRouter is missing a closing tag.

C. Routes should be replaced with Switch.

D. Profile component is not imported.

Solution

1. Step 1: Check Route props

   React Router v6 uses 'element' prop with JSX, not 'component'.

2. Step 2: Verify other code parts

   BrowserRouter is properly closed, Routes is correct in v6, and Profile import is not shown but not necessarily an error here.

3. Final Answer:

   The first Route uses 'component' prop instead of 'element'. -> Option A

4. Quick Check:

   React Router v6 Route uses element prop [OK]

Hint: Use 'element' prop with JSX in React Router v6 [OK]

Common Mistakes:

• Using 'component' prop from older React Router versions
• Confusing Routes with Switch in v6
• Assuming missing closing tags without checking

5. You want to build a React SPA that shows a loading spinner while fetching user data on route change. Which approach best fits SPA principles?

hard

A. Use React Router for routes and show a spinner component while fetching data asynchronously in the route component.

B. Reload the entire page on each route change to fetch fresh data.

C. Fetch all user data once on app load and never update it.

D. Use multiple HTML pages and link between them for each user view.

Solution

1. Step 1: Understand SPA data fetching

   SPAs fetch data asynchronously and update views without full reloads.

2. Step 2: Implement loading state in route components

   Showing a spinner while fetching data fits SPA dynamic update and user feedback.

3. Step 3: Eliminate non-SPA approaches

   Reloading pages or using multiple HTML pages breaks SPA flow; fetching once without updates is inflexible.

4. Final Answer:

   Use React Router for routes and show a spinner component while fetching data asynchronously in the route component. -> Option A

5. Quick Check:

   SPA + async data + spinner = Use React Router for routes and show a spinner component while fetching data asynchronously in the route component. [OK]

Hint: Show spinner during async fetch inside SPA route components [OK]

Common Mistakes:

• Reloading pages instead of dynamic updates
• Not showing loading feedback during fetch
• Ignoring SPA dynamic data needs