POST requests in Angular - Performance & Optimization

Performance: POST requests

MEDIUM IMPACT

POST requests affect the time it takes to send data to the server and receive a response, impacting interaction responsiveness and perceived speed.

Sending form data to the server without blocking the UI

Angular

this.isLoading = true;
this.http.post('/api/data', largePayload).subscribe({
  next: response => { this.processResponse(response); },
  complete: () => { this.isLoading = false; },
  error: () => { this.isLoading = false; }
}); // shows loading state and provides feedback

Shows loading state and provides feedback to keep UI feeling responsive.

📈 Performance Gainimproves INP by providing feedback and preventing multiple submissions

Sending form data to the server without blocking the UI

Angular

this.http.post('/api/data', largePayload).subscribe(response => { this.processResponse(response); }); // no loading state or user feedback

This does not provide feedback, causing the UI to feel unresponsive until the request completes.

📉 Performance CostUI feels unresponsive during request, increases INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
POST without UI feedback	Minimal	0	Low but UI feels unresponsive	[X] Bad
Asynchronous POST with loading state	Minimal	0	Low and non-blocking	[OK] Good

Rendering Pipeline

POST requests run asynchronously outside the rendering pipeline but can affect rendering if UI updates wait for the response.

→Composite

→Paint

⚠️ BottleneckUI feeling unresponsive while waiting for POST response

Core Web Vital Affected

INP

POST requests affect the time it takes to send data to the server and receive a response, impacting interaction responsiveness and perceived speed.

Optimization Tips

1Provide loading indicators for all POST requests to improve perceived responsiveness.

2Show loading indicators during POST requests to improve user feedback.

3Keep POST payloads small to reduce network delay and improve responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk of sending large POST requests without loading states in Angular?

A It causes layout shifts (CLS) during rendering.

B It increases the page's Largest Contentful Paint (LCP).

C It causes the UI to feel unresponsive, causing slow interaction response.

D It reduces the bundle size.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR, and observe POST request timing and size.

What to look for: Look for long request durations or large payload sizes that delay response and affect interaction speed.

Practice

1. What is the main purpose of a POST request in Angular's HttpClient?

easy

A. To retrieve data from the server

B. To send data from the app to the server

C. To update the URL in the browser

D. To delete data on the server

Solution

1. Step 1: Understand HTTP methods

   POST requests are used to send data to a server, unlike GET which retrieves data.

2. Step 2: Relate to Angular HttpClient

   Angular's HttpClient.post() method sends data to the server endpoint.

3. Final Answer:

   To send data from the app to the server -> Option B

4. Quick Check:

   POST = send data [OK]

Hint: POST means sending data to server, not fetching [OK]

Common Mistakes:

• Confusing POST with GET method
• Thinking POST updates browser URL
• Assuming POST deletes data

2. Which of the following is the correct syntax to send a POST request using Angular's HttpClient?

easy

A. this.http.post('url', data).subscribe(response => console.log(response));

B. this.http.get('url', data).subscribe(response => console.log(response));

C. this.http.post('url').subscribe(data);

D. this.http.send('url', data).subscribe(response => console.log(response));

Solution

1. Step 1: Identify correct HttpClient method

   HttpClient.post() requires a URL and data object as parameters.

2. Step 2: Check subscription syntax

   subscribe() is used to handle the response asynchronously.

3. Final Answer:

   this.http.post('url', data).subscribe(response => console.log(response)); -> Option A

4. Quick Check:

   post(url, data) + subscribe() = correct syntax [OK]

Hint: Use post(url, data).subscribe() to send POST requests [OK]

Common Mistakes:

• Using get() instead of post()
• Omitting data parameter in post()
• Using non-existent send() method

3. What will be logged to the console when this Angular code runs?

this.http.post('https://api.example.com/items', {name: 'Book'}).subscribe(response => console.log(response));

medium

A. The URL string 'https://api.example.com/items'

B. An error because POST requests need no data

C. The server's response object after adding the item

D. Nothing, because subscribe() is missing

Solution

1. Step 1: Understand HttpClient.post behavior

   It sends data and waits for the server's response asynchronously.

2. Step 2: Analyze subscribe callback

   The response from the server is passed to the callback and logged.

3. Final Answer:

   The server's response object after adding the item -> Option C

4. Quick Check:

   subscribe logs server response [OK]

Hint: subscribe() logs server response from POST [OK]

Common Mistakes:

• Thinking POST requests don't need data
• Forgetting subscribe() to handle response
• Expecting URL string to be logged

4. Identify the error in this Angular POST request code:

this.http.post('https://api.example.com/data').subscribe(response => console.log(response));

medium

A. URL string is invalid

B. subscribe() method is not called correctly

C. HttpClient does not support POST requests

D. Missing data object as second argument in post()

Solution

1. Step 1: Check HttpClient.post parameters

   post() requires at least two arguments: URL and data to send.

2. Step 2: Identify missing data argument

   The code only provides URL, missing the data object to post.

3. Final Answer:

   Missing data object as second argument in post() -> Option D

4. Quick Check:

   post() needs URL and data [OK]

Hint: Always provide data object as second argument in post() [OK]

Common Mistakes:

• Omitting data argument in post()
• Misusing subscribe() syntax
• Assuming URL alone is enough

5. You want to send a POST request to add a new user with name and email, then update a message on success. Which Angular code snippet correctly does this?

hard

A. this.http.post('/api/users', {name: userName, email: userEmail}).subscribe(() => this.message = 'User added');

B. this.http.post('/api/users', userName, userEmail).subscribe(response => this.message = response);

C. this.http.post('/api/users').subscribe(response => this.message = 'User added');

D. this.http.get('/api/users', {name: userName, email: userEmail}).subscribe(() => this.message = 'User added');

Solution

1. Step 1: Verify POST request parameters

   POST requires URL and a single data object containing user info.

2. Step 2: Check subscribe callback updates message

   On success, the callback sets the message string correctly.

3. Final Answer:

   this.http.post('/api/users', {name: userName, email: userEmail}).subscribe(() => this.message = 'User added'); -> Option A

4. Quick Check:

   post(url, data).subscribe(() => update message) [OK]

Hint: POST needs data object; subscribe updates UI on success [OK]

Common Mistakes:

• Passing multiple arguments instead of one data object
• Using GET instead of POST for sending data
• Not updating message inside subscribe callback