Why components are the building blocks in Angular - Performance Evidence

Performance: Why components are the building blocks

MEDIUM IMPACT

This concept affects how efficiently the browser renders and updates the UI by managing DOM complexity and reflows.

Building a UI with reusable and maintainable parts

Angular

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

@Component({
  selector: 'app-title',
  template: `<h1>Title</h1>`
})
export class TitleComponent {}

@Component({
  selector: 'app-button',
  template: `<button (click)="clickHandler()">Click</button>`
})
export class ButtonComponent {
  clickHandler() {
    console.log('Clicked');
  }
}

@Component({
  selector: 'app-root',
  template: `<app-title></app-title><p>Paragraph</p><app-button></app-button>`
})
export class AppComponent {}

Splitting UI into components reduces DOM size per component and isolates updates, minimizing reflows.

📈 Performance GainSingle reflow per component update; smaller DOM trees improve rendering and responsiveness.

Building a UI with reusable and maintainable parts

Angular

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

@Component({
  selector: 'app-root',
  template: `<div><h1>Title</h1><p>Paragraph</p><button (click)="clickHandler()">Click</button></div>`
})
export class AppComponent {
  clickHandler() {
    console.log('Clicked');
  }
}

All UI elements are in one big component causing large DOM and frequent reflows on any change.

📉 Performance CostTriggers multiple reflows on any update; large DOM tree slows rendering and interaction.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Single large component	High DOM nodes in one tree	Multiple reflows on any change	High paint cost due to large updates	[X] Bad
Multiple small components	Smaller DOM per component	Single reflow per component update	Lower paint cost with isolated updates	[OK] Good

Rendering Pipeline

Angular components create isolated DOM subtrees. When state changes, only affected components re-render, reducing layout recalculations and paint.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout stage due to large DOM and frequent updates

Core Web Vital Affected

INP

This concept affects how efficiently the browser renders and updates the UI by managing DOM complexity and reflows.

Optimization Tips

1Break UI into small, reusable Angular components to limit DOM size.

2Update only the components that need changes to reduce reflows.

3Avoid large monolithic components to improve interaction responsiveness.

Performance Quiz - 3 Questions

How do Angular components improve page interaction performance?

A By using inline styles to speed up CSS parsing

B By loading all HTML at once to avoid delays

C By isolating DOM updates to smaller parts, reducing reflows

D By disabling browser caching for fresh content

DevTools: Performance

How to check: Record a performance profile while interacting with the app. Look for layout and paint events and their duration.

What to look for: Long layout times and frequent reflows indicate poor component structure; shorter, isolated updates indicate good performance.

Practice

1. Why are components considered the building blocks in Angular applications?

easy

A. Because they split the app into small, manageable pieces with their own HTML, CSS, and logic.

B. Because they replace the need for services and modules entirely.

C. Because they only contain CSS styles for the app.

D. Because they are used only for routing between pages.

Solution

1. Step 1: Understand the role of components

   Components divide the app into smaller parts, each with its own structure and behavior.

2. Step 2: Recognize what components contain

   Each component has its own HTML, CSS, and logic, making the app easier to build and maintain.

3. Final Answer:

   Because they split the app into small, manageable pieces with their own HTML, CSS, and logic. -> Option A

4. Quick Check:

   Components = small parts with own code [OK]

Hint: Components bundle HTML, CSS, and logic into small parts [OK]

Common Mistakes:

• Thinking components only hold styles
• Confusing components with services
• Believing components handle routing only

2. Which of the following is the correct way to define a basic Angular component?

easy

A. function SampleComponent() { selector: 'app-sample' }

B. @Component({ selector: 'app-sample', templateUrl: './sample.html' }) export class SampleComponent {}

C. @Component({ selector: 'app-sample' }) function SampleComponent() {}

D. class SampleComponent { selector = 'app-sample' }

Solution

1. Step 1: Identify Angular component syntax

   Angular components use the @Component decorator with metadata like selector and templateUrl.

2. Step 2: Check the class declaration

   The component must be a class exported with the decorator above it.

3. Final Answer:

   @Component({ selector: 'app-sample', templateUrl: './sample.html' }) export class SampleComponent {} -> Option B

4. Quick Check:

   @Component decorator + class = correct syntax [OK]

Hint: Look for @Component decorator above an exported class [OK]

Common Mistakes:

• Using function instead of class for components
• Missing @Component decorator
• Placing selector inside class body without decorator

3. Given this Angular component template:

<h1>{{title}}</h1>
<p>Welcome to {{appName}}!</p>

and this component class:

export class WelcomeComponent {
  title = 'Hello';
  appName = 'MyApp';
}

What will be the rendered output in the browser?

medium

A. HelloWelcome to {{appName}}!

B. {{title}}Welcome to {{appName}}!

C. HelloWelcome to MyApp!

D. {{title}}Welcome to MyApp!

Solution

1. Step 1: Understand Angular interpolation

   Angular replaces {{variable}} with the variable's value from the component class.

2. Step 2: Substitute variables in the template

   title = 'Hello' and appName = 'MyApp', so the template renders with these values.

3. Final Answer:

   <h1>Hello</h1><p>Welcome to MyApp!</p> -> Option C

4. Quick Check:

   Interpolation replaces variables with values [OK]

Hint: Remember {{}} shows variable values in template [OK]

Common Mistakes:

• Thinking {{}} stays as text in output
• Mixing variable names or values
• Ignoring component class properties

4. Identify the error in this Angular component code:

@Component({
  selector: 'app-test',
  template: '<p>Test works!</p>'
})
export class TestComponent {
  title = 'Test';
  constructor() {
    this.title = 123;
  }
}

medium

A. Assigning a number to a string property 'title' causes a type error.

B. Missing @Injectable decorator on the class.

C. Template string should use backticks instead of single quotes.

D. Selector name 'app-test' is invalid.

Solution

1. Step 1: Check property type consistency

   title is initialized as a string 'Test', but later assigned a number 123, which is a type mismatch.

2. Step 2: Verify other parts for errors

   @Injectable is not required for components, template string with single quotes is valid, and selector 'app-test' is valid.

3. Final Answer:

   Assigning a number to a string property 'title' causes a type error. -> Option A

4. Quick Check:

   Property type mismatch = error [OK]

Hint: Check if property types stay consistent in constructor [OK]

Common Mistakes:

• Thinking @Injectable is needed for components
• Believing template string quotes cause error
• Assuming selector names must be different

5. You want to build a dashboard app with multiple sections like header, sidebar, and content. Why should you use components for each section instead of writing all HTML and logic in one file?

hard

A. Because writing all code in one file is faster and recommended for large apps.

B. Because Angular requires every section to be a separate component by default.

C. Because components automatically improve app speed without any extra work.

D. Because components let you reuse, maintain, and test each section separately, making the app easier to manage.

Solution

1. Step 1: Understand component benefits

   Components break the app into smaller parts that can be reused, tested, and maintained independently.

2. Step 2: Compare with single-file approach

   Writing all code in one file makes it hard to manage, debug, and update as the app grows.

3. Final Answer:

   Because components let you reuse, maintain, and test each section separately, making the app easier to manage. -> Option D

4. Quick Check:

   Components improve manageability and reuse [OK]

Hint: Use components to split and manage app parts easily [OK]

Common Mistakes:

• Thinking Angular forces components for every section
• Believing components alone boost speed automatically
• Assuming one big file is better for large apps