Lazy loading routes in Vue - Performance & Optimization

Performance: Lazy loading routes

HIGH IMPACT

This affects the initial page load speed by deferring loading of route components until needed.

Loading route components in a Vue app

Vue

const routes = [
  { path: '/', component: () => import('./views/Home.vue') },
  { path: '/about', component: () => import('./views/About.vue') }
];

Route components are loaded only when the user navigates to them, reducing initial bundle size and speeding up first paint.

📈 Performance GainReduces initial bundle size by 50-200KB; improves LCP by 200-500ms

Loading route components in a Vue app

Vue

import Home from './views/Home.vue';
import About from './views/About.vue';

const routes = [
  { path: '/', component: Home },
  { path: '/about', component: About }
];

All route components are bundled and loaded upfront, increasing initial bundle size and slowing first paint.

📉 Performance CostBlocks rendering for extra 200-500ms depending on component size; increases initial bundle size by 50-200KB

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Eager loading routes	N/A (no extra DOM nodes)	0	Higher paint cost due to larger JS bundle delaying first paint	[X] Bad
Lazy loading routes	N/A (no extra DOM nodes)	0	Lower paint cost due to smaller initial JS bundle	[OK] Good

Rendering Pipeline

Lazy loading routes delays fetching and parsing route components until navigation triggers them, reducing initial JavaScript parsing and execution.

→Network

→JavaScript Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Parsing and Network load during initial page load

Core Web Vital Affected

LCP

This affects the initial page load speed by deferring loading of route components until needed.

Optimization Tips

1Use dynamic import() for route components to enable lazy loading.

2Lazy loading routes reduces initial JavaScript bundle size and speeds up LCP.

3Verify lazy loading by checking network requests load route chunks on demand.

Performance Quiz - 3 Questions

What is the main performance benefit of lazy loading routes in a Vue app?

A Reduces number of DOM nodes created

B Reduces initial bundle size and speeds up first paint

C Improves CSS selector matching speed

D Preloads all routes to avoid network delay

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network panel, reload page and observe JS chunk sizes and load timing. Then navigate to lazy route and see new chunk load. Use Performance panel to check main thread blocking time.

What to look for: Smaller initial JS bundle size and deferred loading of route chunks on navigation confirm good lazy loading performance.

Practice

1. What is the main benefit of using lazy loading for routes in Vue?

easy

A. It automatically caches all components in the browser.

B. It preloads all components at app start for faster navigation.

C. It loads components only when the route is visited, reducing initial load time.

D. It disables routing and shows all components on one page.

Solution

1. Step 1: Understand lazy loading concept

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

2. Step 2: Apply to Vue routes

   In Vue, lazy loading routes means components load only when their route is visited, reducing initial app size and speeding start time.

3. Final Answer:

   It loads components only when the route is visited, reducing initial load time. -> Option C

4. Quick Check:

   Lazy loading = load on demand [OK]

Hint: Lazy loading means load components only when needed [OK]

Common Mistakes:

• Thinking lazy loading preloads all components
• Confusing lazy loading with caching
• Believing lazy loading disables routing

2. Which of the following is the correct syntax to lazy load a route component in Vue Router?

easy

A. component: import('./MyComponent.vue')

B. component: './MyComponent.vue'

C. component: () => require('./MyComponent.vue')

D. component: () => import('./MyComponent.vue')

Solution

1. Step 1: Recall Vue Router lazy loading syntax

   Vue Router uses dynamic import with arrow function: () => import('path').

2. Step 2: Check each option

   component: () => import('./MyComponent.vue') matches correct syntax. component: import('./MyComponent.vue') misses arrow function. component: () => require('./MyComponent.vue') uses require which is not standard for lazy loading in Vue 3. component: './MyComponent.vue' is just a string, not a function.

3. Final Answer:

   component: () => import('./MyComponent.vue') -> Option D

4. Quick Check:

   Lazy load syntax = arrow function + import() [OK]

Hint: Lazy load uses arrow function returning import() [OK]

Common Mistakes:

• Omitting arrow function
• Using require() instead of import()
• Assigning component to string path directly

3. Given this Vue Router route config, what will happen when the user visits '/dashboard' for the first time?

const routes = [
  {
    path: '/dashboard',
    component: () => import('./Dashboard.vue')
  }
]

medium

A. The Dashboard component is loaded immediately when the app starts.

B. The Dashboard component is loaded only when the '/dashboard' route is visited.

C. The Dashboard component is never loaded.

D. The Dashboard component is loaded twice.

Solution

1. Step 1: Analyze the route config

   The component is assigned as a function returning import(), which means lazy loading.

2. Step 2: Understand lazy loading behavior

   The component will load only when the route '/dashboard' is visited, not before.

3. Final Answer:

   The Dashboard component is loaded only when the '/dashboard' route is visited. -> Option B

4. Quick Check:

   Lazy load means load on visit [OK]

Hint: Lazy loaded components load on route visit, not app start [OK]

Common Mistakes:

• Assuming component loads at app start
• Thinking component never loads
• Believing component loads multiple times automatically

4. Identify the error in this Vue Router lazy loading route config:

const routes = [
  {
    path: '/profile',
    component: import('./Profile.vue')
  }
]

medium

A. Missing arrow function wrapping the import call.

B. The path should be '/profiles' instead of '/profile'.

C. The import path must be absolute, not relative.

D. Lazy loading is not supported in Vue Router.

Solution

1. Step 1: Check lazy loading syntax

   Lazy loading requires component to be a function returning import(), like () => import('...').

2. Step 2: Identify the error

   Here, import() is called directly without arrow function, causing immediate import and syntax error.

3. Final Answer:

   Missing arrow function wrapping the import call. -> Option A

4. Quick Check:

   Lazy load needs () => import() [OK]

Hint: Lazy load must use arrow function wrapping import() [OK]

Common Mistakes:

• Calling import() directly without arrow function
• Changing path unnecessarily
• Believing lazy loading is unsupported

5. You want to lazy load two nested routes in Vue Router: '/settings' and '/settings/profile'. Which is the correct way to configure lazy loading for both routes?

hard

A. Use component: () => import() for both routes inside children array.

B. Lazy load only the parent route; child routes load immediately.

C. Use static imports for both routes to avoid delays.

D. Define child routes outside the parent route config.

Solution

1. Step 1: Understand nested route lazy loading

   Each route can lazy load its component independently using () => import().

2. Step 2: Apply to nested routes

   Both '/settings' and '/settings/profile' should have component properties with arrow functions returning import() to lazy load separately.

3. Step 3: Check other options

   Lazy load only the parent route; child routes load immediately. is wrong because child routes won't lazy load automatically. Use static imports for both routes to avoid delays. disables lazy loading. Define child routes outside the parent route config. is unrelated to lazy loading.

4. Final Answer:

   Use component: () => import() for both routes inside children array. -> Option A

5. Quick Check:

   Lazy load each nested route with () => import() [OK]

Hint: Lazy load each nested route with arrow function import() [OK]

Common Mistakes:

• Lazy loading only parent route
• Using static imports for lazy loading
• Separating child routes incorrectly