Compression middleware in Node.js - Performance & Optimization

Performance: Compression middleware

HIGH IMPACT

Compression middleware affects the time it takes for the browser to receive and render content by reducing the size of data sent over the network.

Serving HTTP responses with compression to improve load speed

Node.js

import express from 'express';
import compression from 'compression';

const app = express();

// Compress only text-based responses
app.use(compression({
  filter: (req, res) => {
    const contentType = res.getHeader('Content-Type') || '';
    return /text|json|javascript|css/.test(contentType);
  }
}));

app.get('/', (req, res) => {
  res.sendFile('large-image.png');
});

Skips compression for already compressed files, saving CPU and speeding up response delivery.

📈 Performance GainReduces CPU blocking, lowers TTFB, improves LCP by sending smaller payloads only when beneficial

Serving HTTP responses with compression to improve load speed

Node.js

import express from 'express';
import compression from 'compression';

const app = express();

// Compress all responses including already compressed files
app.use(compression({
  filter: () => true
}));

app.get('/', (req, res) => {
  res.sendFile('large-image.png');
});

Compressing already compressed files like images wastes CPU and delays response without reducing size.

📉 Performance CostBlocks response for extra CPU time, increasing TTFB and delaying LCP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Compress all responses including images	No impact	No impact	No impact	[X] Bad
Compress only text-based responses	No impact	No impact	No impact	[OK] Good

Rendering Pipeline

Compression middleware reduces the size of HTTP responses before they reach the browser, speeding up network transfer and enabling faster rendering.

→Network Transfer

→First Contentful Paint

→Largest Contentful Paint

⚠️ BottleneckCPU time spent compressing large or already compressed files

Core Web Vital Affected

LCP

Compression middleware affects the time it takes for the browser to receive and render content by reducing the size of data sent over the network.

Optimization Tips

1Compress only text-based responses to save CPU and improve speed.

2Avoid compressing already compressed files like images or videos.

3Use compression middleware to reduce network payload size and improve LCP.

Performance Quiz - 3 Questions

What is the main benefit of using compression middleware in Node.js?

A Reduces the size of HTTP responses to speed up page load

B Increases CPU usage to slow down the server

C Adds extra HTML elements to the page

D Prevents caching of static files

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check the 'Content-Encoding' header and size of responses.

What to look for: Look for 'gzip' or 'br' encoding on text files and verify images are not compressed again. Smaller transferred size indicates good compression.

Practice

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

easy

A. To parse JSON data from client requests

B. To add security headers to HTTP responses

C. To log all incoming requests to the server

D. To reduce the size of server responses and speed up loading times

Solution

1. Step 1: Understand what compression middleware does

   Compression middleware compresses the data sent from the server to the client to reduce its size.

2. Step 2: Identify the benefit of compression

   Smaller response sizes mean faster loading times for users because less data travels over the network.

3. Final Answer:

   To reduce the size of server responses and speed up loading times -> Option D

4. Quick Check:

   Compression = smaller responses = faster loading [OK]

Hint: Compression shrinks response size to speed up loading [OK]

Common Mistakes:

• Confusing compression with security or logging
• Thinking compression parses request data
• Assuming compression adds headers unrelated to size

2. Which of the following is the correct way to add compression middleware in an Express app?

easy

A. app.use('compression');

B. app.use(compression);

C. app.use(compression());

D. app.use(compress());

Solution

1. Step 1: Recall the syntax for middleware usage in Express

   Middleware functions are passed as functions, so you must call compression() to get the middleware function.

2. Step 2: Identify the correct syntax

   app.use(compression()); correctly calls the compression function and passes the middleware to Express.

3. Final Answer:

   app.use(compression()); -> Option C

4. Quick Check:

   Middleware needs function call syntax () [OK]

Hint: Middleware must be called as a function with () [OK]

Common Mistakes:

• Forgetting parentheses after compression
• Passing string instead of function
• Using wrong function name like compress

3. Given this Express code snippet, what will be the effect on the response?

import express from 'express';
import compression from 'compression';

const app = express();
app.use(compression());

app.get('/', (req, res) => {
  res.send('Hello World!');
});

app.listen(3000);

medium

A. The response will be compressed if the client supports it

B. The response will always be sent uncompressed

C. The server will throw an error because compression is not configured

D. The response will be compressed only for POST requests

Solution

1. Step 1: Understand compression middleware behavior

   Compression middleware compresses responses only if the client sends an Accept-Encoding header that supports compression (like gzip).

2. Step 2: Analyze the code snippet

   The middleware is applied globally with app.use(compression()), so all responses, including GET '/', will be compressed if the client supports it.

3. Final Answer:

   The response will be compressed if the client supports it -> Option A

4. Quick Check:

   Compression depends on client support [OK]

Hint: Compression works only if client accepts it [OK]

Common Mistakes:

• Assuming compression always compresses regardless of client
• Thinking compression only works on POST
• Believing compression requires extra config to avoid errors

4. What is wrong with this code snippet that tries to add compression middleware?

const express = require('express');
const compression = require('compression');

const app = express();
app.use(compression);

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

app.listen(3000);

medium

A. The route handler is missing a next() call

B. Compression middleware is not called as a function

C. Express app is not created correctly

D. Compression middleware must be added after routes

Solution

1. Step 1: Check how compression middleware is added

   The code uses app.use(compression); which passes the compression function itself, not the middleware returned by calling it.

2. Step 2: Identify correct usage

   Compression middleware must be called as compression() to return the middleware function, so it should be app.use(compression());.

3. Final Answer:

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

4. Quick Check:

   Middleware must be called with () [OK]

Hint: Always call middleware functions with () when adding [OK]

Common Mistakes:

• Passing middleware function without calling it
• Thinking middleware order doesn't matter here
• Confusing route handler requirements with middleware

5. You want to compress only responses larger than 1KB in your Express app. Which code snippet correctly applies this condition using compression middleware?

hard

A. app.use(compression({ threshold: 1024 }));

B. app.use(compression({ minSize: 1024 }));

C. app.use(compression({ sizeLimit: 1024 }));

D. app.use(compression({ compressAbove: 1024 }));

Solution

1. Step 1: Recall compression middleware options

   The official compression middleware option to set minimum response size for compression is threshold, which accepts bytes.

2. Step 2: Match the correct option name and value

   Setting threshold: 1024 means compress responses only if size is greater than 1024 bytes (1KB).

3. Final Answer:

   app.use(compression({ threshold: 1024 })); -> Option A

4. Quick Check:

   Use threshold option to set minimum size [OK]

Hint: Use threshold option to set minimum compression size [OK]

Common Mistakes:

• Using incorrect option names like minSize or sizeLimit
• Not specifying size in bytes
• Assuming compression applies to all sizes by default