Returning different status codes in Spring Boot - Performance & Optimization

Performance: Returning different status codes

MEDIUM IMPACT

This affects the server response time and perceived page load speed by the client, impacting how quickly the browser can proceed after receiving the status code.

Returning HTTP status codes in a Spring Boot REST API

Spring Boot

public ResponseEntity<String> getData() {
    Optional<String> data = service.getDataOptional();
    return data.map(d -> ResponseEntity.ok(d))
               .orElseGet(() -> ResponseEntity.status(HttpStatus.NOT_FOUND).body("Not Found"));
}

Returns precise status codes like 404 for missing data, reducing client retries and improving perceived load speed.

📈 Performance GainReduces unnecessary network calls and speeds up client rendering by clear status signaling.

Returning HTTP status codes in a Spring Boot REST API

Spring Boot

public ResponseEntity<String> getData() {
    try {
        String data = service.getData();
        return new ResponseEntity<>(data, HttpStatus.OK);
    } catch (Exception e) {
        return new ResponseEntity<>("Error", HttpStatus.INTERNAL_SERVER_ERROR);
    }
}

Using generic exception handling returns 500 status for all errors, causing unnecessary retries or confusion on the client side.

📉 Performance CostBlocks client processing until server responds; may cause extra network round-trips if client retries.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Generic 500 on all errors	N/A (server-side)	N/A	N/A	[X] Bad
Specific status codes (404, 200)	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

The server sends an HTTP status code that informs the browser how to handle the response. Correct status codes help the browser decide whether to render content, show errors, or retry requests.

→Network Request

→Response Handling

→Rendering

⚠️ BottleneckNetwork Request and Response Handling

Core Web Vital Affected

LCP

This affects the server response time and perceived page load speed by the client, impacting how quickly the browser can proceed after receiving the status code.

Optimization Tips

1Always return the most accurate HTTP status code for the response.

2Avoid generic 500 errors for all failures; use 404, 400, or other codes as appropriate.

3Use status codes to help clients avoid unnecessary retries and speed up page load.

Performance Quiz - 3 Questions

Why is returning specific HTTP status codes better for performance than always returning 500 on errors?

A It makes the server response larger in size.

B It increases server CPU usage.

C It reduces unnecessary client retries and speeds up error handling.

D It delays the initial connection to the server.

DevTools: Network

How to check: Open DevTools, go to the Network tab, reload the page or API call, and inspect the status code column for each request.

What to look for: Look for correct HTTP status codes (200, 404, 500) matching the expected server response to confirm efficient status handling.