req.ip and req.hostname in Express - Performance & Optimization

Performance: req.ip and req.hostname

LOW IMPACT

Accessing req.ip and req.hostname affects server-side request handling speed and can impact response time if used inefficiently.

Extract client IP and hostname efficiently in Express middleware

Express

app.use((req, res, next) => {
  req.clientIp = req.ip;
  req.clientHostname = req.hostname;
  // Avoid DNS lookup or perform async caching if needed
  next();
});

Avoids blocking operations; uses Express built-in properties directly for fast access.

📈 Performance GainNon-blocking, immediate access with zero added latency

Extract client IP and hostname efficiently in Express middleware

Express

app.use((req, res, next) => {
  const ip = req.ip;
  const hostname = req.hostname;
  // Synchronous DNS lookup for hostname
  const dns = require('dns');
  let address;
  try {
    address = dns.lookupSync(hostname);
  } catch (err) {
    return next(err);
  }
  req.resolvedAddress = address;
  next();
});

Synchronous or blocking DNS lookups on req.hostname delay response and block event loop.

📉 Performance CostBlocks event loop during DNS lookup, increasing response time by 50-200ms depending on network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Access req.ip and req.hostname directly	N/A (server-side)	N/A	N/A	[OK] Good
Perform synchronous DNS lookup on req.hostname	N/A	N/A	N/A	[X] Bad

Rendering Pipeline

On the server, accessing req.ip and req.hostname happens during request processing before response is sent. It does not affect browser rendering but impacts server response time.

→Request Handling

→Response Preparation

⚠️ BottleneckBlocking synchronous operations based on req.hostname (e.g., DNS lookups)

Optimization Tips

1Access req.ip and req.hostname directly without blocking operations.

2Avoid synchronous DNS lookups during request processing.

3Cache any hostname resolutions asynchronously to prevent delays.

Performance Quiz - 3 Questions

What is the main performance risk when using req.hostname in Express middleware?

A Increasing DOM nodes on the client

B Performing synchronous DNS lookups blocking the event loop

C Triggering browser reflows

D Adding large CSS files

DevTools: Network

How to check: Open DevTools Network panel, inspect server response times for requests, and look for increased latency caused by middleware.

What to look for: Long server response times or waterfall delays indicating blocking operations during request processing