Gzip compression in Nginx - Commands & Configuration

Introduction

Websites often send large files that take time to load. Gzip compression makes these files smaller before sending, so pages load faster and use less internet data.

When your website has large HTML, CSS, or JavaScript files that slow down loading.

When you want to improve user experience by speeding up page load times.

When you want to reduce bandwidth costs by sending smaller files.

When you want to optimize your site for mobile users with slower connections.

When you want to improve your website's SEO by having faster loading pages.

Config File - nginx.conf

nginx.conf

http {
    gzip on;
    gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
    gzip_min_length 256;
    gzip_comp_level 5;
    gzip_vary on;
}

This configuration enables gzip compression in nginx inside the http block.

• gzip on; turns gzip compression on.
• gzip_types lists the file types to compress.
• gzip_min_length sets the minimum file size to compress (256 bytes here).
• gzip_comp_level sets compression level (1-9, 5 is a good balance).
• gzip_vary on; adds a header so caches know the content is compressed.

Commands

Check the nginx configuration file for syntax errors before applying changes.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

Reload nginx to apply the new gzip compression settings without stopping the server.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

Send a request to the server asking for gzip compressed content and check the response headers.

Terminal

curl -H "Accept-Encoding: gzip" -I http://localhost

Expected Output

HTTP/1.1 200 OK

Server: nginx

Content-Encoding: gzip

Content-Type: text/html

Key Concept

If you remember nothing else from this pattern, remember: enabling gzip compression in nginx reduces file sizes sent to users, speeding up website loading.

Common Mistakes

Not enabling gzip with 'gzip on;' in the config.

Without this, gzip compression will not work even if other settings are present.

Always include 'gzip on;' inside the http block to activate compression.

Forgetting to reload nginx after changing the config.

Changes won't take effect until nginx reloads the configuration.

Run 'sudo systemctl reload nginx' after editing the config.

Not specifying the correct file types in 'gzip_types'.

Only files matching these types will be compressed; others will not.

Include all relevant MIME types like text/css, application/javascript, and application/json.

Summary

Edit nginx.conf to enable gzip compression and specify file types to compress.

Test the configuration syntax with 'nginx -t' before applying changes.

Reload nginx to apply the new settings without downtime.

Verify gzip is working by checking response headers with curl.

Practice

1. What is the main purpose of enabling gzip compression in nginx?

easy

A. To block certain file types from being served

B. To increase the server's CPU usage for better performance

C. To encrypt data between server and client

D. To reduce the size of files sent to the browser, speeding up page load

Solution

1. Step 1: Understand gzip compression purpose

   Gzip compresses files to reduce their size before sending to the browser.

2. Step 2: Connect compression to page load speed

   Smaller files load faster, improving website speed and user experience.

3. Final Answer:

   To reduce the size of files sent to the browser, speeding up page load -> Option D

4. Quick Check:

   gzip compression = smaller files = faster load [OK]

Hint: Remember gzip shrinks files to speed up loading [OK]

Common Mistakes:

• Thinking gzip increases CPU for performance
• Confusing gzip with encryption
• Believing gzip blocks files

2. Which of the following is the correct way to enable gzip compression in nginx configuration?

easy

A. gzip on;

B. gzip enable;

C. enable gzip;

D. gzip true;

Solution

1. Step 1: Recall nginx gzip syntax

   The correct directive to enable gzip is gzip on;.

2. Step 2: Check other options for syntax errors

   Options A, C, and D use invalid keywords or syntax not recognized by nginx.

3. Final Answer:

   gzip on; -> Option A

4. Quick Check:

   Enable gzip with 'gzip on;' [OK]

Hint: Use exact directive 'gzip on;' to enable gzip [OK]

Common Mistakes:

• Using 'gzip enable;' instead of 'gzip on;'
• Writing 'enable gzip;' which is invalid
• Using 'gzip true;' which is not recognized

3. Given this nginx snippet:

gzip on;
gzip_types text/plain application/json;

Which file types will be compressed when served?

medium

A. All file types are compressed

B. Only text/plain and application/json files

C. No files are compressed because gzip_types is incomplete

D. Only binary files are compressed

Solution

1. Step 1: Analyze gzip_types directive

   The directive specifies only text/plain and application/json MIME types for compression.

2. Step 2: Understand gzip on directive effect

   With gzip on;, only the listed types in gzip_types are compressed.

3. Final Answer:

   Only text/plain and application/json files -> Option B

4. Quick Check:

   gzip_types limits compression to listed types [OK]

Hint: gzip_types controls which file types get compressed [OK]

Common Mistakes:

• Assuming all files compress by default
• Thinking gzip_types must list all types including binaries
• Believing gzip_types disables compression

4. You added gzip on; and gzip_types text/html; to nginx.conf but compression is not working. What is the likely mistake?

medium

A. Enabling gzip disables compression by default

B. Using gzip_types with only one type

C. Forgetting to reload nginx after config change

D. Missing gzip_disable directive

Solution

1. Step 1: Check nginx reload requirement

   After config changes, nginx must be reloaded to apply new settings.

2. Step 2: Evaluate other options

   Using one type in gzip_types is valid; gzip on enables compression; gzip_disable disables it for some clients but is optional.

3. Final Answer:

   Forgetting to reload nginx after config change -> Option C

4. Quick Check:

   Reload nginx to apply gzip changes [OK]

Hint: Always reload nginx after config edits [OK]

Common Mistakes:

• Not reloading nginx after config update
• Thinking gzip_types must list many types
• Confusing gzip_disable as required

5. You want to compress HTML, CSS, and JavaScript files in nginx. Which configuration snippet correctly enables gzip for these types?

hard

A. gzip on;\ngzip_types text/html text/css application/javascript;

B. gzip on;\ngzip_types html css js;

C. gzip enable;\ngzip_types text/html text/css application/javascript;

D. gzip on;\ngzip_types text/html text/css js;

Solution

1. Step 1: Verify gzip enabling syntax

   The correct directive to enable gzip is gzip on;, not gzip enable;.

2. Step 2: Check MIME types in gzip_types

   File types must be specified by their MIME types: text/html, text/css, and application/javascript. Using extensions like 'html', 'css', or 'js' is invalid.

3. Final Answer:

   gzip on;\ngzip_types text/html text/css application/javascript; -> Option A

4. Quick Check:

   Use 'gzip on;' and correct MIME types [OK]

Hint: Use MIME types, not file extensions, in gzip_types [OK]

Common Mistakes:

• Using 'gzip enable;' instead of 'gzip on;'
• Listing file extensions instead of MIME types
• Omitting JavaScript MIME type