Getting Started
Install mod_pagespeed 1.15 on nginx, Apache, IIS, or Envoy. Platform-specific setup instructions, verification steps, license activation, and next steps.
On this page
Choose your platform
mod_pagespeed 1.15 runs on nginx, Apache, IIS, and Envoy. Pick your web server below.
Install from the apt repository
The signed repository at packages.modpagespeed.com ships the nginx dynamic module (nginx-module-pagespeed) prebuilt for Debian and Ubuntu, amd64 and arm64. Each module is pinned to that distribution’s exact stock nginx:
| Distribution | Stock nginx (pinned) |
|---|---|
| Debian 11 (bullseye) | 1.18.0 |
| Debian 12 (bookworm) | 1.22.1 |
| Debian 13 (trixie) | 1.26.3 |
| Ubuntu 22.04 (jammy) | 1.18.0 |
| Ubuntu 24.04 (noble) | 1.24.0 |
One command configures the apt source and imports the signing key:
curl -fsSL https://packages.modpagespeed.com/install.sh | sudo shThen install the package:
sudo apt-get install nginx-module-pagespeedInstalling the package drops the module into the standard nginx modules directory and adds a modules-enabled auto-include snippet — there is no load_module line to copy by hand. Enable optimization in your server block:
server {
pagespeed on;
pagespeed FileCachePath /var/cache/pagespeed;
# Your existing configuration...
}Reload nginx:
sudo nginx -t && sudo systemctl reload nginxUpdates flow through the normal package upgrade path (apt-get upgrade).
Running a different nginx version?
Each .so is pinned to its distribution’s exact stock nginx version — nginx’s --with-compat does not relax that check, so upgrading nginx past the stock version (or running nginx.org’s stable/mainline builds) requires a matching rebuild. The module source is not public; contact us and we’ll provide a build pinned to your nginx version.
Install from the apt/yum repository (recommended)
The signed repository at packages.modpagespeed.com ships the Apache module for Debian 11/12/13, Ubuntu 22.04/24.04, and AlmaLinux/RHEL 9. One command configures the apt or yum source and imports the signing key:
curl -fsSL https://packages.modpagespeed.com/install.sh | sudo shThen install the package:
sudo apt-get install mod-pagespeed # Debian/Ubuntu
sudo dnf install mod-pagespeed # AlmaLinux/RHELThe package drops the module into the standard Apache modules directory and enables it. Restart Apache:
sudo systemctl restart apache2 # Debian/Ubuntu
sudo systemctl restart httpd # RHEL familyUpdates flow through the normal package upgrade path:
sudo apt-get update && sudo apt-get upgrade # Debian/Ubuntu
sudo dnf upgrade # RHEL familyThe signed apt repo (Debian/Ubuntu) ships amd64 and arm64. The signed yum repo (AlmaLinux/RHEL 9) ships x86_64; for arm64 / aarch64 RPMs, use the direct-download fallback below.
Direct download (arm64, air-gapped, or no package manager)
For Debian and Ubuntu (apt/dpkg):
# amd64
curl -O https://modpagespeed.com/releases/v1.15.0/mod-pagespeed_1.15.0-r0_amd64.deb
sudo dpkg -i mod-pagespeed_1.15.0-r0_amd64.deb
# arm64
curl -O https://modpagespeed.com/releases/v1.15.0/mod-pagespeed_1.15.0-r0_arm64.deb
sudo dpkg -i mod-pagespeed_1.15.0-r0_arm64.debFor RHEL family (dnf/yum):
# x86_64
sudo dnf install -y https://modpagespeed.com/releases/v1.15.0/mod-pagespeed-1.15.0-0.x86_64.rpm
# aarch64
sudo dnf install -y https://modpagespeed.com/releases/v1.15.0/mod-pagespeed-1.15.0-0.aarch64.rpmYour existing pagespeed.conf continues to work — no configuration changes needed.
Module-only install (no package manager)
If you’d rather drop the .so in by hand:
# x86_64
curl -O https://modpagespeed.com/releases/v1.15.0/libmod_pagespeed-linux-x86_64.so
sudo cp libmod_pagespeed-linux-x86_64.so /usr/lib/apache2/modules/mod_pagespeed.so
sudo systemctl restart apache2Verify the download
Installs through packages.modpagespeed.com verify signatures automatically against the repository signing key (RSA 4096, fingerprint DF00E296BE9141CEA5411346F50D6054F10712A0).
For direct downloads, each artifact is GPG-signed and listed in SHA256SUMS:
curl -O https://modpagespeed.com/releases/v1.15.0/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
# Or with the GPG signing key:
curl -O https://modpagespeed.com/releases/v1.1.0/weamp-pkg-public.asc
gpg --import weamp-pkg-public.asc
gpg --verify mod-pagespeed_1.15.0-r0_amd64.deb.ascRequirements
- Windows Server 2019 or later (IIS 10+)
- 64-bit only
- Visual C++ Redistributable 2022
- IIS worker process identity needs write permissions on the cache directory
Migrating from IISpeed?
If IISpeed is installed on this host, uninstall it before running the mod_pagespeed 1.15 MSI. The two modules register the same handler in IIS and cannot coexist — leaving IISpeed in place will cause one or both to fail at site startup. Open Apps & features (or Programs and Features), remove “IISpeed”, iisreset, and then run the 1.15 installer.
Your existing IISpeed license transfers to mod_pagespeed 1.15 at no cost — contact us to arrange the transfer.
Install the module
Download the IIS MSI installer (signature) and run it on your Windows Server. The installer registers the module in IIS as a native HTTP module automatically and creates the default cache directory at %ProgramData%\We-Amp\IISWebSpeed\Cache.
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\CacheThe 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\CacheThe 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\:
- Copy the module DLL to a known location
- Add the module registration under
<globalModules>and<modules> - Restart IIS Express
Disable optimization
To disable optimization for a site, either delete or rename its pagespeed.config file, or add:
pagespeed offEnvoy
Add the mod_pagespeed HTTP filter to your Envoy configuration. Envoy integration is experimental — 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.15.0
On Apache the header is named X-Mod-Pagespeed instead of X-Page-Speed. On IIS the module emits X-Page-Speed, the same as nginx — check for it with PowerShell:
(Invoke-WebRequest http://localhost/ -Method Head).Headers["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
The module optimizes responses out of the box. Production use requires a commercial license — but the software never locks you out. While an installation is unlicensed (no valid token, or an expired token), the engine keeps optimizing and signals the unlicensed state by adding an X-PageSpeed-Warn: unlicensed response header, showing a notice in the admin console, and writing a WARNING line to the startup log.
To evaluate before you buy, simply install and run the module unlicensed: it fully optimizes your site and just adds the X-PageSpeed-Warn: unlicensed header. When you are ready for production, purchase a license at modpagespeed.com/pricing/ — license keys are issued by email and pasted into the admin console. To activate a license you already own, open the license console at /pagespeed_global_admin on your server (e.g. https://your-site/pagespeed_global_admin) and apply your key.
If you are migrating from IISpeed, your existing license transfers at no cost. Contact us to arrange the transfer.
Next steps
- What’s New in 1.15 — see everything that changed
- Upgrading from Open-Source — step-by-step migration guide
- Legacy docs (1.0) — original open-source documentation