Third-party middleware installation in Express - Performance & Optimization

Performance: Third-party middleware installation

MEDIUM IMPACT

This affects the server response time and the overall latency before the client receives the response.

Adding middleware to handle requests in an Express app

Express

const express = require('express');
const app = express();
const heavyMiddleware = require('heavy-middleware');
app.get('/special', heavyMiddleware(), (req, res) => res.send('Special route'));
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

Apply heavy middleware only on routes that need it, reducing unnecessary processing on other requests.

📈 Performance GainReduces average request delay by 50-100ms, improving INP and server throughput.

Adding middleware to handle requests in an Express app

Express

const express = require('express');
const app = express();
const heavyMiddleware = require('heavy-middleware');
app.use(heavyMiddleware());
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

Using a heavy middleware globally for all routes causes unnecessary processing on every request, increasing latency.

📉 Performance CostAdds 50-100ms delay per request, increasing INP and slowing server response.

Performance Comparison

Pattern	Middleware Usage	Request Latency	Server Load	Verdict
Global heavy middleware	All routes	High (50-100ms added)	High	[X] Bad
Route-specific heavy middleware	Only needed routes	Low	Moderate	[OK] Good

Rendering Pipeline

Middleware runs on the server before sending the response. Heavy or unnecessary middleware increases server processing time, delaying response delivery and affecting user interaction speed.

→Server Processing

→Response Generation

⚠️ BottleneckServer Processing time due to middleware execution

Core Web Vital Affected

INP

This affects the server response time and the overall latency before the client receives the response.

Optimization Tips

1Avoid installing heavy middleware globally if not needed on all routes.

2Use lightweight middleware and apply it selectively to reduce server latency.

3Monitor server response times to detect middleware bottlenecks early.

Performance Quiz - 3 Questions

What is the main performance risk of installing heavy third-party middleware globally in Express?

A It causes layout shifts in the browser

B It reduces client-side rendering speed

C It increases server response time for all requests

D It decreases network bandwidth

DevTools: Network and Performance panels

How to check: Use Network panel to measure server response times; use Performance panel to record server-side processing delays if possible with remote profiling.

What to look for: Look for increased server response time and long blocking periods before response starts, indicating middleware overhead.

Practice

1. What is the main purpose of third-party middleware in an Express app?

easy

A. To add extra features like parsing or logging easily

B. To replace the Express framework completely

C. To write HTML pages automatically

D. To create a database connection

Solution

1. Step 1: Understand middleware role

   Middleware adds extra functions to Express apps, like parsing data or logging requests.

2. Step 2: Compare options

   Replacing Express or creating databases are not middleware tasks; middleware enhances features.

3. Final Answer:

   To add extra features like parsing or logging easily -> Option A

4. Quick Check:

   Middleware adds features = A [OK]

Hint: Middleware adds features, not replaces core framework [OK]

Common Mistakes:

• Thinking middleware replaces Express
• Confusing middleware with database tools
• Assuming middleware generates HTML pages

2. Which code snippet correctly installs and uses the cors middleware in an Express app?

easy

A. const cors = require('cors'); app.use(cors());

B. import cors from 'cors'; app.use(cors);

C. import cors from 'cors'; app.use(cors());

D. const cors = require('cors'); app.use(cors);

Solution

1. Step 1: Check import style

   Modern Express apps use ES modules, so import cors from 'cors'; is correct.

2. Step 2: Check middleware usage

   Middleware must be called as a function: app.use(cors()); not just cors.

3. Final Answer:

   import cors from 'cors'; app.use(cors()); -> Option C

4. Quick Check:

   Import + call middleware function = C [OK]

Hint: Import middleware and call it with () in app.use [OK]

Common Mistakes:

• Forgetting parentheses after middleware name
• Mixing require and import syntax
• Using app.use(cors) without calling it

3. What will be the output when this Express app code runs and receives a JSON POST request?

import express from 'express';
import bodyParser from 'body-parser';
const app = express();
app.use(bodyParser.json());
app.post('/data', (req, res) => {
  res.send(req.body.name);
});
app.listen(3000);

medium

A. The server responds with an empty string

B. The server responds with '[object Object]'

C. The server crashes with a syntax error

D. The server responds with the value of 'name' from the JSON body

Solution

1. Step 1: Understand bodyParser.json()

   This middleware parses JSON request bodies and sets req.body to the parsed object.

2. Step 2: Check response code

   The route sends back req.body.name, so the response is the 'name' value from JSON.

3. Final Answer:

   The server responds with the value of 'name' from the JSON body -> Option D

4. Quick Check:

   bodyParser parses JSON, response sends req.body.name = B [OK]

Hint: bodyParser.json() parses JSON, so req.body has data [OK]

Common Mistakes:

• Not using bodyParser.json(), so req.body is undefined
• Expecting raw JSON string instead of parsed object
• Sending req.body instead of req.body.name

4. Identify the error in this Express app code using helmet middleware:

import express from 'express';
import helmet from 'helmet';
const app = express();
app.use(helmet);
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

medium

A. helmet is imported incorrectly

B. helmet middleware is not called as a function

C. app.listen is missing a callback

D. app.get route is missing a response

Solution

1. Step 1: Check middleware usage

   Middleware must be called as a function: app.use(helmet()); not app.use(helmet);.

2. Step 2: Verify other code parts

   Import is correct, app.listen works without callback, and route sends response properly.

3. Final Answer:

   helmet middleware is not called as a function -> Option B

4. Quick Check:

   Middleware must be called with () = A [OK]

Hint: Always call middleware with () in app.use [OK]

Common Mistakes:

• Using app.use(helmet) instead of app.use(helmet())
• Thinking app.listen needs a callback
• Forgetting to send response in route

5. You want to add morgan logging middleware only for POST requests in your Express app. Which code correctly applies this?

hard

A. app.use((req, res, next) => { if(req.method === 'POST') morgan('dev')(req, res, next); else next(); });

B. app.post('*', morgan('dev'));

C. app.use(morgan('dev')); if(req.method === 'POST') next();

D. app.use('/post', morgan('dev'));

Solution

1. Step 1: Understand middleware conditional use

   To run middleware only on POST, wrap it in a function checking req.method.

2. Step 2: Analyze options

   app.use((req, res, next) => { if(req.method === 'POST') morgan('dev')(req, res, next); else next(); }); calls morgan only if method is POST, else calls next(). Others either apply to wrong paths or misuse middleware.

3. Final Answer:

   app.use((req, res, next) => { if(req.method === 'POST') morgan('dev')(req, res, next); else next(); }); -> Option A

4. Quick Check:

   Conditional middleware call for POST = D [OK]

Hint: Wrap middleware in function checking req.method for selective use [OK]

Common Mistakes:

• Using app.use with path that doesn't match POST method
• Calling middleware without next() in else branch
• Trying to use app.post with middleware incorrectly