WebSocket authentication in FastAPI - Performance & Optimization

Performance: WebSocket authentication

MEDIUM IMPACT

This affects the initial connection setup time and ongoing message responsiveness in WebSocket communication.

Authenticating users on WebSocket connections

FastAPI

async def websocket_endpoint(websocket: WebSocket, token: str):
    user = await authenticate_token(token)  # Authenticate once during handshake
    if not user:
        await websocket.close()
        return
    await websocket.accept()
    while True:
        data = await websocket.receive_text()
        await websocket.send_text(f"Hello {user.name}")

Authenticate once during connection setup, reducing repeated checks and improving message responsiveness.

📈 Performance GainSingle authentication cost upfront, resulting in faster message handling and lower INP

Authenticating users on WebSocket connections

FastAPI

async def websocket_endpoint(websocket: WebSocket):
    await websocket.accept()
    while True:
        data = await websocket.receive_text()
        user = await authenticate_token(data)  # Authenticate on every message
        if not user:
            await websocket.close()
            break
        await websocket.send_text(f"Hello {user.name}")

Authenticating on every message adds latency and CPU load, causing slower message handling and higher INP.

📉 Performance CostBlocks message processing for each message, increasing input delay and CPU usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Authenticate on every message	N/A (WebSocket, no DOM)	N/A	N/A	[X] Bad
Authenticate once during handshake	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

WebSocket authentication occurs during the handshake phase before the connection is established. Proper authentication avoids blocking message processing later.

→Connection Setup

→Message Processing

⚠️ BottleneckRepeated authentication during message processing causes input delay and CPU overhead

Core Web Vital Affected

INP

This affects the initial connection setup time and ongoing message responsiveness in WebSocket communication.

Optimization Tips

1Authenticate once during the WebSocket handshake, not on every message.

2Cache user info after authentication to speed up message handling.

3Use DevTools Network panel to monitor WebSocket handshake and message latency.

Performance Quiz - 3 Questions

What is the main performance benefit of authenticating once during the WebSocket handshake?

A Decreases CSS paint cost

B Reduces message processing delay by avoiding repeated authentication

C Improves DOM rendering speed

D Reduces bundle size

DevTools: Network

How to check: Open DevTools Network panel, filter by WS, observe WebSocket handshake timing and message latency.

What to look for: Long handshake time or high latency between messages indicates inefficient authentication.