PageSpeed

PageSpeed is the score Google’s own tools assign to how quickly a page loads and becomes usable, measured the same way for every site so results can be compared fairly. The number that matters most inside it is largest contentful paint, how long it takes for the biggest visible element on the page, usually a heading or a hero image, to actually appear. Google’s own threshold for a good experience there is 2.5 seconds. Cross that line and Google itself starts calling the experience poor.

What causes a page to miss that threshold is rarely one dramatic problem. It’s usually an accumulation: a page loading over a hundred separate files, plugins nobody remembers installing, images nobody resized before uploading, scripts running for tracking tools that were set up years ago and never revisited. Each one adds a small delay. Together they push a page well past 2.5 seconds without anything looking obviously broken to a person just glancing at the design.

I run this test before and after every rebuild, on the same day, under the same conditions, because the comparison is the whole point. A client can see, in Google’s own numbers, exactly what changed.

Why it matters to you

A visitor who has to wait for your page often doesn’t wait. They leave before the content even finishes appearing, and you never learn they were there. That’s revenue with no evidence it existed. On top of that, Google factors page speed directly into how a site ranks in an organic result, so a slow page loses twice: once on visitors who bail, and once on ranking that never had a chance to compete.

Speed also compounds with other Google-measured signals. The same PageSpeed test reports accessibility score and agentic browsing results side by side, and a site built with speed in mind tends to score well across all three at once, because the underlying discipline, a lean, well-structured build, helps everything measured together.

How I set it up

I build on Astro, which produces lean, mostly static pages by default rather than assembling a page from dozens of plugin scripts at load time. That alone removes most of the excess weight that drags a typical small-business site past the 2.5 second mark. Images get sized properly before they ship. Scripts that aren’t needed get removed rather than left running out of habit.

What it looks like in practice

The clearest proof is the before-and-after PageSpeed screenshot itself, same test, same day, mobile and desktop both. A client sees their old site’s slow, red-flagged score sitting next to the rebuilt site’s fast, clean one, straight from Google, with nothing to take my word for.