Directive execution and DOM manipulation in Angular - Performance & Optimization

Performance: Directive execution and DOM manipulation

HIGH IMPACT

This affects how fast the page renders and responds by controlling when and how DOM elements are created or changed.

Manipulating DOM elements inside Angular directives

Angular

import { Directive, ElementRef, Renderer2, AfterViewInit } from '@angular/core';

@Directive({ selector: '[goodDomManip]' })
export class GoodDomManipDirective implements AfterViewInit {
  constructor(private el: ElementRef, private renderer: Renderer2) {}

  ngAfterViewInit() {
    const fragment = document.createDocumentFragment();
    for (let i = 0; i < 1000; i++) {
      const div = this.renderer.createElement('div');
      this.renderer.setProperty(div, 'textContent', `Item ${i}`);
      fragment.appendChild(div);
    }
    this.el.nativeElement.appendChild(fragment);
  }
}

Using a document fragment batches DOM insertions, causing only one reflow and letting Angular run this after initial rendering.

📈 Performance GainSingle reflow triggered, reduces blocking time by 90% or more.

Manipulating DOM elements inside Angular directives

Angular

import { Directive, ElementRef } from '@angular/core';

@Directive({ selector: '[badDomManip]' })
export class BadDomManipDirective {
  constructor(private el: ElementRef) {
    for (let i = 0; i < 1000; i++) {
      const div = document.createElement('div');
      div.textContent = `Item ${i}`;
      this.el.nativeElement.appendChild(div);
    }
  }
}

This creates and appends 1000 DOM nodes synchronously during directive construction, blocking rendering and causing many reflows.

📉 Performance CostTriggers 1000 reflows and blocks rendering for 100+ ms on typical devices.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct DOM append in constructor	1000 nodes appended individually	1000 reflows	High paint cost	[X] Bad
Batch DOM append with DocumentFragment in ngAfterViewInit	1000 nodes appended once	1 reflow	Low paint cost	[OK] Good

Rendering Pipeline

Directive code runs during Angular's rendering cycle. Direct DOM changes cause style recalculations and layout reflows. Batching DOM updates reduces layout thrashing and paint cost.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout (reflow) stage is most expensive due to repeated DOM insertions.

Core Web Vital Affected

LCP, INP

This affects how fast the page renders and responds by controlling when and how DOM elements are created or changed.

Optimization Tips

1Avoid direct DOM manipulation in directive constructors to prevent blocking rendering.

2Use ngAfterViewInit lifecycle hook for heavy DOM updates to defer work until after initial paint.

3Batch DOM changes with DocumentFragment or Renderer2 to minimize reflows and paints.

Performance Quiz - 3 Questions

What is the main performance problem with manipulating DOM directly inside an Angular directive constructor?

A It increases CSS selector complexity.

B It blocks rendering by causing many reflows synchronously.

C It delays network requests.

D It reduces JavaScript bundle size.

DevTools: Performance

How to check: Record a performance profile while loading the page with the directive. Look for long scripting tasks and multiple layout events.

What to look for: Multiple layout (reflow) events and long scripting blocks indicate poor DOM manipulation. A single layout event with shorter scripting time indicates good performance.

Practice

1. What is the primary purpose of an Angular directive?

easy

A. To create new Angular modules

B. To add or change behavior on HTML elements

C. To define routes in the application

D. To manage HTTP requests

Solution

1. Step 1: Understand what directives do

   Directives in Angular are used to add or change behavior on HTML elements, such as changing styles or responding to events.

2. Step 2: Compare with other Angular features

   Modules organize code, routes manage navigation, and HTTP requests handle data fetching, which are not the main roles of directives.

3. Final Answer:

   To add or change behavior on HTML elements -> Option B

4. Quick Check:

   Directive purpose = Add/change behavior [OK]

Hint: Directives change element behavior, not app structure [OK]

Common Mistakes:

• Confusing directives with modules
• Thinking directives manage routing
• Assuming directives handle HTTP

2. Which syntax correctly injects Renderer2 in a directive's constructor?

easy

A. constructor(renderer: Renderer2 private) {}

B. constructor(Renderer2 private renderer) {}

C. constructor(private Renderer2 renderer) {}

D. constructor(private renderer: Renderer2) {}

Solution

1. Step 1: Recall Angular dependency injection syntax

   Angular uses TypeScript constructor parameters with access modifiers like 'private' before the variable name and type after the colon.

2. Step 2: Match correct syntax

   constructor(private renderer: Renderer2) {} follows the pattern: 'constructor(private renderer: Renderer2) {}'. Other options have incorrect order or missing colons.

3. Final Answer:

   constructor(private renderer: Renderer2) {} -> Option D

4. Quick Check:

   Correct DI syntax = private name: Type [OK]

Hint: Use 'private name: Type' in constructor for DI [OK]

Common Mistakes:

• Swapping parameter order
• Omitting colon between name and type
• Placing access modifier after type

3. Given this directive code, what will happen when the user clicks the host element?

import { Directive, HostListener, Renderer2, ElementRef } from '@angular/core';

@Directive({ selector: '[appHighlight]' })
export class HighlightDirective {
  constructor(private el: ElementRef, private renderer: Renderer2) {}

  @HostListener('click') onClick() {
    this.renderer.setStyle(this.el.nativeElement, 'backgroundColor', 'yellow');
  }
}

medium

A. The element's text color changes to yellow on click

B. Nothing happens on click

C. The element's background color changes to yellow on click

D. An error occurs because Renderer2 is not used correctly

Solution

1. Step 1: Understand @HostListener usage

   The @HostListener('click') decorator listens for click events on the host element and triggers the onClick method.

2. Step 2: Analyze onClick method

   Inside onClick, Renderer2 sets the backgroundColor style of the element to 'yellow'. This changes the element's background color on click.

3. Final Answer:

   The element's background color changes to yellow on click -> Option C

4. Quick Check:

   @HostListener + Renderer2 changes background [OK]

Hint: HostListener triggers method; Renderer2 safely changes style [OK]

Common Mistakes:

• Confusing backgroundColor with text color
• Assuming no effect without manual event binding
• Thinking Renderer2 usage causes error

4. Identify the error in this directive code snippet:

import { Directive, ElementRef, Renderer2 } from '@angular/core';

@Directive({ selector: '[appColor]' })
export class ColorDirective {
  constructor(el: ElementRef, renderer: Renderer2) {
    renderer.setStyle(el.nativeElement, 'color', 'blue');
  }
}

medium

A. Missing access modifiers in constructor parameters prevent DI

B. Renderer2 cannot set styles directly

C. Selector syntax is invalid

D. ElementRef should not be used in directives

Solution

1. Step 1: Check constructor parameters for DI

   Angular dependency injection requires constructor parameters to have access modifiers like 'private' or 'public' to assign them as class properties.

2. Step 2: Identify missing access modifiers

   Here, 'el' and 'renderer' lack 'private' or 'public', so Angular won't inject them properly, causing runtime errors.

3. Final Answer:

   Missing access modifiers in constructor parameters prevent DI -> Option A

4. Quick Check:

   DI needs access modifiers in constructor [OK]

Hint: Always add 'private' or 'public' for DI in constructor [OK]

Common Mistakes:

• Thinking Renderer2 can't set styles
• Believing selector syntax is wrong
• Assuming ElementRef is disallowed

5. You want to create a directive that toggles a CSS class active on the host element when the user hovers over it, and removes it when the mouse leaves. Which approach correctly implements this behavior?

hard

A. Use two @HostListener methods for 'mouseenter' and 'mouseleave' to add and remove the class using Renderer2

B. Use a single @HostListener for 'click' to toggle the class

C. Directly modify the element's classList without Renderer2 inside the constructor

D. Use @HostBinding to bind a boolean and toggle it manually without event listeners

Solution

1. Step 1: Understand event requirements

   Hover behavior requires reacting to 'mouseenter' and 'mouseleave' events to add and remove the class.

2. Step 2: Use Renderer2 with @HostListener

   Using two @HostListener methods for these events and Renderer2 to add/remove the 'active' class is the safe and correct Angular way.

3. Final Answer:

   Use two @HostListener methods for 'mouseenter' and 'mouseleave' to add and remove the class using Renderer2 -> Option A

4. Quick Check:

   Hover needs mouseenter/mouseleave + Renderer2 [OK]

Hint: Use separate HostListeners for mouseenter and mouseleave [OK]

Common Mistakes:

• Using click event instead of hover events
• Manipulating DOM directly without Renderer2
• Relying only on @HostBinding without events