Fallback UI patterns in React - Performance & Optimization

Performance: Fallback UI patterns

MEDIUM IMPACT

Fallback UI patterns affect the perceived loading speed and interaction responsiveness by controlling what the user sees during data fetching or lazy loading.

Showing a loading state while fetching data or lazy loading components

React

function MyComponent() {
  const [data, setData] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/data').then(res => res.json()).then(setData);
  }, []);
  if (!data) {
    return <div aria-busy="true" aria-label="Loading content" style={{width: '100%', height: '1rem', backgroundColor: '#eee'}}></div>;
  }
  return <div>{data.content}</div>;
}

The fallback UI is a simple, fixed-size placeholder that avoids layout shifts and reduces paint complexity.

📈 Performance GainSingle reflow, minimal paint cost, reduces CLS and improves LCP.

Showing a loading state while fetching data or lazy loading components

React

function MyComponent() {
  const [data, setData] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/data').then(res => res.json()).then(setData);
  }, []);
  if (!data) {
    return <div style={{fontSize: '2rem', fontWeight: 'bold'}}>Loading, please wait...</div>;
  }
  return <div>{data.content}</div>;
}

The fallback UI uses heavy styles and large text, causing layout shifts and longer paint times.

📉 Performance CostTriggers multiple reflows and increases CLS due to layout shifts; blocks LCP until data loads.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy styled fallback UI	Moderate DOM nodes	Multiple reflows due to size changes	High paint cost from complex styles	[X] Bad
Simple fixed-size placeholder fallback	Minimal DOM nodes	Single reflow with fixed size	Low paint cost with simple styles	[OK] Good

Rendering Pipeline

Fallback UI patterns affect the browser's rendering pipeline by controlling when and how much content is painted during loading states, impacting layout and paint stages.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout is most expensive due to reflows caused by fallback UI size changes.

Core Web Vital Affected

LCP

Fallback UI patterns affect the perceived loading speed and interaction responsiveness by controlling what the user sees during data fetching or lazy loading.

Optimization Tips

1Use simple, fixed-size placeholders as fallback UI to avoid layout shifts.

2Keep fallback UI styles minimal to reduce paint cost.

3Add ARIA attributes to fallback UI for accessibility without performance cost.

Performance Quiz - 3 Questions

What is the main performance benefit of using a simple fixed-size fallback UI in React Suspense?

A It prevents layout shifts and reduces paint cost.

B It increases bundle size but improves interactivity.

C It delays the first contentful paint.

D It triggers multiple reflows to update styles.

DevTools: Performance

How to check: Record a performance profile while loading the page or component. Look for layout shifts and paint times during fallback UI display.

What to look for: Check for multiple layout recalculations and long paint durations indicating heavy fallback UI. Minimal layout and paint times indicate good fallback performance.

Practice

1. What is the main purpose of a fallback UI in React applications?

easy

A. To speed up the rendering of all components

B. To permanently replace the main UI with a different design

C. To disable user interactions during loading

D. To show a temporary interface while content is loading or an error occurs

Solution

1. Step 1: Understand fallback UI role

   Fallback UI is used to improve user experience by showing temporary content during loading or errors.

2. Step 2: Differentiate from permanent UI changes

   Fallback UI is temporary, not a permanent replacement or disabling interaction.

3. Final Answer:

   To show a temporary interface while content is loading or an error occurs -> Option D

4. Quick Check:

   Fallback UI = temporary loading/error display [OK]

Hint: Fallback UI shows temporary content during loading/errors [OK]

Common Mistakes:

• Thinking fallback UI is permanent
• Confusing fallback UI with performance optimization
• Assuming fallback UI disables all user actions

2. Which of the following is the correct way to render a fallback UI in React using conditional rendering?

easy

A. {isLoading ? <LoadingSpinner /> : <Content />}

B. {isLoading && <Content />}

C. {isLoading || <LoadingSpinner />}

D. {isLoading = <LoadingSpinner />}

Solution

1. Step 1: Review conditional rendering syntax

   Using the ternary operator ? : correctly chooses between fallback and main UI.

2. Step 2: Check each option's logic

   {isLoading ? <LoadingSpinner /> : <Content />} uses ternary correctly; B and C misuse logical operators; D uses assignment instead of comparison.

3. Final Answer:

   {isLoading ? <LoadingSpinner /> : <Content />} -> Option A

4. Quick Check:

   Ternary operator for fallback UI = {isLoading ? <LoadingSpinner /> : <Content />} [OK]

Hint: Use ternary operator for fallback UI rendering [OK]

Common Mistakes:

• Using && or || incorrectly for fallback UI
• Using assignment (=) instead of comparison
• Not providing both fallback and main UI in conditional

3. Given the code below, what will be rendered when hasError is true?

function MyComponent({ hasError, isLoading }) {
  if (hasError) {
    return <div>Error occurred</div>
  }
  if (isLoading) {
    return <div>Loading...</div>
  }
  return <div>Content loaded</div>
}

medium

A. Loading...

B. Error occurred

C. Content loaded

D. Nothing will render

Solution

1. Step 1: Check error condition first

   The component returns the error message immediately if hasError is true.

2. Step 2: Understand conditional order

   Since error check comes before loading, loading state is ignored if error exists.

3. Final Answer:

   <div>Error occurred</div> -> Option B

4. Quick Check:

   Error condition renders error UI first [OK]

Hint: Error check before loading shows error UI first [OK]

Common Mistakes:

• Assuming loading shows even if error is true
• Ignoring order of conditions
• Thinking content loads despite error

4. Identify the error in this fallback UI pattern code:

function Profile({ user }) {
  return (
    <div>
      {user ? <ProfileDetails user={user} /> : <LoadingSpinner />}
      {!user && <LoadingSpinner />}
    </div>
  )
}

medium

A. The conditional rendering syntax is invalid

B. The component will crash because user is undefined

C. The fallback UI <LoadingSpinner /> is shown twice when user is null

D. The fallback UI is missing for loading state

Solution

1. Step 1: Analyze conditional rendering logic

   The first condition shows LoadingSpinner if user is falsy.

2. Step 2: Check second condition

   The second condition shows LoadingSpinner if user is falsy, causing it to appear twice when user is falsy.

3. Final Answer:

   The fallback UI <LoadingSpinner /> is shown twice when user is null -> Option C

4. Quick Check:

   Duplicate fallback UI rendering due to conflicting conditions [OK]

Hint: Check if fallback UI appears more than once [OK]

Common Mistakes:

• Assuming fallback UI shows only once
• Confusing truthy and falsy conditions
• Ignoring duplicated components in render

5. You want to create a fallback UI that shows a spinner while data loads, an error message if loading fails, and the content once loaded. Which React pattern best handles this cleanly and accessibly?

hard

A. Use separate components for Loading, Error, and Content, and conditionally render them in order

B. Use nested ternary operators inside JSX to handle loading, error, and content states

C. Render all three components simultaneously and hide/show with CSS

D. Use a single state variable with string values and switch-case inside JSX

Solution

1. Step 1: Evaluate clarity and accessibility

   Separate components for each state improve readability and accessibility.

2. Step 2: Compare with other options

   Nested ternaries (B) reduce readability; rendering all simultaneously (C) wastes resources; switch-case in JSX (D) is less common and can be confusing.

3. Final Answer:

   Use separate components for Loading, Error, and Content, and conditionally render them in order -> Option A

4. Quick Check:

   Separate components for fallback states = Use separate components for Loading, Error, and Content, and conditionally render them in order [OK]

Hint: Separate components for each state improve clarity [OK]

Common Mistakes:

• Using nested ternaries that are hard to read
• Rendering all states at once and hiding with CSS
• Using complex switch-case inside JSX