Table of Contents
- The precondition: an architecture where 100 is even possible
- The method: no secrets, just discipline
- The bonus: a site ready for the age of AI agents
- What follows from all this
Summary
The site achieves perfect 100/100 PageSpeed scores (mobile and desktop) plus a flat-out pass on Lighthouse's Agentic Browsing checks by combining a static, CDN-served headless frontend with a familiar legacy CMS backend, avoiding any need for a full backend migration. The gains come not fromspecial tricks but from methodically implementing every optimization Google's PageSpeed report already recommends, while also structuring content to be machine-readable for AI agents and search assistants.
When did you last see a perfect score in Google PageSpeed? Not 90-something, not ""the green zone"" — a flat 100 out of 100. We honestly tried to recall one, and couldn't name a single site from the past two or three years. Until we opened the report for our own.
Here is what our measurements show today:
- Google PageSpeed: 100 on mobile, 100 on desktop
- Ahrefs Site Audit: Health Score 100% (it was 99 until recently — we closed the gap)
- Lighthouse Agentic Browsing: all checks passed, 3 out of 3
PageSpeed Desktop
PageSpeed Mobile
Let's be honest right away: a perfect score was never the goal. It arrived as a side effect of two things — the right architecture chosen from the start, and boring, methodical checklist work. Let's take both in order.
The precondition: an architecture where 100 is even possible
Nothing is faster than static. That's the core thesis everything else follows from.
Our site is built on a headless architecture: the backend and the frontend are fully separated. The frontend is pure static — at build time we generate a ready-made ""snapshot"" of the site and serve it through a CDN. No server-side rendering, no database queries on every visit, no lazy calls slowing down the render. The visitor gets prebuilt files from the nearest CDN edge — and that's it.
Which CDN doesn't really matter: CloudFront, Cloudflare, DigitalOcean — any cloud delivery network will produce comparable results. It's the approach that matters, not the vendor.
Now the interesting part: our backend is far from new. It's a classic CMS that has been around for many years. And it doesn't slow the frontend down one bit — because visitors never touch the backend at all. The backend remains a working tool for editors; the frontend lives its own, very fast life.
Why this matters to you: if you run an older site on WordPress, Drupal, or another familiar CMS, you don't need to migrate anything to get this kind of speed. Your content team keeps working in the admin panel they know; nothing changes in their workflow. This is exactly what a headless migration without rewriting the backend looks like in practice — you're not throwing away your CMS, you're adding a static layer on top of it. If you're evaluating options, this is also what a proper website performance audit should surface: whether your current stack even needs replacing, or just a faster delivery layer.
The method: no secrets, just discipline
The second ingredient will disappoint anyone hoping for hacks. Every recommendation you need for a perfect score, Google hands out for free — right in the PageSpeed report, item by item, with documentation and examples.
The difference between ""everyone gets 70–90"" and ""we got 100"" is not secret knowledge. It's that we took that list and closed every item, methodically, step by step. Not just the easy ones — all of them. It wasn't quick. But that's the whole method: don't chase the score, just keep taking the necessary steps — the score follows.
This is, in effect, Core Web Vitals optimization done exhaustively rather than partially — which is usually the actual gap between a site stuck in the 80s and one that hits 100.
One honest caveat: PageSpeed numbers fluctuate a little from run to run — that's normal; that's how the measurement works. So we're not claiming ""we're always at exactly 100."" We're saying the site consistently sits at the very top of the range, and a perfect score on both device types is a regular, reproducible result. You're welcome to check for yourself.
The bonus: a site ready for the age of AI agents
Lighthouse recently introduced an experimental category called Agentic Browsing. It evaluates how usable a site is not just for people but for AI agents: whether they can correctly read the page structure, find a machine-readable description of the site, and interact with the interface reliably.
We passed every check — 3 out of 3. Among other things, we reworked the content served to agents into a machine-readable website structure. Search and AI assistants already drive a noticeable share of traffic, and that share will only grow. A site that agents can ""understand"" makes it into their answers and recommendations more often — this is the practical side of AI search optimization (sometimes called generative engine optimization): making sure your site is legible not just to Googlebot, but to the models people now ask instead of Google.
What follows from all this
Site speed is not about vanity metrics. It's about conversion (every second of load time costs you orders), about SEO (Core Web Vitals are a ranking factor), and now also about visibility in AI assistants.
The good news: you don't need to throw away your current site. You need to split it properly into a fast static frontend and the backend you're used to — and then walk through the recommendations Google has already written for all of us, with discipline. If that sounds like more than an in-house team wants to take on, that's exactly what a website speed optimization service is for.
Want to see what that would look like on your site? Drop us a line — we'll show you on a live example.
