Lazy loading standalone components in Angular - Performance & Optimization

Performance: Lazy loading standalone components

HIGH IMPACT

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

Loading a feature component only when the user navigates to it

Angular

const featureLoader = () => import('./feature.component').then(m => m.FeatureComponent);
@Component({
  selector: 'app-root',
  template: '<ng-container *ngComponentOutlet="featureLoader()"></ng-container>'
})
export class AppComponent {}

The feature component is loaded only when needed, reducing initial bundle size and speeding up first paint.

📈 Performance GainSaves 50-100kb on initial load, reduces LCP by 200-400ms depending on network.

Loading a feature component only when the user navigates to it

Angular

import { FeatureComponent } from './feature.component';
@Component({
  selector: 'app-root',
  template: '<app-feature></app-feature>'
})
export class AppComponent {}

The feature component is imported and bundled upfront, increasing initial load time even if the user never visits it.

📉 Performance CostAdds 50-100kb to initial bundle, blocking rendering longer and increasing LCP.

Performance Comparison

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

Rendering Pipeline

Lazy loading delays fetching and parsing of component code until user interaction or navigation triggers it, reducing initial style calculation and layout work.

→Network

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork and Style Calculation during initial load

Core Web Vital Affected

LCP

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

Optimization Tips

1Always split large components into lazy loaded chunks to reduce initial load.

2Use Angular's dynamic import syntax for standalone components to enable lazy loading.

3Monitor bundle sizes and network requests to ensure lazy loading is effective.

Performance Quiz - 3 Questions

What is the main benefit of lazy loading standalone components in Angular?

A Improves CSS selector performance

B Reduces initial bundle size and speeds up page load

C Increases DOM nodes for better SEO

D Prevents JavaScript errors

DevTools: Performance

How to check: Record a page load and look for long tasks and large script evaluation times. Check network tab for large initial bundles.

What to look for: Look for smaller initial JS bundles and shorter scripting times indicating lazy loading is effective.

Practice

1. What is the main benefit of lazy loading standalone components in Angular?

easy

A. It bundles all components into a single file

B. It automatically updates components without user action

C. It disables component rendering on mobile devices

D. It improves app speed by loading components only when needed

Solution

1. Step 1: Understand lazy loading purpose

   Lazy loading delays loading parts of the app until they are needed, reducing initial load time.

2. Step 2: Connect lazy loading to standalone components

   Standalone components can be lazy loaded to improve app speed by not loading them upfront.

3. Final Answer:

   It improves app speed by loading components only when needed -> Option D

4. Quick Check:

   Lazy loading = improves speed [OK]

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

Common Mistakes:

• Thinking lazy loading bundles all components together
• Confusing lazy loading with automatic updates
• Believing lazy loading disables components on devices

2. Which syntax correctly lazy loads a standalone component in Angular routing?

easy

A. { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) }

B. { path: 'home', component: () => import('./home.component').then(m => m.HomeComponent) }

C. { path: 'home', loadChildren: () => import('./home.component').then(m => m.HomeComponent) }

D. { path: 'home', loadModule: () => import('./home.component').then(m => m.HomeComponent) }

Solution

1. Step 1: Identify correct property for lazy loading standalone components

   Angular uses loadComponent to lazy load standalone components in routes.

2. Step 2: Check syntax correctness

   { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) } uses loadComponent with dynamic import and then returns the component class, which is correct.

3. Final Answer:

   { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) } -> Option A

4. Quick Check:

   Lazy load standalone = loadComponent [OK]

Hint: Use loadComponent with dynamic import for standalone lazy loading [OK]

Common Mistakes:

• Using component property instead of loadComponent
• Using loadChildren for components instead of modules
• Using non-existent loadModule property

3. Given this route config, what happens when navigating to '/dashboard'?

{ path: 'dashboard', loadComponent: () => import('./dashboard.component').then(m => m.DashboardComponent) }

medium

A. The DashboardComponent is loaded immediately when the app starts

B. The DashboardComponent is loaded only when '/dashboard' is visited

C. The DashboardComponent is never loaded

D. The app throws a runtime error due to missing component

Solution

1. Step 1: Understand loadComponent behavior

   Using loadComponent with dynamic import delays loading the component until the route is accessed.

2. Step 2: Apply to '/dashboard' route

   The DashboardComponent will load only when the user navigates to '/dashboard', not before.

3. Final Answer:

   The DashboardComponent is loaded only when '/dashboard' is visited -> Option B

4. Quick Check:

   loadComponent = lazy load on route visit [OK]

Hint: loadComponent loads component on route visit only [OK]

Common Mistakes:

• Assuming component loads at app start
• Thinking component never loads
• Expecting runtime error without import

4. Identify the error in this route config for lazy loading a standalone component:

{ path: 'profile', loadComponent: import('./profile.component').then(m => m.ProfileComponent) }

medium

A. Missing arrow function wrapping the import call

B. Using loadComponent instead of component property

C. Incorrect path string format

D. Missing import statement at the top of the file

Solution

1. Step 1: Check loadComponent syntax

   The loadComponent property must be a function returning a Promise, so it needs an arrow function wrapping the import.

2. Step 2: Identify missing arrow function

   The code calls import directly without wrapping in a function, causing the component to load eagerly or a runtime error when the router tries to invoke it.

3. Final Answer:

   Missing arrow function wrapping the import call -> Option A

4. Quick Check:

   loadComponent requires () => import(...) [OK]

Hint: Wrap import in arrow function for loadComponent [OK]

Common Mistakes:

• Calling import directly without function
• Confusing loadComponent with component property
• Thinking import must be at file top

5. You want to lazy load two standalone components, AdminComponent and UserComponent, under routes '/admin' and '/user'. Which is the best way to configure the routes to optimize initial load time?

hard

A. Import both components eagerly and assign them to routes directly

B. Use loadChildren to lazy load a module containing both components

C. Use loadComponent with dynamic imports for both routes separately

D. Combine both components into one and lazy load that single component

Solution

1. Step 1: Understand lazy loading standalone components

   Using loadComponent with dynamic imports allows each component to load only when its route is visited, reducing initial load.

2. Step 2: Compare options for multiple components

   Use loadComponent with dynamic imports for both routes separately loads each component lazily and separately, optimizing load time better than eager loading or bundling.

3. Final Answer:

   Use loadComponent with dynamic imports for both routes separately -> Option C

4. Quick Check:

   Separate loadComponent calls = best lazy loading [OK]

Hint: Lazy load each standalone component separately with loadComponent [OK]

Common Mistakes:

• Eagerly importing components defeats lazy loading
• Using loadChildren for standalone components unnecessarily
• Combining components increases initial load size