Lazy loading modules with routes in Angular - Performance & Optimization

Performance: Lazy loading modules with routes

HIGH IMPACT

This affects the initial page load speed by deferring loading of feature modules until their routes are accessed.

Loading feature modules in an Angular app

Angular

const routes: Routes = [
  { path: 'feature', loadChildren: () => import('./feature/feature.module').then(m => m.FeatureModule) },
  { path: 'dashboard', component: DashboardComponent }
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule]
})
export class AppRoutingModule {}

Modules are loaded only when their route is accessed, reducing initial bundle size and speeding up first paint.

📈 Performance GainReduces initial bundle size by 30-70% depending on app size, improving LCP and reducing blocking time.

Loading feature modules in an Angular app

Angular

import { FeatureModule } from './feature/feature.module';

const routes: Routes = [
  { path: 'feature', loadChildren: () => FeatureModule },
  { path: 'dashboard', component: DashboardComponent }
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule]
})
export class AppRoutingModule {}

Eagerly imports FeatureModule, which bundles it into the main chunk despite using loadChildren, causing all code to load upfront.

📉 Performance CostBlocks initial rendering by loading all modules upfront, increasing bundle size and delaying LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Eager loading all modules	High (all components loaded)	Multiple (due to large DOM)	High (large initial paint)	[X] Bad
Lazy loading modules with routes	Low initially (only active route DOM)	Single or few (on route change)	Low initial paint cost	[OK] Good

Rendering Pipeline

Lazy loading defers module loading until route activation, so initial style calculation and layout only process minimal code. When navigating, the browser fetches and compiles the module, triggering additional style and layout recalculations.

→Network

→Script Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckInitial bundle size and script parsing delay LCP.

Core Web Vital Affected

LCP

This affects the initial page load speed by deferring loading of feature modules until their routes are accessed.

Optimization Tips

1Always use lazy loading for large feature modules to reduce initial bundle size.

2Avoid importing feature modules eagerly in the main app module.

3Monitor network requests to ensure modules load only when their routes are accessed.

Performance Quiz - 3 Questions

What is the main performance benefit of lazy loading modules with routes in Angular?

A Loads all modules upfront to avoid delays later

B Reduces initial bundle size and speeds up first contentful paint

C Improves CSS selector matching speed

D Prevents any network requests after initial load

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, reload page and observe JS bundle sizes. Then navigate to lazy route and see additional chunks load. Use Performance tab to record load and interaction times.

What to look for: Look for smaller initial JS bundles and deferred loading of route chunks. Check LCP timing improves and fewer long tasks block main thread.

Practice

1. What is the main purpose of lazy loading modules in Angular routing?

easy

A. To preload all modules when the app starts

B. To load modules only when the user navigates to their route

C. To load modules in alphabetical order

D. To load all modules at once for faster navigation

Solution

1. Step 1: Understand lazy loading concept

   Lazy loading means delaying the loading of a module until it is needed, usually when the user navigates to a route that requires it.

2. Step 2: Identify the purpose in routing

   In Angular routing, lazy loading helps improve app speed by loading modules only on demand, not all at once.

3. Final Answer:

   To load modules only when the user navigates to their route -> Option B

4. Quick Check:

   Lazy loading = load on demand [OK]

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

Common Mistakes:

• Thinking lazy loading loads all modules at start
• Confusing lazy loading with preloading
• Assuming lazy loading loads modules alphabetically

2. Which of the following is the correct syntax to lazy load a module named AdminModule in Angular routes?

easy

A. { path: 'admin', loadChildren: import('./admin/admin.module') }

B. { path: 'admin', loadChildren: './admin/admin.module#AdminModule' }

C. { path: 'admin', component: AdminModule }

D. { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) }

Solution

1. Step 1: Recall Angular lazy loading syntax

   Angular uses dynamic import with a function returning a promise that resolves to the module class.

2. Step 2: Match syntax to options

   { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) } uses the correct arrow function with import and then to get AdminModule. { path: 'admin', loadChildren: './admin/admin.module#AdminModule' } is old deprecated string syntax. Options C and D are incorrect usage.

3. Final Answer:

   { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) } -> Option D

4. Quick Check:

   Dynamic import with arrow function = correct syntax [OK]

Hint: Use arrow function with import().then() for lazy loading [OK]

Common Mistakes:

• Using deprecated string syntax for loadChildren
• Assigning component instead of loadChildren
• Omitting the arrow function wrapper

3. Given this route configuration snippet:

{ path: 'shop', loadChildren: () => import('./shop/shop.module').then(m => m.ShopModule) }

What happens when the user navigates to /shop for the first time?

medium

A. The ShopModule is already loaded at app start, so navigation is instant

B. Navigation fails because loadChildren requires a component

C. The ShopModule is loaded asynchronously and its routes are activated

D. The entire app reloads to load ShopModule

Solution

1. Step 1: Understand lazy loading behavior on navigation

   When navigating to a lazy loaded route for the first time, Angular loads the module asynchronously.

2. Step 2: Identify what happens on first navigation

   The ShopModule is fetched, loaded, and its routes become active, enabling the user to see the shop page.

3. Final Answer:

   The ShopModule is loaded asynchronously and its routes are activated -> Option C

4. Quick Check:

   First navigation triggers async module load [OK]

Hint: First visit loads module asynchronously, not at app start [OK]

Common Mistakes:

• Assuming module loads at app start
• Confusing loadChildren with component property
• Thinking app reloads on lazy load

4. Identify the error in this Angular route configuration for lazy loading:

{ path: 'dashboard', loadChildren: './dashboard/dashboard.module#DashboardModule' }

medium

A. Using string syntax for loadChildren is deprecated and causes errors

B. Missing component property for the route

C. Path should be capitalized as 'Dashboard'

D. loadChildren should be a component, not a string

Solution

1. Step 1: Check loadChildren syntax

   The string syntax with '#ModuleName' is deprecated in Angular and may cause errors in recent versions.

2. Step 2: Identify correct syntax

   Modern Angular requires loadChildren to be a function returning a dynamic import promise, not a string.

3. Final Answer:

   Using string syntax for loadChildren is deprecated and causes errors -> Option A

4. Quick Check:

   Use dynamic import function, not string [OK]

Hint: Avoid string syntax; use dynamic import function [OK]

Common Mistakes:

• Using old string syntax for loadChildren
• Confusing component and loadChildren properties
• Ignoring case sensitivity in paths

5. You want to lazy load a feature module ProfileModule only when the user navigates to /profile. The module has child routes. Which is the best way to configure the main app routing to achieve this and ensure accessibility and performance?

hard

A. { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule), canActivate: [AuthGuard] }

B. { path: 'profile', component: ProfileModule }

C. { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule) }

D. { path: 'profile', loadChildren: './profile/profile.module#ProfileModule' }

Solution

1. Step 1: Identify modern lazy loading syntax

   The correct syntax uses dynamic import with an arrow function returning a promise: loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule).

2. Step 2: Consider best practices for accessibility and performance

   For protected features like a user profile, adding canActivate: [AuthGuard] ensures secure access while lazy loading maintains performance.

3. Step 3: Eliminate incorrect configurations

   Using component property fails for modules with child routes. String syntax like './profile/profile.module#ProfileModule' is deprecated.

4. Final Answer:

   { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule), canActivate: [AuthGuard] } -> Option A

5. Quick Check:

   Lazy load with guard for best practice [OK]

Hint: Lazy load with import and add guards for security [OK]

Common Mistakes:

• Using component instead of loadChildren for modules
• Using deprecated string syntax
• Forgetting route guards for protected routes