Our work

Case study: 100 on Google PageSpeed Insights, mobile and desktop

We took our own website, a WordPress and WooCommerce site with a page builder, a shop and a full set of plugins, and tuned it until Google PageSpeed Insights gave it 100 for Performance, Accessibility, Best Practices and SEO, on mobile and on desktop. It also scores 2 out of 2 for Agentic Browsing. This is exactly what we can do for your site.

The result

Both reports were run on the live home page at pagespeed.web.dev on 30 October 2026. When we started, the mobile Performance score was in the low sixties.

Scores move by a few points between tests, because Google measures on a simulated phone and a slow connection. We do not promise a specific number, but we do show you the before and after reports.

What it takes to get to 100

A perfect score is not one setting. It needs all of these in place at the same time:

• Access. A WordPress administrator login, plus access to the caching and CDN layer so changes show up for Google's test.
• A working cache. Full-page caching, long browser cache lifetimes for images, fonts and scripts, and a correct purge so visitors and Google never see an old copy.
• Right-sized, modern images. WebP, the correct size for each screen, explicit width and height, and the main image loaded first.
• Fast, stable fonts. Fonts loaded from your own server and preloaded, so text appears at once and nothing jumps.
• Nothing blocking the first paint. Scripts deferred and non-essential styles loaded after the page appears.
• Only the code each page needs. Unused plugin styles and scripts removed page by page.
• A lean page structure. A large page is split so the browser only builds what is on screen first.
• Accessibility done properly. Readable colour contrast, headings in order, labelled controls, unique IDs and sensible link names.
• Clean SEO and best-practice signals. Titles, descriptions, crawlable links and secure, modern code.
• A page that is easy for AI agents to read. Clear structure and named buttons and links, which is what the Agentic Browsing check looks at.
• Repeat testing. Several runs on mobile and desktop, because a single result can be a fluke.

What we changed on our own site

This was a lot more than installing a speed plugin. These are the main changes, in the order they mattered:

• Converted the home page images to WebP and replaced oversized originals, cutting image weight sharply.
• Swapped a heavy background photo for a lightweight gradient, so the biggest thing on screen paints almost instantly.
• Fixed the main image downloading twice at two different sizes.
• Made the main image smaller on phones, so the headline becomes the largest element Google measures, then checked it stays sharp.
• Deferred jQuery and every script that depends on it, removing about 600 milliseconds of render blocking.
• Loaded non-critical stylesheets after the page appears.
• Removed a 51 KB block of unused inline styling and stopped loading unused theme fonts.
• Moved the two display fonts onto our own server, preloaded them and set matching fallbacks, which brought layout shift to zero.
• Used content visibility so the browser skips the parts of a long page that are not on screen yet.
• Fixed colour contrast on text and buttons, including a bright red button that now follows the brand colours.
• Corrected the heading order, removed duplicate IDs and tidied labels and slider markup.
• Set long cache lifetimes and made sure the host's edge cache refreshed whenever we changed a page.

Does it matter for every page?

PageSpeed Insights tests one page at a time, but most fixes are shared across the whole site. We test one page from each type, such as the home page, a service page, a product, a blog post and the shop, and the shared improvements carry across all of them.

Want the same for your site?

Our PageSpeed Insights Optimisation service starts at £119 ex VAT, fixed price (with optional upkeep at £24.99 ex VAT per month), with before and after reports. We work on WordPress and WooCommerce sites.