Health check endpoints in Express - Performance & Optimization

Performance: Health check endpoints

MEDIUM IMPACT

Health check endpoints affect server responsiveness and overall user experience by providing quick status feedback without heavy processing.

Implementing a health check endpoint to monitor server status

Express

app.get('/health', (req, res) => {
  res.json({ status: 'ok' });
});

Returns a simple static response immediately without extra processing, keeping the server responsive.

📈 Performance GainNon-blocking, responds instantly, improves INP

Implementing a health check endpoint to monitor server status

Express

app.get('/health', (req, res) => {
  // Simulate heavy DB query or complex logic
  const data = heavyDatabaseQuery();
  res.json({ status: 'ok', data });
});

This blocks the event loop with heavy synchronous operations, delaying responses and increasing server load.

📉 Performance CostBlocks event loop causing slow response times and higher INP

Performance Comparison

Pattern	Server Load	Response Time	Event Loop Blocking	Verdict
Heavy synchronous logic in health check	High	Slow	Blocks event loop	[X] Bad
Simple static response	Minimal	Fast	Non-blocking	[OK] Good

Rendering Pipeline

Health check endpoints bypass browser rendering but impact server response time and interaction responsiveness.

→Server Processing

→Network Transfer

⚠️ BottleneckServer Processing when heavy logic is included

Core Web Vital Affected

INP

Health check endpoints affect server responsiveness and overall user experience by providing quick status feedback without heavy processing.

Optimization Tips

1Keep health check endpoints minimal and synchronous-free.

2Avoid heavy database or file system operations in health checks.

3Respond immediately with simple status data to maintain server responsiveness.

Performance Quiz - 3 Questions

What is the main performance risk of a health check endpoint that runs heavy database queries synchronously?

A It blocks the event loop causing slow server responses

B It increases the page load time for users

C It causes layout shifts in the browser

D It reduces the bundle size

DevTools: Network

How to check: Open DevTools, go to Network tab, request the /health endpoint, and observe the response time.

What to look for: Look for very low response time (under 10ms) indicating a fast, lightweight health check.