Root module (AppModule) structure in Angular - Performance & Optimization

Performance: Root module (AppModule) structure

MEDIUM IMPACT

This affects the initial page load speed and rendering performance by controlling how much code and how many components load at startup.

Setting up the root Angular module for an app

Angular

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app.component';
import { RouterModule } from '@angular/router';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, RouterModule.forRoot([
    { path: 'heavy', loadChildren: () => import('./heavy-feature/heavy-feature.module').then(m => m.HeavyFeatureModule) }
  ])],
  bootstrap: [AppComponent]
})
export class AppModule {}

Uses lazy loading for heavy feature modules, so their code loads only when needed, reducing initial bundle size and speeding up first paint.

📈 Performance GainReduces initial bundle by 100+ KB, improves LCP by 300-500ms, non-blocking initial render

Setting up the root Angular module for an app

Angular

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app.component';
import { HeavyFeatureModule } from './heavy-feature/heavy-feature.module';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, HeavyFeatureModule],
  bootstrap: [AppComponent]
})
export class AppModule {}

Importing large feature modules directly in the root module causes all their code to load immediately, increasing bundle size and delaying initial render.

📉 Performance CostIncreases bundle size by 100+ KB, blocks rendering until all modules load, delays LCP by 300-500ms

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Import all feature modules in AppModule	Low (few nodes initially)	Low (initial load only)	High (delayed paint due to JS parsing)	[X] Bad
Lazy load feature modules via Router	Low (few nodes initially)	Low (initial load only)	Low (faster paint)	[OK] Good

Rendering Pipeline

The root module loads first and sets up the app structure. Large imports here increase JavaScript parsing and execution time, delaying style calculation and layout.

→JavaScript Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Parsing and Execution due to large initial bundle

Core Web Vital Affected

LCP

This affects the initial page load speed and rendering performance by controlling how much code and how many components load at startup.

Optimization Tips

1Keep the root module imports minimal to reduce initial bundle size.

2Use lazy loading for large feature modules to speed up first paint.

3Avoid importing heavy libraries or modules directly in AppModule.

Performance Quiz - 3 Questions

What is the main performance drawback of importing all feature modules directly in the root AppModule?

A It triggers many layout reflows during user interaction.

B It increases the initial bundle size and delays the first contentful paint.

C It causes excessive DOM nodes to be created immediately.

D It reduces the app's accessibility features.

DevTools: Performance

How to check: Record a page load and look at the Main thread activity. Check the time spent in scripting and when the first contentful paint occurs.

What to look for: Long scripting tasks and delayed first contentful paint indicate large initial bundles slowing down the root module load.

Practice

1. What is the main purpose of the AppModule in an Angular application?

easy

A. To declare components and import modules needed for the app

B. To style the application globally

C. To handle HTTP requests

D. To manage routing only

Solution

1. Step 1: Understand the role of AppModule

   The AppModule is the root module that organizes the app's components and imports other modules.

2. Step 2: Identify what AppModule does

   It declares components and imports modules needed for the app to work properly.

3. Final Answer:

   To declare components and import modules needed for the app -> Option A

4. Quick Check:

   AppModule organizes components and imports [OK]

Hint: AppModule declares components and imports modules [OK]

Common Mistakes:

• Confusing AppModule with styling or HTTP handling
• Thinking AppModule only manages routing
• Assuming AppModule is for CSS or HTTP only

2. Which of the following is the correct way to define the bootstrap property in @NgModule for starting the app with AppComponent?

easy

A. bootstrap: AppComponent

B. bootstrap = AppComponent

C. bootstrap = [AppComponent]

D. bootstrap: [AppComponent]

Solution

1. Step 1: Recall the syntax for bootstrap in @NgModule

   The bootstrap property expects an array of components to start the app.

2. Step 2: Match the correct syntax

   Using bootstrap: [AppComponent] is the correct way to provide an array with the main component.

3. Final Answer:

   bootstrap: [AppComponent] -> Option D

4. Quick Check:

   Bootstrap uses array syntax [OK]

Hint: Bootstrap needs an array of components [OK]

Common Mistakes:

• Using assignment (=) instead of colon (:)
• Not wrapping component in an array
• Omitting brackets around AppComponent

3. Given this AppModule snippet, what will happen when the app starts?

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule],
  bootstrap: [AppComponent]
})
export class AppModule { }

medium

A. The app will throw a syntax error

B. The app will fail because BrowserModule is missing

C. The app will start and display the AppComponent template

D. The app will start but show a blank page

Solution

1. Step 1: Check declarations and imports

   AppComponent is declared and BrowserModule is imported, which is required for browser apps.

2. Step 2: Verify bootstrap property

   AppComponent is bootstrapped correctly, so it will be the starting component shown.

3. Final Answer:

   The app will start and display the AppComponent template -> Option C

4. Quick Check:

   Proper declarations, imports, and bootstrap means app runs [OK]

Hint: Check declarations, imports, and bootstrap for app start [OK]

Common Mistakes:

• Assuming BrowserModule is missing
• Thinking bootstrap array can be empty
• Confusing syntax errors with correct code

4. Identify the error in this AppModule code:

@NgModule({
  declarations: AppComponent,
  imports: [BrowserModule],
  bootstrap: [AppComponent]
})
export class AppModule { }

medium

A. imports should not include BrowserModule

B. declarations should be an array, not a single component

C. bootstrap should not be an array

D. Missing import statement for AppComponent

Solution

1. Step 1: Check declarations syntax

   Declarations must be an array of components, but here it is a single component without brackets.

2. Step 2: Confirm other parts are correct

   Imports and bootstrap are correctly formatted; import statement is assumed present.

3. Final Answer:

   declarations should be an array, not a single component -> Option B

4. Quick Check:

   Declarations require array syntax [OK]

Hint: Declarations always use arrays [OK]

Common Mistakes:

• Forgetting brackets around declarations
• Confusing imports with declarations
• Thinking bootstrap cannot be an array

5. You want to add a new component HeaderComponent to your Angular app. Which changes must you make in AppModule to include it properly?

hard

A. Add HeaderComponent to declarations array and import its file

B. Add HeaderComponent only to bootstrap array

C. Add HeaderComponent to imports array

D. No changes needed if HeaderComponent is in the same folder

Solution

1. Step 1: Import the new component

   You must import HeaderComponent from its file to use it in AppModule.

2. Step 2: Declare the component in declarations array

   Adding HeaderComponent to declarations lets Angular recognize and use it in templates.

3. Final Answer:

   Add HeaderComponent to declarations array and import its file -> Option A

4. Quick Check:

   New components require import and declaration [OK]

Hint: Import and declare new components in AppModule [OK]

Common Mistakes:

• Adding component to imports instead of declarations
• Only adding to bootstrap instead of declarations
• Assuming no changes needed for new components