Skip to main content
ModPageSpeed 2.0 and mod_pagespeed 1.1 — Coming Soon

Getting Started

Install mod_pagespeed 1.1 on nginx, Apache, IIS, or Envoy. Platform-specific setup instructions, verification steps, license activation, and next steps.

Choose your platform

mod_pagespeed 1.1 runs on nginx, Apache, IIS, and Envoy. Pick your web server below.

Install the dynamic module alongside your existing nginx (1.26.x stable or 1.27.x mainline):

# Copy the module to nginx modules directory
sudo cp ngx_pagespeed_module.so /usr/lib/nginx/modules/

# Add to nginx.conf (top-level, before http block)
load_module modules/ngx_pagespeed_module.so;

Then enable it in your server block:

server {
    pagespeed on;
    pagespeed FileCachePath /var/cache/pagespeed;

    # Your existing configuration...
}

Reload nginx:

sudo nginx -t && sudo systemctl reload nginx

Replace the open-source module with the 1.1 build:

# Replace the existing module
sudo cp mod_pagespeed.so /usr/lib/apache2/modules/

# Restart Apache
sudo systemctl restart apache2

Your existing pagespeed.conf continues to work — no configuration changes needed.

Requirements

  • Windows Server 2019 or later (IIS 10+)
  • 64-bit only
  • IIS worker process identity needs write permissions on the cache directory

Install the module

Download the IIS module installer from the downloads page and run it on your Windows Server. The installer registers the module in IIS as a native HTTP module automatically.

Configure the file cache path

After installation, verify the cache path in the server-level configuration at %ProgramData%\We-Amp\IISWebSpeed\pagespeed.config:

pagespeed FileCachePath %ProgramData%\We-Amp\IISWebSpeed\Cache

The cache directory must be writable by the IIS worker process identity (typically IIS_IUSRS or the app pool identity). The installer creates this directory with appropriate permissions.

To validate the cache path, make a request to any page on your server and check that files appear in the cache directory.

Enable optimization for a site

Place a pagespeed.config file in your website’s root directory:

pagespeed on
pagespeed FileCachePath %ProgramData%\We-Amp\IISWebSpeed\Cache

The FileCachePath must be included in per-site configs if not set in the server-level config. Site-level settings override server-level settings.

IIS Express

For local development with IIS Express, add the module to applicationhost.config in %userprofile%\Documents\IISExpress\config\:

  1. Copy the module DLL to a known location
  2. Add the module registration under <globalModules> and <modules>
  3. Restart IIS Express

Disable optimization

To disable optimization for a site, either delete or rename its pagespeed.config file, or add:

pagespeed off

Envoy

Add the mod_pagespeed HTTP filter to your Envoy configuration. Envoy integration is currently in beta — contact us for setup guidance.

Verify it works

Send a request and check for the response header:

curl -I http://localhost/

You should see:

X-Page-Speed: 1.1.0

On Apache the header is named X-Mod-Pagespeed instead of X-Page-Speed.

The first request to any URL will show X-Page-Speed: MISS (or X-Mod-Pagespeed: MISS on Apache) while resources are being optimized. Subsequent requests will show HIT.

License activation

mod_pagespeed 1.1 includes a 14-day free trial. No credit card required to start.

To activate a subscription after the trial, visit modpagespeed.com/pricing/ and choose a plan. You’ll receive setup instructions by email.

If you are migrating from IISpeed, your existing license transfers at no cost. Contact us to arrange the transfer.

Next steps