Route guards (canActivate, canDeactivate) in Angular - Performance & Optimization

Performance: Route guards (canActivate, canDeactivate)

MEDIUM IMPACT

Route guards affect the initial navigation speed and responsiveness when changing routes in an Angular app.

Protecting routes with guards that check user permissions

Angular

async canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Promise<boolean> {
  // Async non-blocking permission check
  const result = await this.permissionService.checkPermissionsAsync();
  return result;
}

Using async guards allows Angular to handle navigation without blocking UI thread.

📈 Performance GainImproves responsiveness by avoiding main thread blocking, reducing INP.

Protecting routes with guards that check user permissions

Angular

canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
  // Synchronous heavy computation or blocking call
  const result = this.heavyPermissionCheck();
  return result;
}

Blocking synchronous logic in canActivate delays route activation and blocks UI updates.

📉 Performance CostBlocks rendering and user interaction until guard completes, increasing INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous heavy guard	0 (no DOM changes yet)	0	Blocks paint until done	[X] Bad
Asynchronous guard with Promise	0	0	Non-blocking paint	[OK] Good

Rendering Pipeline

Route guards run before route activation, blocking navigation until they resolve. This affects the browser's ability to paint the new view and respond to user input.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution blocking navigation delays subsequent rendering stages.

Core Web Vital Affected

INP

Route guards affect the initial navigation speed and responsiveness when changing routes in an Angular app.

Optimization Tips

1Avoid heavy synchronous code in route guards to prevent blocking navigation.

2Use asynchronous guards with Promises or Observables to keep UI responsive.

3Test route guard performance using browser DevTools Performance panel.

Performance Quiz - 3 Questions

What is the main performance risk of using synchronous logic in canActivate guards?

A It causes layout shifts after the route loads.

B It increases the bundle size significantly.

C It blocks the main thread, delaying route activation and user interaction.

D It improves initial page load speed.

DevTools: Performance

How to check: Record a navigation in the Performance panel and look for long tasks or scripting blocking the main thread during route change.

What to look for: Long JavaScript execution blocking paint and input responsiveness indicates slow guards.

Practice

1. What is the primary purpose of the canActivate guard in Angular routing?

easy

A. To handle errors during route navigation.

B. To check if navigation to a route is allowed before entering it.

C. To preload data before the route loads.

D. To confirm if navigation away from a route is allowed.

Solution

1. Step 1: Understand the role of canActivate

   canActivate is a route guard that runs before entering a route to decide if navigation is allowed.

2. Step 2: Differentiate from other guards

   canDeactivate checks leaving a route, not entering. Preloading and error handling are unrelated to canActivate.

3. Final Answer:

   To check if navigation to a route is allowed before entering it. -> Option B

4. Quick Check:

   canActivate = check before entering route [OK]

Hint: canActivate controls entering routes, canDeactivate controls leaving [OK]

Common Mistakes:

• Confusing canActivate with canDeactivate
• Thinking canActivate preloads data
• Assuming canActivate handles errors

2. Which of the following is the correct syntax to apply a canDeactivate guard to a route in Angular?

easy

A. { path: 'edit', component: EditComponent, canDeactivate: [UnsavedChangesGuard] }

B. { path: 'edit', component: EditComponent, canLoad: [LoadGuard] }

C. { path: 'edit', component: EditComponent, canActivate: [AuthGuard] }

D. { path: 'edit', component: EditComponent, canActivateChild: [ChildGuard] }

Solution

1. Step 1: Identify the guard type for leaving routes

   canDeactivate is used to check if navigation away from a route is allowed.

2. Step 2: Match syntax with canDeactivate

   The correct syntax uses canDeactivate: [GuardName] inside the route object.

3. Final Answer:

   { path: 'edit', component: EditComponent, canDeactivate: [UnsavedChangesGuard] } -> Option A

4. Quick Check:

   canDeactivate syntax = canDeactivate: [Guard] [OK]

Hint: Use canDeactivate: [Guard] to protect leaving a route [OK]

Common Mistakes:

• Using canActivate instead of canDeactivate for leaving routes
• Confusing canLoad with canDeactivate
• Missing brackets around guard name

3. Given this canDeactivate guard code snippet, what will happen when the user tries to leave the EditComponent with unsaved changes?

export class UnsavedChangesGuard implements CanDeactivate<EditComponent> {
  canDeactivate(component: EditComponent): boolean {
    if (component.hasUnsavedChanges()) {
      return confirm('You have unsaved changes. Leave anyway?');
    }
    return true;
  }
}

medium

A. The guard throws an error because confirm is not allowed.

B. The user is always allowed to leave without confirmation.

C. The user is blocked from leaving if there are unsaved changes.

D. The user is asked to confirm leaving only if there are unsaved changes.

Solution

1. Step 1: Analyze the guard logic

   The guard checks if component.hasUnsavedChanges() returns true, then asks for confirmation.

2. Step 2: Understand the confirm behavior

   If the user confirms, confirm() returns true allowing navigation; otherwise, navigation is blocked.

3. Final Answer:

   The user is asked to confirm leaving only if there are unsaved changes. -> Option D

4. Quick Check:

   canDeactivate confirms only if unsaved changes exist [OK]

Hint: canDeactivate can prompt user to confirm leaving [OK]

Common Mistakes:

• Assuming user can leave without confirmation always
• Thinking guard blocks leaving without prompt
• Believing confirm causes errors in Angular guards

4. Identify the error in this canActivate guard implementation:

export class AuthGuard implements CanActivate {
  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) {
    if (this.authService.isLoggedIn()) {
      return true;
    }
  }
}

medium

A. Missing return statement when user is not logged in.

B. Incorrect method name; should be canDeactivate.

C. The guard should return a Promise, not boolean.

D. The guard must not use services inside canActivate.

Solution

1. Step 1: Check all code paths return a value

   If isLoggedIn() is false, the method returns nothing (undefined), which is invalid.

2. Step 2: Understand guard return requirements

   canActivate must return true, false, or an observable/promise resolving to those. Missing return causes errors.

3. Final Answer:

   Missing return statement when user is not logged in. -> Option A

4. Quick Check:

   All canActivate paths must return true/false [OK]

Hint: Always return true or false in all canActivate paths [OK]

Common Mistakes:

• Not returning false or redirect when unauthorized
• Confusing canActivate with canDeactivate method names
• Thinking services can't be used in guards

5. You want to prevent users from leaving a form page if they have unsaved changes, but only if they are editing (not creating new). Which approach correctly uses canDeactivate to achieve this?

hard

A. Use canActivate guard to check unsaved changes before entering the form route.

B. Use canDeactivate guard that always returns true to allow navigation.

C. Use canDeactivate guard that checks component.isEditing and component.hasUnsavedChanges() before confirming navigation.

D. Use canActivateChild guard to block leaving the form.

Solution

1. Step 1: Identify when to block navigation away

   Blocking leaving only applies when editing and unsaved changes exist, so guard must check both conditions.

2. Step 2: Use canDeactivate guard properly

   canDeactivate runs when leaving a route, so it is the correct place to check and confirm navigation.

3. Final Answer:

   Use canDeactivate guard that checks component.isEditing and component.hasUnsavedChanges() before confirming navigation. -> Option C

4. Quick Check:

   canDeactivate with condition on editing and unsaved changes [OK]

Hint: Check editing and unsaved changes inside canDeactivate guard [OK]

Common Mistakes:

• Using canActivate to block leaving routes
• Always returning true in canDeactivate guard
• Confusing canActivateChild with canDeactivate