Your agent says the site is faster, because the score went up. On the WordPress site this pack was built from, the score went up while the phone menu took 3.9 seconds to open after the first tap, and a muted video preview still streamed 7.7 MB as the page loaded. The Site Speed Pack makes your agent measure first, change one kind of thing at a time, and prove after each change that the phone menu opens on the first tap, video waits for play, signed-in pages stay out of the edge cache and the layout doesn’t move.
Inside, two skills. Measure, change one thing, prove it: Lighthouse 13, the version PageSpeed Insights runs, and a byte census of what a phone downloads, all written down before anything changes, then one kind of change at a time, with a note on how to undo each one. WordPress, setting by setting: every cache layer and speed tool listed and backed up, one tool per job, the delay exclusions WP Rocket and Perfmatters publish, checkout, cart and account pages left alone, and logged-in users checked for each tool. Measured on WP Rocket, Perfmatters and EWWW Image Optimizer with Easy IO; LiteSpeed Cache, FlyingPress, Autoptimize, WP-Optimize and others from their docs. On a WordPress course and store site, mobile Lighthouse on seven pages went from 67–90 to 94–100.
What you get: the download, numbered updates with a list of what changed, and a license for one company on as many machines and projects as you like. Every future version of the Site Speed Pack is included at no charge, so you never pay for a new version. Fourteen-day refund, no questions. No tracking, no license check, nothing phoning home: the scripts read the pages you name, the asset check sends requests only to the host you name, the exclusions lookup reads WP Rocket’s list on GitHub and Perfmatters’ docs page, and npx fetches Lighthouse 13 from the npm registry unless you point LH_BIN at your own copy. The selftests never leave the machine.
