Handling HTTP errors in Angular - Performance & Optimization

Performance: Handling HTTP errors

MEDIUM IMPACT

This affects the responsiveness and smoothness of user interactions by managing how HTTP errors impact UI updates and loading states.

Handling HTTP errors in Angular services

Angular

this.http.get('/api/data').pipe(catchError(err => { this.errorMessage = 'Failed to load data'; return of([]); })).subscribe(data => { this.data = data; });

Using catchError with a fallback observable avoids blocking UI and allows graceful error display.

📈 Performance Gainnon-blocking error handling improves INP and user experience

Handling HTTP errors in Angular services

Angular

this.http.get('/api/data').subscribe(data => { this.data = data; }, error => { alert('Error occurred'); });

Using alert blocks the main thread and interrupts user interaction, causing poor responsiveness.

📉 Performance Costblocks rendering and user input for the alert duration

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking alert on error	Minimal	0	Blocks UI thread causing delayed paint	[X] Bad
Non-blocking catchError with fallback	Minimal	1 (UI update)	Efficient paint with minimal reflow	[OK] Good
Blind retry without delay	Minimal	0	Delays error feedback, increasing perceived latency	[!] OK
Retry with delay and limit	Minimal	1 (UI update)	Balanced paint cost with timely feedback	[OK] Good

Rendering Pipeline

HTTP error handling affects the interaction phase by controlling when and how UI updates occur after network responses, influencing layout and paint operations.

→JavaScript Execution

→Layout

→Paint

→Composite

⚠️ BottleneckJavaScript Execution when blocking UI or handling errors inefficiently

Core Web Vital Affected

INP

This affects the responsiveness and smoothness of user interactions by managing how HTTP errors impact UI updates and loading states.

Optimization Tips

1Avoid blocking UI calls like alert() in HTTP error handlers.

2Use RxJS operators like catchError and retryWhen with delays to handle errors gracefully.

3Update UI state asynchronously to minimize layout and paint costs.

Performance Quiz - 3 Questions

What is a performance drawback of using alert() inside an HTTP error handler in Angular?

A It causes layout thrashing.

B It blocks the main thread and delays user interaction.

C It increases network requests.

D It reduces bundle size.

DevTools: Performance

How to check: Record a session while triggering HTTP errors; look for long tasks or blocked frames during error handling.

What to look for: Check for main thread blocking and long JavaScript execution times that delay UI updates.

Practice

1. What is the main purpose of using catchError in Angular HTTP requests?

easy

A. To handle errors that occur during the HTTP request

B. To retry the HTTP request automatically

C. To transform the HTTP response data

D. To cancel the HTTP request

Solution

1. Step 1: Understand the role of catchError

   catchError is used to catch errors in an observable stream, such as HTTP requests.

2. Step 2: Identify its purpose in HTTP requests

   It allows handling errors gracefully instead of letting them crash the app or go unhandled.

3. Final Answer:

   To handle errors that occur during the HTTP request -> Option A

4. Quick Check:

   catchError handles HTTP errors = A [OK]

Hint: Remember catchError catches errors in observable streams [OK]

Common Mistakes:

• Thinking catchError retries requests automatically
• Confusing catchError with data transformation operators
• Assuming catchError cancels requests

2. Which of the following is the correct syntax to catch HTTP errors in Angular using RxJS operators?

easy

A. this.http.get(url).catchError(error => throwError(error))

B. this.http.get(url).pipe(catchError(error => throwError(() => error)))

C. this.http.get(url).pipe(map(error => throwError(error)))

D. this.http.get(url).subscribe(catchError(error => throwError(error)))

Solution

1. Step 1: Recognize correct RxJS operator usage

   In Angular, pipe() is used to chain operators like catchError.

2. Step 2: Check the syntax of catchError

   The correct form is catchError(error => throwError(() => error)) inside pipe().

3. Final Answer:

   this.http.get(url).pipe(catchError(error => throwError(() => error))) -> Option B

4. Quick Check:

   Use pipe with catchError and throwError = B [OK]

Hint: Always use pipe() to chain catchError in Angular HTTP calls [OK]

Common Mistakes:

• Using catchError outside pipe()
• Using map instead of catchError for errors
• Passing throwError without a function wrapper

3. Consider this Angular service code snippet:

getData() {
  return this.http.get('/api/data').pipe(
    catchError(err => {
      console.error('Error:', err.message);
      return throwError(() => new Error('Failed to load data'));
    })
  );
}

What will happen when the HTTP request fails?

medium

A. The HTTP request is retried automatically

B. The error is ignored and the observable completes successfully

C. The error is logged and a new error is passed to subscribers

D. The app crashes due to unhandled error

Solution

1. Step 1: Analyze catchError behavior on failure

   When the HTTP request fails, catchError runs, logging the error message.

2. Step 2: Understand throwError usage

   It returns a new error observable with a friendly message, passing it to subscribers.

3. Final Answer:

   The error is logged and a new error is passed to subscribers -> Option C

4. Quick Check:

   catchError logs and rethrows error = A [OK]

Hint: catchError logs error then returns throwError to notify subscribers [OK]

Common Mistakes:

• Assuming error is ignored or swallowed
• Thinking HTTP request retries automatically
• Believing app crashes without catchError

4. Identify the error in this Angular HTTP error handling code:

this.http.get('/api/items').pipe(
  catchError(error => {
    console.log('Error:', error);
    return throwError(error);
  })
).subscribe(data => console.log(data));

medium

A. throwError should be called with a function: throwError(() => error)

B. catchError should be outside pipe()

C. subscribe should be before pipe()

D. console.log cannot be used inside catchError

Solution

1. Step 1: Check throwError usage

   In RxJS 7+, throwError requires a function returning the error: throwError(() => error).

2. Step 2: Verify catchError and subscribe placement

   catchError must be inside pipe(), and subscribe after pipe(), which is correct here.

3. Final Answer:

   throwError should be called with a function: throwError(() => error) -> Option A

4. Quick Check:

   throwError needs function wrapper = D [OK]

Hint: Use throwError(() => error) to avoid RxJS errors [OK]

Common Mistakes:

• Calling throwError directly with error object
• Placing catchError outside pipe()
• Misordering subscribe and pipe()

5. You want to show a friendly message to users when an HTTP error occurs, but still log the original error for debugging. Which code snippet correctly implements this in Angular?

hard

A. return this.http.get(url).pipe(catchError(err => { console.error(err); return of('Error occurred'); }))

B. return this.http.get(url).pipe(catchError(err => { return throwError(() => new Error('Error occurred')); }))

C. return this.http.get(url).pipe(catchError(err => { alert(err.message); return throwError(() => err); }))

D. return this.http.get(url).pipe(catchError(err => { alert('Error occurred'); console.error(err); return throwError(() => err); }))

Solution

1. Step 1: Check user notification and logging

   return this.http.get(url).pipe(catchError(err => { alert('Error occurred'); console.error(err); return throwError(() => err); })) shows an alert to users and logs the error to console, fulfilling both requirements.

2. Step 2: Verify error propagation

   It returns throwError(() => err) to pass the error downstream for further handling.

3. Final Answer:

   return this.http.get(url).pipe(catchError(err => { alert('Error occurred'); console.error(err); return throwError(() => err); })) -> Option D

4. Quick Check:

   Alert user + log error + rethrow = C [OK]

Hint: Alert user, log error, then rethrow with throwError(() => err) [OK]

Common Mistakes:

• Not alerting user or not logging error
• Returning a string instead of throwing error
• Alerting raw error message confusing users