Third-party middleware usage in Node.js - Performance & Optimization

Performance: Third-party middleware usage

MEDIUM IMPACT

This affects server response time and overall page load speed by adding processing steps before sending responses.

Adding middleware to handle requests in a Node.js server

Node.js

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

Using lightweight or async middleware reduces blocking and speeds up request handling.

📈 Performance GainReduces blocking time to under 10ms per request, improving server response and LCP.

Adding middleware to handle requests in a Node.js server

Node.js

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

Using a heavy third-party middleware that performs expensive synchronous operations blocks the event loop and delays responses.

📉 Performance CostBlocks event loop for 50-100ms per request, increasing server response time and LCP.

Performance Comparison

Pattern	Server Blocking	Response Delay	Impact on LCP	Verdict
Heavy synchronous middleware	High (blocks event loop)	50-100ms delay	Significant delay	[X] Bad
Lightweight async middleware	Low (non-blocking)	Under 10ms delay	Minimal delay	[OK] Good

Rendering Pipeline

Third-party middleware runs on the server before the response is sent. Heavy or synchronous middleware delays the server response, which delays the browser's ability to start rendering the page.

→Server Processing

→Network Transfer

→Browser Rendering Start

⚠️ BottleneckServer Processing stage due to blocking middleware operations

Core Web Vital Affected

LCP

This affects server response time and overall page load speed by adding processing steps before sending responses.

Optimization Tips

1Avoid heavy synchronous middleware that blocks the Node.js event loop.

2Prefer asynchronous and lightweight middleware to keep server response fast.

3Monitor server response time (TTFB) to detect middleware performance issues.

Performance Quiz - 3 Questions

How does heavy synchronous middleware affect Node.js server performance?

A It blocks the event loop, delaying all requests

B It speeds up response by caching data

C It reduces network latency

D It improves browser rendering speed

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the Time column for server response time (TTFB).

What to look for: Look for high Time to First Byte (TTFB) values indicating slow server response caused by middleware.

Practice

1. What is the main purpose of using third-party middleware in a Node.js Express app?

easy

A. To replace the Express framework completely

B. To add extra features without writing them from scratch

C. To write all server code manually

D. To make the app run without Node.js

Solution

1. Step 1: Understand middleware role

   Middleware adds features like logging or parsing to an app without extra coding.

2. Step 2: Compare options

   Only To add extra features without writing them from scratch correctly describes middleware's purpose; others are incorrect or unrelated.

3. Final Answer:

   To add extra features without writing them from scratch -> Option B

4. Quick Check:

   Middleware adds features [OK]

Hint: Middleware adds features without extra coding [OK]

Common Mistakes:

• Thinking middleware replaces Express
• Believing middleware runs without Node.js
• Confusing middleware with full app code

2. Which of the following is the correct way to add a third-party middleware called helmet to an Express app?

easy

A. use.app(helmet);

B. app.helmet();

C. helmet(app);

D. app.use(helmet());

Solution

1. Step 1: Recall Express middleware syntax

   Middleware is added using app.use() with the middleware function called.

2. Step 2: Check options

   Only app.use(helmet()); uses app.use(helmet()); correctly; others have wrong syntax.

3. Final Answer:

   app.use(helmet()); -> Option D

4. Quick Check:

   Middleware added with app.use() [OK]

Hint: Use app.use() with middleware function call [OK]

Common Mistakes:

• Forgetting parentheses after middleware name
• Using incorrect method names like app.helmet()
• Passing middleware without calling it

3. Given this code snippet, what will be the output when a GET request is made to '/'?

const express = require('express');
const morgan = require('morgan');
const app = express();
app.use(morgan('tiny'));
app.get('/', (req, res) => {
  res.send('Hello World');
});
app.listen(3000);

medium

A. Throws an error because morgan is not used correctly

B. Responds with 'Hello World' but no logs appear

C. Logs request details in console and responds with 'Hello World'

D. Server crashes on start

Solution

1. Step 1: Understand morgan middleware

   Morgan logs HTTP request info to the console when used with app.use().

2. Step 2: Analyze code behavior

   GET '/' triggers morgan logging and sends 'Hello World' response.

3. Final Answer:

   Logs request details in console and responds with 'Hello World' -> Option C

4. Quick Check:

   morgan logs + response sent [OK]

Hint: Morgan logs requests when used with app.use() [OK]

Common Mistakes:

• Assuming morgan changes response content
• Thinking morgan causes errors if used like this
• Ignoring middleware effect on logging

4. Identify the error in this code that tries to use the cors middleware:

const express = require('express');
const cors = require('cors');
const app = express();
app.use(cors);
app.get('/', (req, res) => res.send('OK'));
app.listen(3000);

medium

A. Missing parentheses when calling cors middleware

B. cors middleware is not installed

C. app.get() is missing a callback function

D. app.listen() is called without a port

Solution

1. Step 1: Check middleware usage

   Middleware must be called as a function: cors(), not just cors.

2. Step 2: Verify code

   Code uses app.use(cors); missing parentheses, causing error.

3. Final Answer:

   Missing parentheses when calling cors middleware -> Option A

4. Quick Check:

   Middleware must be called with () [OK]

Hint: Always call middleware as a function with () [OK]

Common Mistakes:

• Passing middleware reference without ()
• Assuming app.get() lacks callback
• Forgetting to specify port in listen

5. You want to add both helmet for security and express.json() for parsing JSON bodies in your Express app. Which code correctly adds both middlewares in the right order?

hard

A. app.use(helmet()); app.use(express.json());

B. app.use(express.json); app.use(helmet);

C. app.use(helmet); app.use(express.json);

D. app.use(express.json()); app.use(helmet());

Solution

1. Step 1: Understand middleware order importance

   Security middleware like helmet should run before body parsing for best protection.

2. Step 2: Check middleware calls

   Both must be called as functions with parentheses; options B and C miss these, A has them but wrong order.

3. Step 3: Confirm correct order and syntax

   app.use(helmet()); app.use(express.json()); calls helmet first, then express.json(), both correctly called.

4. Final Answer:

   app.use(helmet()); app.use(express.json()); -> Option A

5. Quick Check:

   Helmet before json, both called [OK]

Hint: Call middleware with () and order security before parsing [OK]

Common Mistakes:

• Not calling middleware as functions
• Placing parsing before security middleware
• Mixing up middleware order