Protecting routes with auth middleware in Express - Performance & Optimization

Performance: Protecting routes with auth middleware

MEDIUM IMPACT

This affects the server response time and user experience by adding authentication checks before route handlers run.

Checking user authentication before accessing protected routes

Express

function authMiddleware(req, res, next) {
  if (!req.user) {
    return res.redirect('/login');
  }
  next();
}

app.get('/dashboard', authMiddleware, (req, res) => {
  res.send('Dashboard');
});

Centralizes auth logic in middleware, reducing repeated checks and improving maintainability.

📈 Performance GainSingle auth check per request before route handler; easier to optimize and cache auth state.

Checking user authentication before accessing protected routes

Express

app.get('/dashboard', (req, res) => {
  if (!req.user) {
    res.redirect('/login');
    return;
  }
  // route logic
  res.send('Dashboard');
});

Authentication check is repeated in every route handler, causing code duplication and inconsistent checks.

📉 Performance CostBlocks route handling for each request; harder to optimize or cache auth logic.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Auth check inside each route	N/A (server-side)	N/A	N/A	[X] Bad
Auth middleware before routes	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Auth middleware runs before the route handler, adding a synchronous check that can delay response if user is not authenticated.

→Request Handling

→Response Generation

⚠️ BottleneckRequest Handling stage due to synchronous auth checks

Core Web Vital Affected

INP

This affects the server response time and user experience by adding authentication checks before route handlers run.

Optimization Tips

1Use auth middleware to centralize and optimize authentication checks.

2Keep auth middleware lightweight to minimize request handling delay.

3Cache user session or token validation results to speed up auth checks.

Performance Quiz - 3 Questions

What is the main performance benefit of using auth middleware instead of checking auth inside each route handler?

A Centralizes auth logic, reducing repeated checks and improving response consistency

B Removes the need for authentication entirely

C Makes the server send responses faster by skipping auth

D Allows the browser to cache the auth state

DevTools: Network

How to check: Open DevTools Network tab, filter requests to protected routes, and observe response times with and without auth middleware.

What to look for: Look for small added latency before response indicating auth check; consistent response times show efficient middleware.