Core Web Vitals Checklist: Is Your Site Passing?

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. Google's own documentation is blunt about why it matters: it highly recommends site owners achieve good Core Web Vitals for success with Search, because page experience is part of what its core ranking systems seek to reward. If your site fails, you compete from behind on every query, convert worse, and get less out of every click you pay for. Most business owners have no idea which side of the line they are 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 is a fail. Google's bar is 2.5 seconds or less. This one has the clearest money trail attached to it: in a server-side A/B test, Vodafone Italy improved LCP by 31% and recorded 8% more sales, with no other functional or visual change to the page.

Responsiveness (INP). When someone taps a button or opens a menu, how quickly does the page react? If it freezes for a beat before anything happens, that is the feeling Google is measuring, and it wants a response inside 200 milliseconds. Anything longer feels broken even when the page works. It is worth more than it sounds: redBus improved its INP and increased sales by 7%.

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.

One detail decides how you should read your own score: Google grades you at the 75th percentile of real visits, not the average. You pass a metric only when at least three out of four page views hit the "good" threshold. That is deliberate — it means your slowest quarter of visitors, usually the ones on mid-range phones and patchy mobile networks, decide whether you pass. Averages hide those people. Google does not let you hide them.

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, and it lands before anyone reads your offer. Google's own performance course points at two results worth knowing: the BBC found it lost a further 10% of users for every extra second its site took to load, and The Economic Times recorded a 43% better bounce rate after getting inside the Core Web Vitals thresholds. Visitors who leave at that stage do not come back, do not fill in your form and do not click your CTA. They bounce, and your competitors get them instead.

The third hit is on paid advertising, and it is worth being precise here because the internet is full of overstated versions of this claim. Google does not publish Core Web Vitals as a Quality Score input. What it does publish is that landing page experience is one of the three components of Quality Score, alongside expected click-through rate and ad relevance — and a page that makes people wait is not delivering a good landing page experience. The practical read: speed is not a documented Ads formula input, but the behaviour it causes is exactly what the formula measures.

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.

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.

Do not rely on a single test. The signal Google uses comes from field data: real visits from real Chrome users, aggregated as a 28-day rolling average in the Chrome User Experience Report, which is what feeds the Core Web Vitals report in Search Console. That is the number that moves your rankings. A lab test tells you what to fix; the field data tells you whether it worked.

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

The honest answer is that nobody can quote you a universal percentage, and anyone who does is guessing. What exists instead is a body of published results from companies that measured the change properly. Rakuten 24 ran an A/B test where the only difference was Core Web Vitals optimization and saw revenue per visitor rise 53.37% and conversion rate 33.13%. Nykaa recorded 28% more organic traffic from tier-2 and tier-3 cities after a 40% LCP improvement. Tokopedia cut LCP by 55% and saw 23% longer average sessions. Agrofy Market improved LCP by 70% and cut load abandonment by 76%.

Read those as evidence of direction and rough scale, not as a forecast for your site — they are different businesses with different baselines. The transferable point is that every one of those wins was measured, not estimated, usually with a server-side A/B test on a single high-value page. That is the same thing you should do before you spend money on a rebuild: pick the page that carries your revenue, fix it, and measure the delta. If failing three checklist items were free, none of these companies would have bothered.

The Quick Wins vs the Real Fix

Most checklist failures do not need a rebuild. They need focused attention from someone who knows where to look. The work splits into three tiers. Quick wins take days: compress and convert images, remove unused third-party scripts, set explicit dimensions on images and ad slots, lazy-load video, preload fonts. Two of those are big enough to have their own breakdowns — why your images are quietly slowing the whole site down and what chat widgets and trackers are costing you.

Medium effort takes a few weeks: refactoring heavy components, replacing bloated plugins, moving onto a CDN, improving server response time, trimming the JavaScript bundle. This is where most of the real gain lives, and where a structured performance pass pays for itself fastest.

Structural fixes are a real project. If the site is slow at the foundation — an old WordPress theme, a page builder carrying thirty plugins, a front end that cannot be server-rendered — no amount of tuning saves it. That is when a rebuild on a modern framework like Next.js is the honest answer, because it renders on the server, ships only the code each page needs, and serves from a global CDN by default. We took that route with Asturmet, a weather platform serving high-resolution map layers and fourteen-day hourly forecasts, where the data density left no room for a slow front end.

Which tier you need depends on your stack, your traffic and your growth plans. A small brochure site can live on quick wins. A B2B site running paid campaigns, or a SaaS product where speed shapes every session, needs the structural fix. If you are trying to decide, the wider case for treating speed as a revenue problem is the place to start, and the mobile-specific version of the same argument is where most of the money actually is.

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.

Three Mistakes That Keep Sites Failing

The same three patterns show up whenever a business tries to handle Core Web Vitals optimization on its own.

Installing a "speed plugin" and calling it done. Caching plugins help at the margins, but they cannot fix a site whose architecture is slow, and they routinely break layouts in ways that make visual stability worse. A plugin is not a strategy.

Optimizing the homepage and ignoring everything else. Google evaluates pages, not sites. The landing page bringing in most of your demos is usually not the page you just sped up. Test every URL that carries revenue — and the anatomy of what those pages need matters as much as how fast they load.

Confusing lab scores with real-world data. PageSpeed Insights shows you two different things: a lab simulation run on demand, and field data from real Chrome users. Only the field data reflects what your customers experience. A green lab score sitting on top of red field data means your actual visitors are still waiting — and Google is scoring you on their experience, not on your test run.

Want to Know Exactly Where You Stand?

If you went through this checklist and failed more than three items, you already know there is 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 you. Send us your URL and we will run a full Core Web Vitals audit for free, pulled from Google's own data, with a plain-English breakdown of what is hurting you and what it would take to fix. No pitch, no pressure — just the numbers you need to make the call.

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