HTTP status codes for APIs in Flask - Performance & Optimization

Performance: HTTP status codes for APIs

MEDIUM IMPACT

This concept affects how quickly clients understand API responses and handle errors, impacting perceived responsiveness and user experience.

Returning API responses with appropriate HTTP status codes

Flask

from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/data')
def data():
    # Returns 404 status code on error
    return jsonify({'error': 'Not found'}), 404

Clients can quickly detect errors from status code without parsing body, reducing unnecessary processing and retries.

📈 Performance GainImproves input responsiveness (INP) by reducing client-side delay and network overhead.

Returning API responses with appropriate HTTP status codes

Flask

from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/data')
def data():
    # Always returns 200 OK even on error
    return jsonify({'error': 'Not found', 'data': None}), 200

Always returning 200 OK forces clients to parse response body to detect errors, causing extra processing and possible retries.

📉 Performance CostIncreases client processing time and network retries, leading to slower interaction (higher INP).

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Always 200 OK with error in body	N/A	N/A	N/A	[X] Bad
Correct HTTP status codes (e.g., 404, 500)	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

HTTP status codes are part of the network response and do not directly affect browser rendering stages but influence client-side logic and perceived responsiveness.

→Network

→Client Processing

⚠️ BottleneckClient Processing when status codes are misused, causing extra parsing and retries.

Core Web Vital Affected

INP

This concept affects how quickly clients understand API responses and handle errors, impacting perceived responsiveness and user experience.

Optimization Tips

1Always use appropriate HTTP status codes for API responses.

2Avoid returning 200 OK for error conditions to prevent extra client processing.

3Correct status codes improve client responsiveness and reduce network overhead.

Performance Quiz - 3 Questions

Why is it better to return a 404 status code instead of a 200 with an error message in the body?

A It reduces the size of the response body.

B Clients can detect errors faster and avoid unnecessary processing.

C It improves the visual layout of the page.

D It increases the number of DOM nodes.

DevTools: Network

How to check: Open DevTools, go to Network tab, make an API request, and inspect the status code column for the response.

What to look for: Check that error responses return appropriate HTTP status codes (e.g., 404, 500) instead of always 200.