Feature modules for organization in Angular - Performance & Optimization

Performance: Feature modules for organization

MEDIUM IMPACT

This affects initial page load speed and bundle size by splitting code into smaller chunks loaded on demand.

Organizing Angular app code to improve load performance

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: 'feature', loadChildren: () => import('./feature/feature.module').then(m => m.FeatureModule) }
    ])
  ],
  bootstrap: [AppComponent]
})
export class AppModule {}

Feature module is lazy loaded only when user navigates, reducing initial bundle size and speeding up first paint.

📈 Performance GainReduces initial bundle size by 30-70%, improving LCP by 100-300ms

Organizing Angular app code to improve load performance

Angular

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

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

All components and features are bundled together, causing a large initial bundle and slower page load.

📉 Performance CostBlocks rendering for 200-500ms on initial load depending on app size

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single large module	Many nodes loaded upfront	Multiple reflows during initial render	High paint cost due to large DOM	[X] Bad
Feature modules with lazy loading	Fewer nodes initially	Single reflow on initial render	Lower paint cost initially	[OK] Good

Rendering Pipeline

Feature modules split code into chunks. The browser loads only the main chunk initially. When user navigates, Angular loads the feature chunk asynchronously. This reduces initial parsing and execution time.

→Network

→Parse & Compile

→Style Calculation

→Layout

→Paint

⚠️ BottleneckNetwork and Parse & Compile stages due to large initial bundle

Core Web Vital Affected

LCP

This affects initial page load speed and bundle size by splitting code into smaller chunks loaded on demand.

Optimization Tips

1Use feature modules to split app code into smaller chunks.

2Lazy load feature modules to reduce initial bundle size.

3Smaller initial bundles improve Largest Contentful Paint (LCP).

Performance Quiz - 3 Questions

How do feature modules improve Angular app load performance?

A By combining all code into one large bundle

B By splitting code into smaller chunks loaded on demand

C By removing CSS styles from components

D By disabling routing in the app

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, reload page and observe JS chunk sizes. Then use Performance tab to record page load and check scripting and rendering times.

What to look for: Look for smaller initial JS bundles and shorter scripting times indicating lazy loading. Check if feature chunks load only on navigation.

Practice

1. What is the main purpose of a feature module in Angular?

easy

A. To store global styles for the app

B. To replace the root AppModule entirely

C. To group related components, directives, and services for better organization

D. To handle routing only

Solution

1. Step 1: Understand feature module role

   Feature modules group related parts like components and services to keep code organized.

2. Step 2: Compare other options

   Feature modules do not replace AppModule, are not only for routing, and do not store styles.

3. Final Answer:

   To group related components, directives, and services for better organization -> Option C

4. Quick Check:

   Feature modules organize related code = D [OK]

Hint: Feature modules group related code parts [OK]

Common Mistakes:

• Thinking feature modules replace AppModule
• Believing feature modules only handle routing
• Confusing feature modules with style storage

2. Which of the following is the correct way to import a feature module named ProductsModule into the root module?

easy

A. declarations: [ProductsModule]

B. imports: [ProductsModule]

C. providers: [ProductsModule]

D. bootstrap: [ProductsModule]

Solution

1. Step 1: Recall Angular module metadata

   Feature modules are imported using the imports array in @NgModule.

2. Step 2: Understand other arrays

   declarations is for components/directives, providers for services, bootstrap for root component.

3. Final Answer:

   imports: [ProductsModule] -> Option B

4. Quick Check:

   Feature modules go in imports = B [OK]

Hint: Import feature modules inside imports array [OK]

Common Mistakes:

• Putting modules in declarations array
• Adding modules to providers array
• Using bootstrap array for modules

3. Given this code snippet in app.module.ts:

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

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

What will happen if ProductsModule declares and exports a component ProductListComponent and you use <app-product-list> in AppComponent template?

medium

A. The ProductListComponent will render correctly inside AppComponent

B. Angular will throw a template parse error because ProductListComponent is not declared in AppModule

C. The app will compile but ProductListComponent will not display anything

D. The app will crash at runtime with a component not found error

Solution

1. Step 1: Understand module imports and declarations

   Since ProductsModule is imported in AppModule, its declared components are available in AppModule's templates.

2. Step 2: Check component usage in template

   Using <app-product-list> in AppComponent works because ProductListComponent is exported by ProductsModule.

3. Final Answer:

   The ProductListComponent will render correctly inside AppComponent -> Option A

4. Quick Check:

   Imported module components usable in templates = A [OK]

Hint: Imported module components can be used in root templates [OK]

Common Mistakes:

• Thinking components must be declared in AppModule to use
• Assuming runtime crash instead of compile error
• Believing imported components won't render

4. You have a feature module OrdersModule but when you try to use its component OrderListComponent in AppComponent, Angular shows an error: 'app-order-list' is not a known element. What is the most likely cause?

medium

A. OrdersModule was not imported into AppModule

B. OrderListComponent was not declared in OrdersModule

C. OrdersModule was added to declarations instead of imports

D. OrderListComponent selector is misspelled in the template

Solution

1. Step 1: Check module import

   If OrdersModule is not imported in AppModule, its components are unknown in root templates.

2. Step 2: Review other options

   While declaration or selector errors cause issues, the common cause for 'not a known element' is missing module import.

3. Final Answer:

   OrdersModule was not imported into AppModule -> Option A

4. Quick Check:

   Missing module import causes unknown element error = C [OK]

Hint: Always import feature modules in AppModule to use their components [OK]

Common Mistakes:

• Forgetting to import the feature module
• Adding module to declarations array
• Ignoring selector typos

5. You want to organize your Angular app by creating two feature modules: UsersModule and AdminModule. AdminModule needs to use components from UsersModule. How should you set up the modules to allow this?

hard

A. Use providers array to share components between modules

B. Import AdminModule into UsersModule and export needed components from AdminModule

C. Declare all components in both modules to share them

D. Import UsersModule into AdminModule and export needed components from UsersModule

Solution

1. Step 1: Understand module dependency direction

   If AdminModule needs UsersModule components, UsersModule must be imported into AdminModule.

2. Step 2: Export components from UsersModule

   Only exported components from UsersModule are visible to AdminModule.

3. Final Answer:

   Import UsersModule into AdminModule and export needed components from UsersModule -> Option D

4. Quick Check:

   Import dependency module and export components = A [OK]

Hint: Import and export modules to share components [OK]

Common Mistakes:

• Importing modules in wrong direction
• Declaring components in multiple modules
• Using providers to share components