Async components for lazy loading in Vue - Performance & Optimization

Performance: Async components for lazy loading

HIGH IMPACT

This affects the initial page load speed by deferring component loading until needed, improving time to interactive.

Loading a large Vue component only when needed

Vue

import { defineAsyncComponent } from 'vue';
export default {
  components: {
    LargeComponent: defineAsyncComponent(() => import('./LargeComponent.vue'))
  }
};

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

📈 Performance GainSaves 100+ kb on initial load, improves LCP by deferring heavy code

Loading a large Vue component only when needed

Vue

import LargeComponent from './LargeComponent.vue';
export default {
  components: { LargeComponent }
};

Imports the large component upfront, increasing initial bundle size and delaying page load.

📉 Performance CostAdds 100+ kb to initial bundle, blocking rendering until loaded

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Eager import of large component	High upfront DOM nodes	Multiple reflows during initial load	High paint cost due to large bundle	[X] Bad
Async component lazy loaded	DOM nodes added on demand	Single reflow when component loads	Lower initial paint cost	[OK] Good

Rendering Pipeline

Async components delay loading until requested, so initial style calculation and layout happen faster with less code. The component is fetched and rendered later, triggering additional paint and composite steps.

→Network

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckNetwork and Paint when async component loads

Core Web Vital Affected

LCP

This affects the initial page load speed by deferring component loading until needed, improving time to interactive.

Optimization Tips

1Always lazy load large components to reduce initial bundle size.

2Use loading placeholders to avoid layout shifts when async components load.

3Monitor network requests to ensure components load only when needed.

Performance Quiz - 3 Questions

What is the main benefit of using async components in Vue for lazy loading?

A Prevents all JavaScript from loading

B Improves CSS selector performance

C Reduces initial bundle size and speeds up page load

D Automatically caches all components

DevTools: Performance

How to check: Record a page load and interaction; look for long tasks and network requests related to component chunks loading.

What to look for: Check if large JS chunks load upfront or deferred; verify faster Time to Interactive and lower LCP with async components.

Practice

1. What is the main purpose of using defineAsyncComponent in Vue?

easy

A. To load a component only when it is needed, improving app performance

B. To define a component that updates automatically on data change

C. To create a component that runs only on the server side

D. To make a component that never re-renders after first load

Solution

1. Step 1: Understand what lazy loading means

   Lazy loading means loading something only when it is needed, not before.

2. Step 2: Connect lazy loading to defineAsyncComponent

   This function helps Vue load components only when they are required, saving resources.

3. Final Answer:

   To load a component only when it is needed, improving app performance -> Option A

4. Quick Check:

   Lazy loading = load on demand [OK]

Hint: Async components load only when needed, boosting speed [OK]

Common Mistakes:

• Thinking it updates components automatically
• Confusing with server-side rendering
• Believing it prevents re-renders forever

2. Which of the following is the correct syntax to create an async component in Vue 3?

easy

A. const AsyncComp = async () => import('./MyComp.vue')

B. const AsyncComp = defineAsyncComponent(() => import('./MyComp.vue'))

C. const AsyncComp = defineComponent(async () => import('./MyComp.vue'))

D. const AsyncComp = createAsyncComponent('./MyComp.vue')

Solution

1. Step 1: Recall the Vue 3 async component syntax

   Vue 3 uses defineAsyncComponent with a function returning an import promise.

2. Step 2: Match the syntax with options

   const AsyncComp = defineAsyncComponent(() => import('./MyComp.vue')) matches the correct pattern: defineAsyncComponent(() => import('...')).

3. Final Answer:

   const AsyncComp = defineAsyncComponent(() => import('./MyComp.vue')) -> Option B

4. Quick Check:

   Correct async syntax = defineAsyncComponent + import [OK]

Hint: Use defineAsyncComponent with arrow function returning import [OK]

Common Mistakes:

• Using async arrow function without defineAsyncComponent
• Using defineComponent instead of defineAsyncComponent
• Calling a non-existent createAsyncComponent function

3. Given this Vue code snippet, what will be rendered initially?

const AsyncComp = defineAsyncComponent(() => new Promise(resolve => {
  setTimeout(() => resolve({ template: '
Loaded!
' }), 2000)
}))

export default {
  components: { AsyncComp },
  template: `
    
    
Loading...
  `
}

medium

A. Loading... (fallback content) for 2 seconds, then Loaded!

B. Loaded! immediately without delay

C. Nothing renders until the component loads

D. An error because Suspense cannot be used with async components

Solution

1. Step 1: Understand Suspense fallback behavior

   Suspense shows fallback content while async component loads.

2. Step 2: Analyze the async component delay

   The component resolves after 2 seconds, so fallback shows first.

3. Final Answer:

   Loading... (fallback content) for 2 seconds, then Loaded! -> Option A

4. Quick Check:

   Suspense fallback shows during async load [OK]

Hint: Suspense fallback shows until async component resolves [OK]

Common Mistakes:

• Expecting immediate component render
• Thinking nothing shows during loading
• Believing Suspense cannot wrap async components

4. Identify the error in this async component usage:

import { defineAsyncComponent } from 'vue'

const AsyncComp = defineAsyncComponent(() => import('./MyComp.vue'))

export default {
  components: { AsyncComp },
  template: `
`
}

medium

A. Async component must be registered globally, not locally

B. The template uses instead of self-closing

C. Missing Suspense wrapper to handle loading state

D. The import path './MyComp.vue' is invalid syntax

Solution

1. Step 1: Check async component usage rules

   Async components should be wrapped in <Suspense> to show fallback during loading.

2. Step 2: Analyze the given code

   The code lacks a <Suspense> wrapper, so no loading state is handled.

3. Final Answer:

   Missing Suspense wrapper to handle loading state -> Option C

4. Quick Check:

   Async components need Suspense for loading fallback [OK]

Hint: Always wrap async components in Suspense for loading UI [OK]

Common Mistakes:

• Thinking self-closing tags are mandatory
• Believing async components must be global
• Assuming import path syntax is wrong

5. You want to lazy load two components, CompA and CompB, but only show CompB after CompA finishes loading. How can you achieve this using Vue async components and Suspense?

hard

A. Wrap CompA in Suspense, and inside its default slot, include CompB as a normal component

B. Use defineAsyncComponent for both, wrap both in a single Suspense, and use v-if to show CompB only after CompA loads

C. Load both components with defineAsyncComponent and render them side by side without Suspense

D. Wrap CompA in a Suspense with fallback, then in CompA's mounted hook, render CompB inside another Suspense

Solution

1. Step 1: Understand the loading order requirement

   You want CompB to appear only after CompA finishes loading.

2. Step 2: Use sequential triggering with lifecycle

   Wrap CompA in Suspense; in CompA's mounted hook, dynamically render CompB (async) inside its own Suspense for true sequential loading.

3. Step 3: Why other options fail

   Wrapping both in a single Suspense loads them in parallel (shows both after slowest finishes); loading side-by-side without Suspense skips fallback and loads parallel; including normal CompB in CompA's default slot loads it immediately upon CompA resolution.

4. Final Answer:

   Wrap CompA in a Suspense with fallback, then in CompA's mounted hook, render CompB inside another Suspense -> Option D

5. Quick Check:

   Sequential async = trigger next in mounted [OK]

Hint: Trigger next async component in mounted hook for sequential loading [OK]

Common Mistakes:

• Using single Suspense for parallel loading
• Skipping Suspense for async components
• Treating second component as normal (non-async)