PageSpeed 100/100 on a Live Site: What We Did and Why It Works

The homepage of this site scores 100/100 in Google PageSpeed Insights in all four categories — performance, accessibility, best practices and SEO — on both mobile and desktop. In the measurement dated July 17, 2026, LCP came in at 1.0 s on mobile and 0.3 s on desktop; we measured again on the day this post was published, and the result is the same: four 100s, CLS of 0, total blocking time of 0 ms. You can verify it in the live report.

This post is not about chasing a score. It is about the architectural decisions that produce that score as a byproduct — because 100/100 is not a late-stage polish, it is the outcome of choices made at the start.

Why Should You Care?

Speed is not a matter of technical pride; it is a matter of money:

• Ad budget: If a visitor you paid for per click leaves because the page takes 4 seconds to open, that budget is wasted.
• Google ranking: Core Web Vitals signals are a ranking factor; a slow site ranks lower with the same content.
• Trust: A site that opens instantly on mobile says “these people know what they are doing” within the first second. A slow agency site is an advertisement against its own service.

The Five Decisions Behind the Result

1. Generate HTML at publish time, not at visit time

The site is compiled statically with Astro: every page’s HTML is ready before it is ever visited. When a visitor arrives there is no database query, no template rendering, no waiting — a prebuilt file is served directly, from Cloudflare’s globally distributed edge locations, at the point closest to the visitor.

2. Draw the hero with code, not an image

The animated panel on the homepage is not an image file; it is an interface drawn with HTML and CSS. Because the largest content element is text, LCP never waits for an image to download. Where images are used, every file is WebP, sized to its real display dimensions, and everything below the fold loads with lazy loading.

3. Fix the layout up front

Every image carries its width and height in the HTML. The browser reserves the space before the file arrives, so nothing jumps while the page opens. The secret behind a CLS of 0 really is that simple: reserve space up front instead of fixing shifts later.

4. Treat JavaScript as the exception

There is barely any script running on the page — no heavy framework bundle, no pile of third-party widgets. The main thread sits idle, so total blocking time is 0 ms. Every proposed script is treated as a cost item, and most proposals are rejected.

5. Cache aggressively, keep HTML fresh

Static assets (CSS, JS, icons) are served with one-year immutable cache headers; HTML is refreshed on every deploy. On a second visit, the browser re-downloads almost nothing.

“Why Is Our Site Slow?”

The four causes we see most often on client sites:

1. Setups that generate HTML from scratch on every page view, with no caching
2. Unsized 3–5 MB images
3. Third-party scripts accumulated over time — analytics, chat, heatmaps
4. Unused CSS and JS shipped by theme and plugin sprawl

None of these require rebuilding the site from scratch, but they do require measuring first and fixing items one by one, largest first. We start every optimization engagement with a measurement, work down the list, and hand over the result as a PageSpeed report — live and verifiable, exactly like this site’s.

If you want to see where your site stands today, take a look at our site speed optimization service or write to us; let’s run the first measurement together.