ngOnInit for initialization in Angular - Performance & Optimization

Performance: ngOnInit for initialization

MEDIUM IMPACT

This affects the initial rendering speed and responsiveness by controlling when component initialization logic runs.

Running initialization logic in Angular components

Angular

import { OnInit } from '@angular/core';

export class MyComponent implements OnInit {
  ngOnInit() {
    this.loadData();
  }
  loadData() {
    // heavy synchronous logic
  }
}

Initialization runs after Angular sets inputs but before rendering starts, allowing faster initial paint.

📈 Performance GainReduces blocking time during component creation, improving LCP by 100-300ms.

Running initialization logic in Angular components

Angular

export class MyComponent {
  constructor() {
    this.loadData();
  }
  loadData() {
    // heavy synchronous logic
  }
}

Running heavy logic in the constructor blocks component creation and delays rendering.

📉 Performance CostBlocks rendering until constructor finishes, increasing LCP by 100-300ms depending on logic.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Initialization in constructor	Immediate heavy DOM changes	Multiple reflows if DOM updated synchronously	High paint cost delaying first paint	[X] Bad
Initialization in ngOnInit	DOM changes after inputs set	Single reflow after initialization	Lower paint cost, faster first paint	[OK] Good

Rendering Pipeline

Angular creates the component instance, then calls ngOnInit after inputs are set but before first render. Initialization logic here affects style calculation and layout if it changes DOM or styles.

→Component Creation

→Style Calculation

→Layout

→Paint

⚠️ BottleneckComponent Creation and Layout stages if initialization is heavy or synchronous.

Core Web Vital Affected

LCP

This affects the initial rendering speed and responsiveness by controlling when component initialization logic runs.

Optimization Tips

1Avoid heavy synchronous logic in the constructor to prevent blocking rendering.

2Use ngOnInit to run initialization after inputs are set for better render timing.

3Defer heavy or async tasks to after ngOnInit to keep initial paint fast.

Performance Quiz - 3 Questions

Why is it better to put initialization logic in ngOnInit instead of the constructor?

A Because ngOnInit runs before the component is created.

B Because ngOnInit runs after inputs are set and does not block initial rendering.

C Because constructor runs asynchronously and delays rendering.

D Because constructor cannot access component inputs.

DevTools: Performance

How to check: Record a performance profile while loading the component. Look for long tasks during component creation and ngOnInit.

What to look for: Long blocking tasks in constructor indicate bad pattern; shorter tasks after component creation indicate good pattern.

Practice

1. What is the main purpose of the ngOnInit method in an Angular component?

easy

A. To run initialization code after the component is created

B. To handle user input events

C. To define the component's HTML template

D. To style the component with CSS

Solution

1. Step 1: Understand the role of ngOnInit

   The ngOnInit lifecycle hook runs after Angular creates the component, making it ideal for initialization tasks.

2. Step 2: Differentiate from other component parts

   Handling user input, defining templates, and styling are done elsewhere, not in ngOnInit.

3. Final Answer:

   To run initialization code after the component is created -> Option A

4. Quick Check:

   ngOnInit = initialization after creation [OK]

Hint: ngOnInit runs once after component setup [OK]

Common Mistakes:

• Confusing ngOnInit with event handlers
• Thinking ngOnInit sets styles or templates
• Using ngOnInit for user input processing

2. Which of the following is the correct way to implement ngOnInit in an Angular component?

easy

A. ngOnInit() { console.log('Init'); }

B. ngOnInit: function() { console.log('Init'); }

C. function ngOnInit() { console.log('Init'); }

D. onInit() { console.log('Init'); }

Solution

1. Step 1: Recall Angular lifecycle hook syntax

   In Angular components, lifecycle hooks like ngOnInit are methods declared as ngOnInit() { ... }.

2. Step 2: Identify incorrect syntax

   The other options use invalid syntax in an Angular class: shorthand property with function, standalone function declaration, and wrong method name.

3. Final Answer:

   ngOnInit() { console.log('Init'); } -> Option A

4. Quick Check:

   ngOnInit is a method, not a property or function keyword [OK]

Hint: Use method syntax: ngOnInit() { } [OK]

Common Mistakes:

• Using function keyword inside class
• Naming method incorrectly as onInit
• Using colon instead of parentheses

3. Consider this Angular component code snippet:

export class MyComponent implements OnInit {
  data = '';
  ngOnInit() {
    this.data = 'Hello World';
  }
}

What will be the value of data after the component initializes?

medium

A. '' (empty string)

B. undefined

C. null

D. 'Hello World'

Solution

1. Step 1: Check initial value of data

   The property data starts as an empty string.

2. Step 2: See what ngOnInit does

   Inside ngOnInit, data is set to 'Hello World'. This runs after component creation.

3. Final Answer:

   'Hello World' -> Option D

4. Quick Check:

   ngOnInit sets data to 'Hello World' [OK]

Hint: ngOnInit runs after creation, sets data [OK]

Common Mistakes:

• Assuming data stays empty string
• Confusing initialization timing
• Thinking ngOnInit runs before constructor

4. Identify the error in this Angular component code:

export class SampleComponent implements OnInit {
  message: string;
  ngOnInit() {
    this.message = 'Welcome';
  }
}

medium

A. ngOnInit method name is incorrect

B. message property should be initialized in constructor

C. Missing import of OnInit interface

D. No error, code is correct

Solution

1. Step 1: Check for required imports

   The component implements OnInit but does not import it from '@angular/core'. This causes a compile error.

2. Step 2: Verify method and property usage

   The method name ngOnInit is correct, and initializing message in ngOnInit is valid.

3. Final Answer:

   Missing import of OnInit interface -> Option C

4. Quick Check:

   Implementing OnInit requires importing it [OK]

Hint: Always import lifecycle interfaces from '@angular/core' [OK]

Common Mistakes:

• Forgetting to import OnInit
• Renaming ngOnInit incorrectly
• Thinking properties must initialize in constructor

5. You want to fetch user data from a server right after your Angular component is created. Where should you place the fetch call to ensure it runs once after initialization?

hard

A. Inside the constructor

B. Inside the ngOnInit method

C. Inside the ngOnDestroy method

D. Inside a button click event handler

Solution

1. Step 1: Understand lifecycle timing

   The constructor runs before Angular sets up the component fully, so it's not ideal for async tasks like fetching data.

2. Step 2: Use ngOnInit for initialization tasks

   ngOnInit runs after component creation and is the recommended place to start fetching data once.

3. Step 3: Exclude other options

   ngOnDestroy runs when component is destroyed, and button click handlers run on user action, not automatically.

4. Final Answer:

   Inside the ngOnInit method -> Option B

5. Quick Check:

   Fetch data in ngOnInit for one-time setup [OK]

Hint: Fetch data in ngOnInit, not constructor [OK]

Common Mistakes:

• Fetching data in constructor causing timing issues
• Using ngOnDestroy which runs too late
• Waiting for user click instead of auto-fetch