GET requests in Angular - Performance & Optimization

Performance: GET requests

MEDIUM IMPACT

GET requests impact page load speed and interaction responsiveness by controlling how fast data is fetched and rendered.

Fetching data on component load

Angular

ngOnInit() {
  forkJoin({
    data: this.http.get('/api/data'),
    extra: this.http.get('/api/extra')
  }).subscribe(results => {
    this.data = results.data;
    this.extra = results.extra;
  });
}

Combines requests to run in parallel and handle results together, reducing overhead and improving load speed.

📈 Performance GainSingle subscription reduces overhead; faster data availability improves LCP.

Fetching data on component load

Angular

ngOnInit() {
  this.http.get('/api/data').subscribe(data => {
    this.data = data;
  });
  this.http.get('/api/extra').subscribe(extra => {
    this.extra = extra;
  });
}

Multiple GET requests fired simultaneously without batching increase network overhead and delay rendering.

📉 Performance CostBlocks rendering until both requests complete; increases total load time by multiple round trips.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple separate GET requests	Multiple DOM updates	Multiple reflows triggered	Higher paint cost due to incremental updates	[X] Bad
Batched GET requests with forkJoin	Single DOM update	Single reflow	Lower paint cost with consolidated update	[OK] Good

Rendering Pipeline

GET requests start in the network stage, then data parsing affects scripting, which triggers DOM updates and layout recalculations.

→Network

→Scripting

→Layout

→Paint

⚠️ BottleneckNetwork latency and blocking JavaScript execution waiting for data

Core Web Vital Affected

LCP

GET requests impact page load speed and interaction responsiveness by controlling how fast data is fetched and rendered.

Optimization Tips

1Batch multiple GET requests to reduce network overhead and DOM updates.

2Cache GET request results to avoid repeated network delays.

3Avoid blocking rendering by lazy loading non-critical GET requests.

Performance Quiz - 3 Questions

What is a main performance drawback of firing multiple separate GET requests on component load?

A Increases network overhead and delays content rendering

B Reduces network overhead by parallelizing requests

C Improves caching automatically

D Triggers fewer DOM updates

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR, reload page and observe GET requests timing and count.

What to look for: Look for multiple similar GET requests and their timing; fewer and faster requests indicate better performance.

Practice

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

easy

A. To update existing data on the server

B. To send new data to the server

C. To delete data from the server

D. To retrieve data from a server without changing it

Solution

1. Step 1: Understand GET request purpose

   GET requests are used to ask the server to send data without modifying it.

2. Step 2: Compare with other HTTP methods

   POST sends new data, DELETE removes data, PUT/PATCH updates data, so they are not GET.

3. Final Answer:

   To retrieve data from a server without changing it -> Option D

4. Quick Check:

   GET = retrieve data [OK]

Hint: GET always fetches data without changing it [OK]

Common Mistakes:

• Confusing GET with POST or DELETE
• Thinking GET modifies server data
• Using GET to send data in the request body

2. Which of the following is the correct way to make a GET request using Angular's HttpClient?

easy

A. this.http.get('url').subscribe(data => console.log(data));

B. this.http.post('url').subscribe(data => console.log(data));

C. this.http.delete('url').subscribe(data => console.log(data));

D. this.http.put('url').subscribe(data => console.log(data));

Solution

1. Step 1: Identify HttpClient method for GET

   The method to fetch data is get() on HttpClient.

2. Step 2: Check syntax with subscribe

   Using subscribe handles the asynchronous response correctly.

3. Final Answer:

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

4. Quick Check:

   HttpClient.get() + subscribe = correct GET syntax [OK]

Hint: Use http.get() with subscribe to fetch data [OK]

Common Mistakes:

• Using post(), delete(), or put() instead of get()
• Forgetting to subscribe to the observable
• Calling get() without parentheses

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

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

medium

A. The data received from the API endpoint

B. An error message because subscribe is missing

C. Nothing, because get() does not return data

D. A syntax error due to wrong method usage

Solution

1. Step 1: Understand HttpClient.get() behavior

   The get() method returns an observable that emits the data from the API.

2. Step 2: Effect of subscribe()

   Calling subscribe() listens to the observable and runs the callback with the data, logging it.

3. Final Answer:

   The data received from the API endpoint -> Option A

4. Quick Check:

   subscribe logs API data [OK]

Hint: subscribe callback logs the fetched data [OK]

Common Mistakes:

• Assuming get() returns data directly without subscribe
• Thinking subscribe is optional
• Confusing observable with promise

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

this.http.get('https://api.example.com/data').subscribe(data => this.data = data);

Assuming this.http is properly injected and data is a class property.

medium

A. GET request URL is invalid

B. HttpClient is not imported

C. Missing error handling in subscribe

D. subscribe callback uses wrong arrow function syntax

Solution

1. Step 1: Check syntax and usage

   The get() call and subscribe syntax are correct, and this.http is assumed injected.

2. Step 2: Identify missing best practice

   No error handling is provided in subscribe, which can cause silent failures.

3. Final Answer:

   Missing error handling in subscribe -> Option C

4. Quick Check:

   Always add error handling in subscribe [OK]

Hint: Always handle errors in subscribe to catch failures [OK]

Common Mistakes:

• Ignoring error callback in subscribe
• Assuming URL is invalid without checking
• Confusing arrow function syntax

5. You want to load a list of users from an API and display them in your Angular component. Which approach correctly combines GET request and updating the component's state?

hard

A. Call this.http.post('api/users').subscribe(users => this.users = users); in constructor

B. Use this.http.get('api/users').subscribe(users => this.users = users); in ngOnInit

C. Assign this.users = this.http.get('api/users'); directly without subscribe

D. Use this.http.delete('api/users').subscribe(users => this.users = users); in ngOnInit

Solution

1. Step 1: Choose correct HTTP method and lifecycle hook

   GET is used to fetch data; ngOnInit is the right place to load data after component creation.

2. Step 2: Use subscribe to update component state

   Subscribe receives data asynchronously and assigns it to this.users for display.

3. Final Answer:

   Use this.http.get('api/users').subscribe(users => this.users = users); in ngOnInit -> Option B

4. Quick Check:

   GET + subscribe + ngOnInit = correct pattern [OK]

Hint: Load data in ngOnInit with http.get() and subscribe [OK]

Common Mistakes:

• Using POST or DELETE instead of GET
• Assigning observable directly without subscribe
• Loading data in constructor instead of ngOnInit