Is Your Website Passing Google's Speed Test? A Non-Technical Checklist

Google is running a speed test on your website right now. You don't see it, you didn't sign up for it, and nobody on your team is monitoring the results. But the score it produces is quietly deciding how often your site shows up in search results, how much of your ad spend converts, and how many visitors abandon you before they ever read your headline.

The test is called Core Web Vitals, and since 2021 it has been an official Google ranking factor. If your site fails it, you rank lower, convert worse, and pay more for every click. If your site passes it, you rank higher, convert better, and get more from every dollar you spend on marketing. Most business owners have no idea which side they're on.

This article is a non-technical core web vitals optimization checklist. No jargon, no code. Just a clear list of questions you can answer in ten minutes to know whether your website is helping or hurting your business. If you fail three or more items on this list, your site is almost certainly costing you money.

What Google's "Speed Test" Actually Measures

Core Web Vitals is a set of three simple measurements Google takes on real visits to your site. You don't need to memorize the acronyms, but it helps to know what each one is really checking.

Loading speed (LCP). How long does it take for the main content of your page to appear? If a visitor clicks a Google result and stares at a blank screen for four seconds, that's a fail. Google wants this in under 2.5 seconds. Amazon famously found that every additional 100 milliseconds of load time cost them 1% in sales.

Responsiveness (INP). When someone clicks a button or taps a menu, how quickly does your site react? If the page freezes for a beat before anything happens, that's the feeling Google is measuring. It wants responses in under 200 milliseconds. Anything longer feels broken — even if the page eventually works.

Visual stability (CLS). Does your layout jump around while loading? You've felt this one: you go to tap a link and an ad pushes it down at the last second, so you tap the wrong thing. Google hates that experience as much as your users do. It measures the amount of unexpected movement on the page and penalizes sites that shift around.

Put together, these three metrics try to answer one business question: does your website feel fast, responsive, and stable to real visitors? If the answer is yes, Google rewards you. If the answer is no, Google buries you — and your visitors leave before they ever become customers.

Why This Matters for Your Revenue

The cost of failing the speed test shows up in three places: search rankings, conversion rates, and ad efficiency. A site that fails Core Web Vitals can drop several positions on Google for competitive keywords, which means less traffic and fewer leads. We've covered the revenue math in detail in this piece on what a 3-second load time is actually costing you, but the short version is that most companies are underestimating the damage by at least half.

The second hit is on conversion. When a page takes longer than three seconds to become usable, 40% of visitors leave. They don't come back. They don't fill out your form. They don't click your CTA. They just bounce, and your competitors get them instead.

The third hit is on paid advertising. Google Ads uses Core Web Vitals as part of your Quality Score, which directly affects what you pay per click. Two companies bidding on the same keyword can pay very different amounts depending on how fast their landing pages load. A slow site is a tax on every ad dollar you spend.

The Non-Technical Core Web Vitals Checklist

Here are the ten questions every business owner should be able to answer about their website. You don't need to know any code. Grab your phone, open your site, and count how many of these you fail.

1. Does your homepage show real content in under 3 seconds on mobile?

Turn off Wi-Fi, use 4G, load your homepage, and count. If you see a blank screen, a spinner, or a logo that sits alone for more than three seconds, you fail. Real visitors experience this every day. Mobile is where more than half your traffic comes from, and it's usually far slower than you think.

2. When you tap a menu or button, does it respond instantly?

Open your site on a phone and start tapping things. If there's a half-second pause before the menu opens, or if you tap a button twice because nothing happened the first time, your responsiveness score is poor. Visitors interpret that hesitation as a broken site, and they leave.

3. Does the page stay still while it's loading?

Load a page and watch it carefully. Does an image pop in and shove your headline down? Does an ad banner appear and push the whole page around? Does a cookie banner cover the text you were reading? Each shift is a strike against you, both with Google and with frustrated visitors.

4. Is your largest image smaller than 200 KB?

Oversized images are the single most common reason websites fail the speed test. A good modern hero image should be under 200 KB, not the 3 MB straight-from-the-camera file many sites serve. If your site was built without image optimization, every page is dragging a weight that kills your score.

5. Does your site work fine if JavaScript is turned off?

A well-built site shows its main content even when scripts are slow to load. If you see a totally blank page for a few seconds before anything appears, it means your visitors are waiting on heavy code instead of seeing your offer. Modern frameworks like Next.js solve this by rendering content on the server first, so the page is visible almost instantly.

6. How many third-party scripts are running on your site?

Chat widgets, heat maps, ad trackers, analytics tools, A/B testing scripts — each one looks harmless on its own. Stack ten of them together and your site starts crawling. If your homepage is loading more than five third-party scripts, you're paying for convenience with conversions.

7. Is your site using a CDN?

A content delivery network (CDN) serves your site from servers close to each visitor, instead of from one origin somewhere across the world. Without one, a visitor in Madrid requesting a site hosted in Virginia is waiting on every round trip. If your developer can't tell you which CDN you're using, odds are you aren't using one.

8. Do fonts load instantly, or do you see text change after a second?

If your headline appears in one font for half a second and then suddenly switches to another, you're watching a layout shift. That is a real penalty on the stability score, and it's fully preventable. Custom fonts should be preloaded and fallback fonts should be matched to them visually.

9. Does your site use modern image formats?

JPEG and PNG are twenty-year-old formats. Modern formats like WebP and AVIF deliver the same image quality at a fraction of the file size. A site still serving every hero image as a 4 MB PNG is paying a tax your competitors stopped paying years ago. Ask your team: are we serving WebP or AVIF? If they shrug, there's your answer.

10. When was the last time anyone measured your Core Web Vitals?

If you can't remember, or if the answer is "never," that's the most important failure on the list. Core Web Vitals drift over time. A site that passed a year ago may be failing today because new plugins, trackers, or content pushed it over the edge. Without ongoing monitoring, you don't know until your rankings drop.

How to Run the Test Yourself in Two Minutes

Google publishes the exact test criteria and a free measurement tool on web.dev/vitals. The fastest path for most business owners is PageSpeed Insights: go to pagespeed.web.dev, paste your URL, and hit analyze. In under a minute you'll get a score out of 100 for mobile and desktop, plus a pass or fail on each Core Web Vital.

Pay attention to the mobile score. Most decision makers test on their laptop, see a respectable number, and assume everything is fine. Mobile is where Google grades you hardest, and where most sites fail. If your mobile score is red or orange, that's what your customers are experiencing every day.

Don't rely on a single test. Google's own ranking signals come from field data — actual visits from actual Chrome users over the previous 28 days. You can see this in the Search Console under the Core Web Vitals report. That's the number that affects your SEO, not a one-off lab test.

If You Failed 3 or More Items, Your Site Is Costing You Money

Here's the honest math. Failing Core Web Vitals on mobile typically means at least a 20% hit to organic traffic over time, because you're ranking below competitors who pass. It typically means at least a 10 to 15% hit to conversion rate, because visitors abandon slow, jumpy pages. And it typically means a 10 to 30% premium on paid ads, because your Quality Score drops.

Stack those effects together on a business doing six figures in online revenue and the annual loss from a failing site is easily in the tens of thousands. Stack them on a business doing seven figures and the cost crosses six figures fast. And unlike most marketing problems, this one is entirely fixable.

The Quick Wins vs the Real Fix

There are two levels of Core Web Vitals optimization. The quick wins are things any competent developer can do in a few days: compress images, remove unused plugins, defer non-critical scripts, set up a CDN, swap to modern image formats. These usually move a failing site into borderline-passing territory. For many small sites, this is enough.

The real fix, for sites that need to consistently crush the test instead of just pass it, is architectural. That usually means rebuilding on a modern framework like Next.js that renders pages on the server, loads only the code each page needs, and ships content to visitors from a global CDN by default. This is the kind of foundation that keeps a site fast as it grows — without a developer fighting performance regressions every quarter.

Which approach is right depends on your stack, your traffic, and your growth plans. A small brochure site can get away with quick wins. A B2B site running paid campaigns, or a SaaS product where speed affects every user session, needs the architectural fix.

What "Good" Actually Looks Like

To set a concrete bar: a well-built modern business site should load its main content in under 1.5 seconds on mobile, respond to taps in under 100 milliseconds, and have almost zero layout shift. PageSpeed Insights mobile scores should sit in the 90s. That's the level of performance your competitors who take this seriously are hitting. Anything materially below that is a competitive disadvantage.

And the good news is that getting there is not mysterious. The same techniques have worked for years: render on the server, ship less JavaScript, compress everything, monitor continuously. The companies consistently passing Core Web Vitals aren't using magic. They just refuse to treat their website as a one-time project and instead treat performance as a permanent line item, the same way they treat SEO or paid advertising.

Want to Know Exactly Where You Stand?

If you went through this checklist and failed more than three items, you already know there's revenue on the table. The next step is a real measurement — not a one-off lab test, but the actual field data Google is using to rank your site. Send us your URL and we'll run a full Core Web Vitals audit for free, pulled from Google's own data, with a plain-English breakdown of what's hurting you and what it would take to fix it. No pitch, no pressure — just the numbers you need to make a decision.