Response time tracking middleware in Express

Introduction

This middleware helps you see how long your server takes to answer each request. It shows the time in milliseconds so you can know if your app is fast or slow.

You want to check if your website loads quickly for users.

You need to find slow parts in your server to improve them.

You want to log response times for monitoring or debugging.

You are testing new features and want to compare speed.

You want to add response time info to HTTP headers for clients.

Syntax

Express

function responseTimeMiddleware(req, res, next) {
  const start = Date.now();
  res.on('finish', () => {
    const duration = Date.now() - start;
    console.log(`${req.method} ${req.url} took ${duration}ms`);
  });
  next();
}

The middleware uses res.on('finish') to run code after the response is sent.

next() is called to pass control to the next middleware or route.

Examples

Adds the middleware to all routes in your Express app.

Express

app.use(responseTimeMiddleware);

You can add the response time to a custom HTTP header for clients to see.

Express

res.setHeader('X-Response-Time', `${duration}ms`);

Use high-resolution timer for more precise timing in nanoseconds converted to milliseconds.

Express

const start = process.hrtime.bigint();
// ... later
const duration = Number(process.hrtime.bigint() - start) / 1_000_000;

Sample Program

This Express app uses the response time middleware to log how long each request takes. The '/' route waits 100ms before responding to simulate work.

Express

import express from 'express';

const app = express();

function responseTimeMiddleware(req, res, next) {
  const start = Date.now();
  res.on('finish', () => {
    const duration = Date.now() - start;
    console.log(`${req.method} ${req.url} took ${duration}ms`);
  });
  next();
}

app.use(responseTimeMiddleware);

app.get('/', (req, res) => {
  setTimeout(() => {
    res.send('Hello, world!');
  }, 100); // simulate delay
});

app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

Important Notes

Response time includes the time your server spends processing plus sending the response.

Use res.on('finish') instead of res.on('close') to ensure the response was fully sent.

Adding the response time header helps frontend developers see performance without checking logs.

Summary

Response time middleware measures how long each request takes.

It uses res.on('finish') to run code after response ends.

You can log times and add them to HTTP headers for easy monitoring.

Practice

1. What is the main purpose of response time tracking middleware in Express?

easy

A. To measure how long each HTTP request takes to complete

B. To modify the request body before processing

C. To handle errors and send error responses

D. To serve static files like images and CSS

Solution

1. Step 1: Understand middleware role

   Response time tracking middleware measures the duration of requests.

2. Step 2: Identify main purpose

   It tracks how long the server takes to respond to each request.

3. Final Answer:

   To measure how long each HTTP request takes to complete -> Option A

4. Quick Check:

   Response time tracking = measuring request duration [OK]

Hint: Middleware timing tracks request duration, not request content [OK]

Common Mistakes:

• Confusing response time tracking with error handling
• Thinking it modifies request data
• Assuming it serves static files

2. Which of the following is the correct way to start measuring time in an Express middleware?

easy

A. const start = setTimeout();

B. const start = Date.now();

C. const start = process.hrtime();

D. const start = new Date().toString();

Solution

1. Step 1: Identify time measurement method

   Date.now() returns the current timestamp in milliseconds, suitable for timing.

2. Step 2: Check other options

   new Date().toString() returns a string, not a number; process.hrtime() returns a tuple, more complex; setTimeout() is for delays, not time capture.

3. Final Answer:

   const start = Date.now(); -> Option B

4. Quick Check:

   Use Date.now() for simple timestamps [OK]

Hint: Use Date.now() for simple time stamps in middleware [OK]

Common Mistakes:

• Using new Date().toString() which returns a string
• Confusing process.hrtime() with Date.now()
• Using setTimeout() incorrectly for timing

3. Given this middleware snippet, what will be logged?

app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    const duration = Date.now() - start;
    console.log(`Request took ${duration}ms`);
  });
  next();
});

medium

A. Logs the time before the request starts processing

B. Logs the time repeatedly during the request

C. Logs the time taken for each request after response finishes

D. Does not log anything because of missing next()

Solution

1. Step 1: Understand event listener on 'finish'

   The 'finish' event triggers after the response is sent, so timing is complete.

2. Step 2: Calculate duration and log

   Duration is current time minus start time, logged once per request.

3. Final Answer:

   Logs the time taken for each request after response finishes -> Option C

4. Quick Check:

   res.on('finish') logs after response ends [OK]

Hint: res.on('finish') runs after response ends for timing [OK]

Common Mistakes:

• Thinking it logs before request processing
• Assuming multiple logs during request
• Forgetting to call next() to continue middleware chain

4. Identify the error in this response time middleware:

app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    const duration = Date.now() - start;
    console.log(`Request took ${duration}ms`);
  });
});

medium

A. Logging inside middleware is not allowed

B. Using Date.now() instead of process.hrtime() causes error

C. res.on('finish') should be res.on('end')

D. Missing call to next(), so request hangs

Solution

1. Step 1: Check middleware flow

   Middleware must call next() to pass control; missing here causes request to hang.

2. Step 2: Validate event and logging

   res.on('finish') is correct event; Date.now() is valid; logging is allowed.

3. Final Answer:

   Missing call to next(), so request hangs -> Option D

4. Quick Check:

   Always call next() in middleware [OK]

Hint: Always call next() to continue middleware chain [OK]

Common Mistakes:

• Forgetting next() call
• Confusing 'finish' with 'end' event
• Thinking Date.now() causes errors

5. You want to log the response time in milliseconds to the console using the format Request took ${duration}ms. Which middleware code correctly does this?

hard

A. app.use((req, res, next) => {
const start = Date.now();
res.on('finish', () => {
const duration = Date.now() - start;
console.log(`Request took ${duration}ms`);
});
next();
});

B. app.use((req, res, next) => {
const start = Date.now();
const duration = Date.now() - start;
console.log(`Request took ${duration}ms`);
next();
});

C. app.use((req, res, next) => {
const start = Date.now();
console.log(`Request took ${Date.now() - start}ms`);
next();
});

D. app.use((req, res, next) => {
const start = Date.now();
res.on('close', () => {
const duration = Date.now() - start;
console.log(`Request took ${duration}ms`);
});
next();
});

Solution

1. Step 1: Understand logging timing

   To capture the full request processing time, record the start time, call next(), and log the duration in the 'finish' event handler which fires after the response is sent.

2. Step 2: Analyze incorrect approaches

   Logging right after starting the timer yields nearly 0ms because handlers haven't executed yet. The 'close' event relates to connection closure, not response completion, and may not fire reliably for timing.

3. Final Answer:

   Uses res.on('finish') to log accurate request duration -> Option A

4. Quick Check:

   res.on('finish') ensures complete request timing [OK]

Hint: Log duration in 'finish' event after response completes [OK]

Common Mistakes:

• Logging before calling next() (duration ~0ms)
• Using 'close' event instead of 'finish'
• Not waiting for response to finish