You’ve probably seen the term PageSpeed before. Maybe in a pitch from a web developer. Maybe buried in a report your current agency sent over. It sounds like a developer thing. Something technical, something you shouldn’t have to think about.

But it hits your revenue. Directly.

What Google PageSpeed Insights Actually Measures

Google’s PageSpeed Insights tool doesn’t just clock how fast a page loads. It measures Core Web Vitals, a set of real-world performance metrics that reflect what a visitor actually experiences on your page.

Three signals matter most.

Largest Contentful Paint (LCP)

LCP tracks how long it takes for the biggest visible element on the page (usually a hero image or headline) to fully render. Google wants this under 2.5 seconds. Anything slower and your visitors are staring at a half-loaded page while your competitor’s site is already done.

I see this one constantly. A business has a gorgeous hero image, but it’s a 3MB uncompressed JPEG. The design looks great in Figma. On a phone over LTE? It crawls.

Interaction to Next Paint (INP)

INP replaced First Input Delay in 2024. It measures how responsive your page is when someone actually interacts with it: clicks, taps, form fields. Google’s threshold is under 200 milliseconds. A site with poor INP feels sluggish. You click a button and nothing happens for a beat. Then it catches up.

This is almost always a JavaScript problem. Heavy frameworks, bloated plugin stacks, third-party scripts fighting for the main thread. I’ve audited WordPress sites running 40+ plugins where every click felt like wading through mud.

Cumulative Layout Shift (CLS)

CLS measures visual stability. How much does the page jump around after it starts rendering? You know the feeling: you go to tap a button and the page shifts, so you hit something else entirely. Infuriating.

Google wants a CLS score below 0.1. The usual culprits are images without declared dimensions, web fonts that swap in late, or ads that shove content around when they load.

Why It Matters: Rankings and Revenue

In 2021, Google formally added Core Web Vitals to its ranking algorithm. So your site’s performance is now a direct input into where you show up in search results. Two sites with similar content and backlinks won’t rank the same if one is noticeably faster.

But the real cost isn’t just SEO. It’s the people who leave.

I’ve rebuilt sites that were scoring in the 30s and 40s on mobile. Our own MVGeneral site was one of them. After the rebuild, people stayed longer, visited more pages, and the inquiries picked up. Nothing else changed. Same company, same services, same market. The site just stopped driving people away.

Every second your page takes to load is a filter. It lets through fewer people. And the ones who bail? They don’t come back. They click the next result.

Every site we ship is built on the same static-first architecture, and every one scores 95 or above on mobile PageSpeed. Those are live production scores on real client sites, not staging environments.

The Common Culprits Behind Slow Sites

Most slow business websites share the same handful of problems. I see these on nearly every audit.

Unoptimized images are the biggest offender. A 4MB JPEG doesn’t magically shrink at mobile resolution. Images need to be served in modern formats like WebP or AVIF, compressed properly, and sized for how they’ll actually display. This single fix sometimes jumps a score by 20+ points.

Render-blocking JavaScript and CSS is the next one. When a browser hits a script or stylesheet, it stops rendering the page until that file downloads and executes. Poorly built sites can have dozens of these blocking resources stacked up.

Then there are the bloated page builders. WordPress with Elementor, Divi, or similar drag-and-drop tools can add hundreds of kilobytes of JavaScript and CSS that the page never even uses. These tools are built for easy editing, not performance. And it shows.

No CDN or bad hosting means every visitor pays the latency cost of distance. Someone in Phoenix loading a site hosted in New York waits longer than necessary for every single byte.

And finally: third-party scripts. Every chat widget, tracking pixel, and analytics tag loads external code. Each one is a performance liability. I’ve seen sites where the third-party scripts alone took longer to load than the entire page should have.

What a 95+ Score Actually Looks Like

You don’t get a consistently high PageSpeed score by tweaking what you already have. It takes architectural decisions from the start.

Static-first architecture is the single biggest lever. Static HTML served directly from a CDN edge node loads faster than any dynamically generated page. Full stop. Doesn’t matter how well-optimized the dynamic page is. We build with Astro, which generates fully static HTML at build time. No server-side processing at the moment of the request.

Optimized asset delivery means images in the right format, right size, right compression. CSS that contains only what the page actually uses. JavaScript that loads after the page is interactive, not before.

Edge delivery through platforms like Cloudflare ensures low latency globally. Not just in the city where your server happens to sit.

This is why the sites we build at Enthrall consistently score 95 or above on PageSpeed Insights. It’s not a line item we add to proposals. It’s built into the architecture of every site we deliver. We don’t ship slow sites. Period.

How to Check Your Current Score

You can check yours right now. Go to pagespeed.web.dev, enter your URL, and run the report. Look at the mobile score. That’s the one that matters most for rankings and for the majority of your traffic.

Below 70? You’ve got a performance problem that’s actively costing you traffic and conversions. Below 50? It’s dragging your business down, and you might not even realize how much.

If you want to know what it would take to fix it, or what a purpose-built, high-performance site would look like for your business, start a conversation with us.