@ContentChild and content projection in Angular - Performance & Optimization

Performance: @ContentChild and content projection

MEDIUM IMPACT

This concept affects rendering speed and interaction responsiveness by how Angular queries and projects DOM nodes inside components.

Accessing projected content efficiently inside a component

Angular

import { Component, ContentChild, AfterContentInit, ElementRef } from '@angular/core';

@Component({
  selector: 'good-projection',
  template: `<ng-content></ng-content>`
})
export class GoodProjectionComponent implements AfterContentInit {
  @ContentChild('projectedRef', { static: false }) projectedElement!: ElementRef;

  ngAfterContentInit() {
    const el = this.projectedElement.nativeElement;
    const height = el.offsetHeight;
    const width = el.offsetWidth;
    console.log(height, width);
  }
}

Caching nativeElement properties reduces layout thrashing by avoiding repeated reflows.

📈 Performance GainSingle reflow triggered instead of multiple, improving input responsiveness.

Accessing projected content efficiently inside a component

Angular

import { Component, ContentChild, AfterContentInit, ElementRef } from '@angular/core';

@Component({
  selector: 'bad-projection',
  template: `<ng-content></ng-content>`
})
export class BadProjectionComponent implements AfterContentInit {
  @ContentChild('projectedRef', { static: false }) projectedElement!: ElementRef;

  ngAfterContentInit() {
    // Accessing nativeElement multiple times
    console.log(this.projectedElement.nativeElement.offsetHeight);
    console.log(this.projectedElement.nativeElement.offsetWidth);
  }
}

Accessing nativeElement properties multiple times triggers multiple layout calculations causing reflows.

📉 Performance CostTriggers 2 reflows per component instance, slowing interaction responsiveness.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple nativeElement reads in ngAfterContentInit	Single query, multiple property reads	2 reflows	Medium paint cost	[X] Bad
Single nativeElement read cached in variable	Single query, single property read	1 reflow	Low paint cost	[OK] Good
@ContentChild query in ngAfterContentChecked	Multiple queries per cycle	Multiple reflows	High paint cost	[X] Bad
@ContentChild query in ngAfterContentInit only	Single query	1 reflow	Low paint cost	[OK] Good

Rendering Pipeline

Angular processes content projection by inserting projected nodes into the component's view. @ContentChild queries the projected DOM nodes after projection. Accessing nativeElement properties can trigger style recalculations and layout (reflow).

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout stage is most expensive due to reflows triggered by DOM property reads.

Core Web Vital Affected

INP

This concept affects rendering speed and interaction responsiveness by how Angular queries and projects DOM nodes inside components.

Optimization Tips

1Query @ContentChild once in ngAfterContentInit, not repeatedly in ngAfterContentChecked.

2Cache nativeElement properties to avoid multiple layout reflows.

3Avoid heavy DOM access inside frequently called lifecycle hooks to keep interaction smooth.

Performance Quiz - 3 Questions

What is the main performance risk when accessing nativeElement properties multiple times in @ContentChild?

A Increases JavaScript bundle size

B Triggers multiple layout reflows slowing interaction

C Blocks network requests

D Causes memory leaks

DevTools: Performance

How to check: Open Chrome DevTools > Performance tab. Record while interacting with the component. Look for Layout events and their frequency.

What to look for: Frequent Layout events indicate repeated reflows caused by DOM property reads or queries. Fewer Layout events mean better performance.

Practice

1. What does the Angular decorator @ContentChild do in a component?

easy

A. It projects content from the component into its parent.

B. It creates a new child component inside the template.

C. It gets a reference to a single element inside the projected content.

D. It listens to events emitted by child components.

Solution

1. Step 1: Understand content projection

   Content projection allows inserting external content inside a component using <ng-content>.

2. Step 2: Role of @ContentChild

   @ContentChild gets a reference to a single element or directive inside that projected content.

3. Final Answer:

   It gets a reference to a single element inside the projected content. -> Option C

4. Quick Check:

   @ContentChild = reference to projected element [OK]

Hint: Remember: @ContentChild targets projected content elements [OK]

Common Mistakes:

• Confusing @ContentChild with @ViewChild
• Thinking it creates new elements
• Assuming it projects content instead of referencing it

2. Which of the following is the correct syntax to use @ContentChild to get a reference to a template variable named myRef?

easy

A. @ContentChild('myRef') myElement!: ElementRef;

B. @ContentChild(myRef) myElement!: ElementRef;

C. @ContentChild(#myRef) myElement!: ElementRef;

D. @ContentChild(myRef, {static: true}) myElement!: ElementRef;

Solution

1. Step 1: Correct syntax for @ContentChild selector

   The selector must be a string matching the template variable name, so it should be quoted: 'myRef'.

2. Step 2: Static option usage

   Static option is optional and usually false by default; not required here.

3. Final Answer:

   @ContentChild('myRef') myElement!: ElementRef; -> Option A

4. Quick Check:

   Use quotes around template variable name in @ContentChild [OK]

Hint: Use quotes around template variable name in @ContentChild [OK]

Common Mistakes:

• Omitting quotes around the selector string
• Using # inside the selector string
• Confusing static option necessity

3. Given this component code:

@Component({ selector: 'child-comp', template: `` })
export class ChildComp {
  @ContentChild('proj') projElement!: ElementRef;

  ngAfterContentInit() {
    console.log(this.projElement.nativeElement.textContent);
  }
}

And usage:

Hello World

What will be logged to the console?

medium

A. Hello World

B. undefined

C. Error: projElement is undefined

D. Empty string

Solution

1. Step 1: Understand content projection and @ContentChild

   The <p #proj> is projected inside <ng-content>. @ContentChild('proj') gets its reference.

2. Step 2: ngAfterContentInit timing

   ngAfterContentInit runs after projected content is initialized, so projElement is defined and accessible.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   Projected element text logged correctly [OK]

Hint: Use ngAfterContentInit to access projected content safely [OK]

Common Mistakes:

• Trying to access projElement before ngAfterContentInit
• Assuming @ContentChild does not find projected elements
• Confusing @ViewChild with @ContentChild

4. Consider this component code:

@Component({ selector: 'proj-comp', template: `` })
export class ProjComp {
  @ContentChild('item') itemRef!: ElementRef;

  ngOnInit() {
    console.log(this.itemRef.nativeElement.textContent);
  }
}

And usage:

Test

What problem will occur when running this code?

medium

A. Logs 'Test' correctly

B. Error because itemRef is undefined in ngOnInit

C. Syntax error due to missing decorator

D. Logs empty string

Solution

1. Step 1: Lifecycle hook timing for @ContentChild

   @ContentChild references are not available in ngOnInit; they become available in ngAfterContentInit.

2. Step 2: Accessing itemRef in ngOnInit

   Accessing itemRef in ngOnInit causes it to be undefined, leading to runtime error when accessing nativeElement.

3. Final Answer:

   Error because itemRef is undefined in ngOnInit -> Option B

4. Quick Check:

   Use ngAfterContentInit for @ContentChild access [OK]

Hint: Access @ContentChild only in ngAfterContentInit [OK]

Common Mistakes:

• Accessing @ContentChild in ngOnInit
• Assuming @ContentChild is available immediately
• Ignoring lifecycle hook order

5. You want to create a component that projects multiple paragraphs and highlights the first paragraph. Which approach correctly achieves this?

Options:
A) Use @ContentChildren('para') and highlight the first in the list.
B) Use @ContentChild('para') and add #para to the first paragraph only.
C) Use @ViewChild('para') inside the component template.
D) Use @ContentChild without a selector and highlight all paragraphs.

hard

A. Use @ContentChild without a selector and highlight all paragraphs.

B. Use @ContentChild('para') and add #para to the first paragraph only.

C. Use @ViewChild('para') inside the component template.

D. Use @ContentChildren('para') and highlight the first in the list.

Solution

1. Step 1: Understand multiple projected elements

   When projecting multiple elements with the same template variable, use @ContentChildren to get all references.

2. Step 2: Highlight the first paragraph

   @ContentChildren returns a QueryList; you can access the first element and apply highlight logic.

3. Final Answer:

   Use @ContentChildren('para') and highlight the first in the list. -> Option D

4. Quick Check:

   Multiple projected elements need @ContentChildren [OK]

Hint: Use @ContentChildren for multiple projected elements [OK]

Common Mistakes:

• Using @ContentChild for multiple elements
• Using @ViewChild for projected content
• Omitting selector in @ContentChild