Skip to main content
ModPageSpeed 2.0: AVIF, WebP, and critical CSS — up to 69% less page weight on the live demo

mod_pagespeed 1.15 · cPanel / EA4

mod_pagespeed for cPanel / EasyApache 4

Actively maintained since 2024. Signed RPMs from We-Amp, served out of packages.modpagespeed.com. Drops into EasyApache 4 as ea-apache24-mod_pagespeed — same package name Google's archived apache/incubator-pagespeed-cpanel repo used before it was archived in 2023. We picked up the upstream and kept shipping; the SRPM in this repo is the canonical EA4 build today.

Install

EasyApache 4 ships only on RHEL-family hosts. Write the yum repo file, then dnf install the module:

1. Write the yum repo file

On EL8 (AlmaLinux 8, Rocky 8, CloudLinux 8) and EL9 (AlmaLinux 9, Rocky 9, RHEL 9, CloudLinux 9) hosts — $releasever selects the right tree: 

sudo tee /etc/yum.repos.d/modpagespeed-ea4.repo >/dev/null <<'EOF'
[ea4]
name=mod_pagespeed for EasyApache 4
baseurl=https://packages.modpagespeed.com/yum/ea4/el$releasever/x86_64/
enabled=0
gpgcheck=1
gpgkey=https://packages.modpagespeed.com/pubkey.gpg
EOF

2. Install the module 

sudo dnf install --enablerepo=ea4 ea-apache24-mod_pagespeed

enabled=0 + --enablerepo=ea4 keeps the EA4 RPM tree out of routine dnf update runs unless you ask for it. The package is signed with key rsa4096/F50D6054F10712A0 — same key as the rest of packages.modpagespeed.com.

Today the operator authors modpagespeed-ea4.repo by hand; the existing install.sh targets the stock apt + yum trees only.

After install — WHM Customize UI

The RPM drops a module file but does not flip it on. Apache only loads mod_pagespeed after the operator ticks the box in WHM and rebuilds.

  1. WHM → Software → EasyApache 4 → Customize on the current profile.
  2. Open the Apache Modules step. mod_pagespeed appears alongside the other EA4 modules.
  3. Tick the checkbox. Review, then Provision. EA4 rebuilds Apache.
  4. When the provision finishes, the module is loaded and the filter runs on every vhost served by ea-apache24-httpd.

Prefer the command line? On a fresh provision the module is also wired into /etc/apache2/conf.d/modpagespeed.conf. Edit that file (or a per-vhost include) the same way you would on any RHEL Apache host — see the getting-started guide for the directive reference.

Activate a license

You can install and run mod_pagespeed unlicensed — it fully optimizes out of the box. The license activation flow runs from the global admin console on the server. Same path on every server mod_pagespeed 1.15 supports — Apache, nginx, IIS, Envoy: 

https://your-host.example.com/pagespeed_global_admin
  1. Open /pagespeed_global_admin on any vhost. The admin route is global to the server, not scoped to one vhost; /pagespeed_admin/ is the per-vhost statistics endpoint and does not run the activation flow.
  2. Click Buy a license. The console hands off to FastSpring checkout, billed immediately on purchase. The license token mints on return.
  3. The same screen accepts an existing license key if you already own one.

Without a license the worker keeps optimizing and adds an X-PageSpeed-Warn: unlicensed header to responses (plus an admin-console notice and a startup-log warning). Production use requires a commercial license — but the software never locks you out. The console stays reachable so you can enter or renew a license at any time.

Licensing is per site (registrable domain): one license covers every Apache instance serving that site. Hosts running many sites can use the Hoster tier instead — about $35/host/month, covering all sites on the host.

Operational warning

Remove before cpanel/elevate. Reinstall after.

Any third-party EA4 module — ea-apache24-mod_pagespeed included — blocks cpanel/elevate on an OS-major upgrade (EL8 → EL9, EL9 → EL10). This is the same precedent mod_passenger sets. cPanel's preflight stops on the package; the upgrade does not start. We build for both EL8 and EL9, so an EL8 → EL9 upgrade has a target-OS package to reinstall afterwards.

Three-step runbook on the OS upgrade window:

  1. sudo dnf remove ea-apache24-mod_pagespeed — the module unwires and Apache rebuilds without it. The license token and any /etc/apache2/conf.d/modpagespeed.conf stay on disk.
  2. Run /scripts/elevate-cpanel through the OS upgrade. EA4 itself migrates to the new EL release.
  3. Re-enable the yum repo for the new EL release (baseurl=…/yum/ea4/el10/x86_64/, once EL10 is available) and reinstall the module: sudo dnf install --enablerepo=ea4 ea-apache24-mod_pagespeed. The existing config and token are picked up unchanged.

The post-install script also writes a one-line reminder to /etc/motd so it surfaces at the next SSH session before the upgrade window.

Pricing

Same as every other mod_pagespeed 1.15 install path — licensed per site. Business is $99/site/month, or $948/site/year billed annually, with unlimited servers per site. One license covers every Apache instance serving the site. No per-request fees. No EA4-specific SKU.

Install and run unlicensed to evaluate — the module fully optimizes and just adds an X-PageSpeed-Warn: unlicensed header. When you're ready for production, buy a license from /pagespeed_global_admin via FastSpring, billed immediately on purchase. Production use requires a commercial license — but the software never locks you out.

Running many sites on one host? The Hoster tier covers all sites on the host for about $35/host/month — set up through the contact form. License terms: we-amp.com/licensing.

See full pricing

Not yet supported

Current limits of the cPanel/EA4 channel:

  • • EL10. Waiting on EA4 itself to ship EL10. We'll add the el10 tree to the repo once ea-apache24-httpd publishes there.
  • • arm64. EA4 RPMs ship x86_64 only at launch. arm64 isn't packaged yet; contact us if it blocks you.
  • • Ubuntu EA4. cPanel's Ubuntu EA4 support is partial / preview. We ship RHEL-family only — EL8 and EL9 (AlmaLinux, Rocky, RHEL, CloudLinux).
  • • WHM plugin UI. Config still lives in modpagespeed.conf and per-vhost includes. There's no WHM plugin for point-and-click config yet.

The module is built against EA4's Apache ABI (Module Magic Number 20120211), which cPanel has held stable across the entire Apache 2.4 series. Routine ea-apache24 updates keep the same MMN, so a yum update does not disturb the installed module. If a future Apache release ever changes the ABI, the package's ea-apache24-mmn requirement makes yum update hold the Apache upgrade with a clear dependency message instead of loading an incompatible module, so your site keeps serving. We track every ea-apache24 release and publish a matching signed rebuild when an ABI change requires one.

Maintained upstream. Signed RPMs. cPanel-native install.

Production use requires a commercial license — but the software never locks you out. Licensed per site; hosting providers can cover every site on a host with the Hoster tier.

Install & run Buy a license

cPanel, WHM, and EasyApache are trademarks of cPanel, L.L.C. We-Amp B.V. is not affiliated with or endorsed by cPanel, L.L.C.