Code splitting and lazy loading in Remix - Performance & Optimization

Performance: Code splitting and lazy loading

HIGH IMPACT

This concept affects page load speed by reducing initial bundle size and deferring non-critical code loading.

Loading a large JavaScript bundle on initial page load

Remix

import { lazy, Suspense } from 'react';
const BigComponent = lazy(() => import('./BigComponent'));

export default function Page() {
  return <Suspense fallback={<div>Loading...</div>}><BigComponent /></Suspense>;
}

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

📈 Performance GainReduces initial bundle size by 100-300kb, improving LCP by 300-700ms.

Loading a large JavaScript bundle on initial page load

Remix

import { BigComponent } from './BigComponent';

export default function Page() {
  return <BigComponent />;
}

Imports entire BigComponent bundle upfront, increasing initial load time and blocking rendering.

📉 Performance CostBlocks rendering until full bundle loads, increasing LCP by 500-1000ms on slow networks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single large bundle	Minimal	Single large reflow	High paint cost due to blocking	[X] Bad
Code splitting with lazy loading	Minimal	Multiple small reflows on demand	Lower paint cost, faster initial render	[OK] Good

Rendering Pipeline

Code splitting delays loading of non-critical JavaScript until needed, reducing blocking during Style Calculation and Layout. Lazy loading defers script parsing and execution, improving Paint and Composite stages.

→Script Parsing

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckScript Parsing and Execution during initial load

Core Web Vital Affected

LCP

This concept affects page load speed by reducing initial bundle size and deferring non-critical code loading.

Optimization Tips

1Split large JavaScript bundles into smaller chunks to reduce initial load time.

2Use lazy loading to defer non-critical code until it is needed by the user.

3Monitor bundle sizes and loading times with browser DevTools to optimize performance.

Performance Quiz - 3 Questions

What is the main benefit of code splitting in a Remix app?

A Reduces initial JavaScript bundle size to speed up page load

B Increases the number of HTTP requests to slow down loading

C Bundles all code into one file for easier caching

D Removes CSS from the page to improve rendering

DevTools: Performance

How to check: Record page load and look for long scripting tasks and blocking time in the flame chart. Check Network tab for large initial JS bundles.

What to look for: Shorter scripting tasks, smaller initial JS files, and faster Time to Interactive indicate good code splitting and lazy loading.

Practice

1. What is the main benefit of using code splitting and lazy loading in a Remix app?

easy

A. It loads only the code needed right now, making the app faster.

B. It bundles all code into one file for easier debugging.

C. It disables JavaScript to improve security.

D. It automatically fixes bugs in the code.

Solution

1. Step 1: Understand code splitting purpose

   Code splitting divides the app code into smaller parts to load only what is needed immediately.

2. Step 2: Recognize lazy loading effect

   Lazy loading delays loading parts of the app until they are needed, improving speed and user experience.

3. Final Answer:

   It loads only the code needed right now, making the app faster. -> Option A

4. Quick Check:

   Code splitting = faster loading [OK]

Hint: Code splitting means load only what you need now [OK]

Common Mistakes:

• Thinking all code loads at once
• Confusing lazy loading with disabling JavaScript
• Believing code splitting bundles everything together

2. Which of the following is the correct way to lazy load a component in Remix using React?

easy

A. const MyComponent = lazyLoad('./MyComponent');

B. const MyComponent = import('./MyComponent').then();

C. const MyComponent = React.load(() => import('./MyComponent'));

D. const MyComponent = React.lazy(() => import('./MyComponent'));

Solution

1. Step 1: Recall React.lazy syntax

   React.lazy expects a function returning a dynamic import promise: React.lazy(() => import('...'))

2. Step 2: Check each option

   const MyComponent = React.lazy(() => import('./MyComponent')); matches correct syntax; others use invalid methods or missing React.lazy.

3. Final Answer:

   const MyComponent = React.lazy(() => import('./MyComponent')); -> Option D

4. Quick Check:

   React.lazy + dynamic import = correct lazy load [OK]

Hint: Use React.lazy with a function returning import() [OK]

Common Mistakes:

• Forgetting to wrap import in a function
• Using non-existent React.load or lazyLoad functions
• Calling import without React.lazy

3. Given this Remix component code:

import React, { Suspense } from 'react';
const LazyComp = React.lazy(() => import('./LazyComp'));

export default function App() {
  return (
    Loading...}>
      
    
  );
}

What will the user see initially when App renders?

medium

A. Nothing until LazyComp finishes loading.

B. The Loading... text until LazyComp loads.

C. An error because Suspense is missing fallback.

D. LazyComp renders immediately without delay.

Solution

1. Step 1: Understand Suspense fallback role

   Suspense shows the fallback UI while the lazy component is loading.

2. Step 2: Analyze the code behavior

   Since LazyComp is lazy loaded,
   Loading... appears first until LazyComp finishes loading.

3. Final Answer:

   The <div>Loading...</div> text until LazyComp loads. -> Option B

4. Quick Check:

   Suspense fallback shows loading UI [OK]

Hint: Suspense fallback shows while lazy component loads [OK]

Common Mistakes:

• Thinking lazy components render instantly
• Forgetting Suspense fallback is required
• Assuming no UI shows during loading

4. What is wrong with this Remix lazy loading code snippet?

const LazyComp = React.lazy(import('./LazyComp'));

export default function App() {
  return ;
}

medium

A. Both B and C are errors.

B. LazyComp must be wrapped in Suspense with fallback UI.

C. React.lazy requires a function returning import, not import called directly.

D. There is no error; this code works fine.

Solution

1. Step 1: Check React.lazy usage

   React.lazy expects a function returning import(), but here import() is called immediately.

2. Step 2: Check Suspense usage

   Lazy loaded components must be inside Suspense with a fallback UI to handle loading state.

3. Final Answer:

   Both B and C are errors. -> Option A

4. Quick Check:

   React.lazy needs function + Suspense fallback [OK]

Hint: React.lazy needs a function and Suspense fallback [OK]

Common Mistakes:

• Calling import() directly inside React.lazy
• Not wrapping lazy component in Suspense
• Assuming lazy loading works without fallback

5. You want to lazy load two components in Remix: Header and Footer. You want to show a spinner while either loads. Which is the best way to implement this?

hard

A. Wrap each lazy component separately in its own Suspense with fallback spinner.

B. Load Header normally and lazy load Footer without Suspense.

C. Wrap both lazy components inside one Suspense with a single fallback spinner.

D. Lazy load both without Suspense; fallback is optional.

Solution

1. Step 1: Understand Suspense scope

   Suspense can wrap multiple lazy components to show one fallback UI while any are loading.

2. Step 2: Compare options

   Wrapping both in one Suspense is simpler and shows one spinner for both components loading.

3. Final Answer:

   Wrap both lazy components inside one Suspense with a single fallback spinner. -> Option C

4. Quick Check:

   One Suspense for multiple lazy components is best [OK]

Hint: Use one Suspense to wrap multiple lazy components [OK]

Common Mistakes:

• Wrapping each lazy component in separate Suspense unnecessarily
• Not using Suspense causing errors or no fallback UI
• Loading lazy components without fallback UI