Core Web Vitals in 2026: what small businesses need to know

TL;DR: Only 48% of mobile websites pass all three of Google’s Core Web Vitals (HTTP Archive, 2025). If your site loads slowly, shifts around while loading, or feels unresponsive when people tap buttons, you’re probably losing customers without realising it. This guide explains the three metrics in plain English and gives you a checklist to hand your developer.

If you run a small business in Australia and you have a website, you’re already ahead of 59% of Australian small businesses who don’t have one at all (GoDaddy, 2024). But having a website isn’t the same as having a website that works well.

I spend a lot of time auditing websites for clients, and I keep running into the same problem. Business owners have spent good money getting a site built, but nobody told them it loads in six seconds on a phone, or that the buttons feel broken, or that the text jumps around while you’re trying to read it. They didn’t know these things had names. They didn’t know Google was measuring them.

Google calls these measurements Core Web Vitals. There are three of them, they’ve changed recently, and they affect both your search rankings and whether people actually stick around long enough to buy something. I’m going to explain all three in plain English, show you exactly how to check your own scores, and give you a checklist you can hand to whoever built your website.

No jargon. No developer prerequisites. Just the stuff that actually matters for your business.

What are Core Web Vitals?

Core Web Vitals are three specific measurements Google uses to evaluate how your website feels to real visitors, based on data from actual Chrome browser sessions (Google Search Central, 2026). Not how it looks. Not what it says. How it feels to use - and whether people stick around or leave.

Think of it like a restaurant inspection, but for websites. Google checks three things:

1. LCP (Largest Contentful Paint) - How fast does the main content appear? Like waiting for the menu to arrive.
2. INP (Interaction to Next Paint) - Does the site respond when you tap things? Like pressing the elevator button and nothing happening.
3. CLS (Cumulative Layout Shift) - Does the page stay still while loading? Like reading a newspaper and someone keeps moving it.

Google evaluates these at the 75th percentile of real user data (web.dev, 2025). That means they’re not testing your site on a fast computer with fibre internet. They’re looking at how it performs for your actual visitors, including the ones on 4G in regional areas.

Each metric gets a traffic-light rating: green (good), amber (needs improvement), or red (poor). You need all three green to pass.

Only 48% of websites manage that on mobile (HTTP Archive, 2025). More than half of all websites fail. That number has been climbing - it was 36% in 2023 and 44% in 2024 - but there’s still a long way to go.

The thresholds for each metric:

Why should a small business owner care?

A 0.1-second improvement in mobile load time increased retail conversions by 8.4% and travel conversions by 10.1% across a study of 37 brand websites and 30 million user sessions (Deloitte/Google, 2020). For a small business doing $10,000 a month online, that’s $840 extra per month from a change your visitors won’t consciously notice.

The business case isn’t theoretical. Vodafone ran an A/B test with roughly 100,000 clicks per day per variant and found that a 31% improvement in LCP led to 8% more sales, 15% better lead generation, and 11% better cart completion (web.dev, 2021). Fotocasa, a Spanish real estate platform, moved their INP score from “needs improvement” to “good” and saw a 27% increase in contact leads (web.dev, 2024).

You might be thinking those are big companies. Fair point. But the maths scales down. If 53% of mobile visitors abandon sites that take longer than three seconds to load (Google, 2017), and your site takes five seconds, you’re losing people before they even see what you sell.

The bounce rate curve tells the story:

The cliff at five seconds is the important bit. That’s where you stop losing a few visitors and start losing most of them.

And in Australia specifically, 97.1% of the population is online, with 34.1 million mobile connections for a population of about 27 million (DataReportal, 2026). People have multiple devices. They’re browsing on their phones at lunch, on the tram, waiting at the school gate. If your site doesn’t work well on mobile, it doesn’t work well for the majority of your customers.

LCP: how fast does your page actually appear?

LCP measures how long it takes for the largest piece of content on your page to become visible, and it’s the metric most people think of when they talk about “page speed.” Google considers under 2.5 seconds good, 2.5 to 4 seconds needs improvement, and over 4 seconds poor (Google Search Central, 2026).

In practice, this is usually your hero image, a large heading, or a video thumbnail. It’s the moment your visitor stops staring at a white screen and starts seeing your actual website.

Currently, 62% of mobile websites pass LCP, but only 74% on desktop (HTTP Archive, 2025). That 12-percentage-point gap matters because Google uses mobile-first indexing, meaning Google ranks your site based on its mobile performance, not its desktop performance (Google Search Central, 2026).

What causes bad LCP

The usual suspects for small business websites:

• Massive images. A 4MB hero photo that looks identical at 200KB after compression. This is the single most common issue I see in audits.
• Slow hosting. Cheap shared hosting where your site competes with hundreds of others for server resources.
• Too many fonts. Loading four different Google Fonts when one or two would do the job.
• Render-blocking scripts. JavaScript and CSS files that the browser has to download and process before it can show anything. 67.7% of websites request at least one render-blocking third party (HTTP Archive, 2025).
• No caching. Your server rebuilds every page from scratch for every visitor instead of serving a cached copy.

Quick test

Open your site on your phone using a mobile data connection (turn off WiFi). Count “one Mississippi, two Mississippi” from when you tap the link to when you see the main content. If you get past three, your LCP probably needs work.

INP: does your site respond when people tap things?

INP replaced an older metric called FID in March 2024 and measures how long your page takes to visually respond after a user taps, clicks, or types something (web.dev, 2025). Good is under 200 milliseconds - that’s a fifth of a second. Over 500 milliseconds is poor.

You know that feeling when you tap a button on a website and nothing happens? So you tap it again, and then two things happen at once? That’s bad INP. The page is doing so much work behind the scenes that it can’t respond to your taps quickly enough.

This is the newest Core Web Vital, and it’s catching a lot of websites off guard. Desktop handles it fine - 97% of desktop pages pass. But only 77% of mobile pages do, and only 53% of the top 1,000 most-visited websites pass on mobile (HTTP Archive, 2025). If the biggest sites in the world are struggling with this, smaller sites loading chat widgets, analytics scripts, and social media plugins are probably doing worse.

What causes bad INP

The primary culprit is JavaScript. Specifically:

• Third-party scripts. Live chat widgets, analytics packages, social media embeds, ad networks. Each one adds processing time. Industry analysis suggests that ten or more third-party scripts can add over 500 milliseconds of interaction delay (SpyceMedia, 2025).
• Heavy page builders. Some WordPress page builders add enormous amounts of code. One analysis found Elementor alone adds over 21MB of unzipped code to a site (CoreWebVitals.io, 2026).
• Too much happening on page load. Animations, carousels, pop-ups, floating elements - all competing for the browser’s attention.

The mobile gap

Here’s what makes INP particularly tricky: according to one industry analysis, the median Total Blocking Time (a related measurement) is 67 milliseconds on desktop but 1,209 milliseconds on mobile (Hashmeta, 2025). That’s roughly an 18x difference. Mobile processors are significantly weaker than desktop ones. All that JavaScript your developer tested on their MacBook Pro runs very differently on a visitor’s three-year-old Android phone.

CLS: does your page stay still while loading?

CLS measures how much your page content shifts around unexpectedly while it loads. A score under 0.1 is good (Google Search Central, 2026). This is the one metric where desktop actually performs worse than mobile - 81% of mobile pages pass but only 72% of desktop pages do (HTTP Archive, 2025).

If you’ve ever been reading an article and the text suddenly jumps because an ad loaded above it, or you’ve tried to tap a button and hit the wrong thing because the layout shifted, that’s CLS in action.

What causes bad CLS

• Images without dimensions. If your HTML doesn’t specify how big an image will be, the browser renders the text first and then shoves everything down when the image loads.
• Late-loading ads. Display ads that inject themselves into the page after the initial content has rendered.
• Web fonts loading late. The browser renders text in a fallback font, then swaps to the custom font at a different size, shifting everything around.
• Dynamic content injection. Cookie consent banners, newsletter pop-ups, or promotional bars that push content down.
• Iframes without reserved space. Embedded maps, videos, or social media widgets that expand after the page has already drawn itself.

CLS is usually the easiest of the three metrics to fix. Setting image dimensions and reserving space for ads solves most problems.

Do Core Web Vitals actually affect Google rankings?

Google’s official position is that Core Web Vitals are a ranking signal, but content relevance matters more. Their documentation states: “For many queries, there is lots of helpful content available. Having a great page experience can contribute to success in Search, in such cases” (Google Search Central, 2026).

John Mueller from Google has been more direct. In 2024, he said Core Web Vitals are “not giant factors in ranking” but described them as more than just a tiebreaker (Search Engine Journal, 2024).

The way I explain it to clients: if you sell plumbing supplies in Melbourne and you’re the only result with good content about a specific fitting, your page speed doesn’t matter much for that search. But if there are ten similar pages competing for “best plumber Melbourne,” the one that loads fastest and feels smoothest has an edge.

Think of it as a tiebreaker that gets more powerful the more competitive your niche is. And given that December 2025 saw Google roll out another core algorithm update across 18 days (Search Engine Land, 2025), the bar keeps rising.

The bigger impact is indirect. Faster sites have lower bounce rates, higher engagement, and better conversion rates. Those user behaviour signals probably influence rankings more than the CWV scores themselves. If you want to understand how page speed fits into a broader SEO and search optimisation strategy, it’s one piece of a much larger puzzle - but it’s the piece most business owners can actually measure. And if you’re running Google Ads, page speed directly affects your Quality Score and cost per click — I explain that connection in how to tell if your Google Ads are actually working.

The WordPress problem (and what to do about it)

WordPress powers roughly 43% of all websites (W3Techs via WordPress.com, 2025). If you run a small business website, there’s a decent chance it’s on WordPress. And WordPress has a Core Web Vitals problem.

Only 43.44% of WordPress sites pass all three Core Web Vitals on mobile, compared to 75.22% for Shopify, 70.76% for Wix, and 67.66% for Squarespace (Search Engine Journal, 2025).

That’s not because WordPress is bad. It’s because WordPress gives you freedom, and freedom includes the freedom to install 25 plugins, a bloated theme, and three different analytics scripts. Shopify and Squarespace limit what you can do, and that limitation is actually protecting their users’ page speed.

It’s not hopeless

WordPress 6.8 introduced speculative loading (the Speculation Rules API), which pre-loads pages a visitor is likely to click on. Sites that enabled this saw roughly a 1.9% improvement in LCP passing rates (Make WordPress Core, 2025). Small improvement, but it’s free.

The real wins on WordPress come from a conversation with your developer about plugins. Most WordPress performance issues come from:

• Plugin bloat. A typical WordPress site runs 20-30 plugins (CoreWebVitals.io, 2026). Each one adds CSS and JavaScript.
• Heavy themes. Multi-purpose themes that load features you never use.
• Page builders. Some are more efficient than others. Ask your developer which one they’re using and what it costs in performance.
• Unoptimised images. WordPress doesn’t compress uploaded images aggressively by default.

If your site is on Shopify, Squarespace, or Wix, you get less control but better defaults. The platform handles most performance optimisation for you. Worth knowing when you’re choosing (or reconsidering) a platform.

How to check your own scores in five minutes

You don’t need technical knowledge for this. Open pagespeed.web.dev in your browser, type in your website address, and click “Analyze.”

It takes about 30 seconds. You’ll get a score out of 100 and individual grades for each Core Web Vital. The important bit is the section labelled “Core Web Vitals Assessment” at the top. You’re looking for either a green pass or a red fail.

Run the test on “Mobile” first (it’s the default tab). That’s what Google uses for ranking.

What to do with the results

If you pass all three: brilliant. You’re in the better-performing half of the internet. Keep an eye on it quarterly to make sure nothing’s slipped.

If you fail one or more: don’t panic. Screenshot the results and send them to whoever manages your website. The report lists specific problems and suggestions, ordered by impact. Your developer will understand what to fix. You don’t need to.

Other free tools worth knowing about

• Google Search Console (search.google.com/search-console) - shows your Core Web Vitals over time, based on real visitor data. Requires a quick setup but then runs automatically.
• Chrome DevTools Lighthouse - built into the Chrome browser. Right-click any page, click “Inspect,” go to the “Lighthouse” tab, and run an audit.
• GTmetrix (gtmetrix.com) - shows a detailed waterfall chart of what’s loading and how long each thing takes.

Six things to ask your developer today

You don’t need to understand the technical details to get better Core Web Vitals. You just need to ask the right questions. Here’s a checklist you can send directly to your developer or agency:

1. “Can you convert our images to WebP format?” WebP images are 25-34% smaller than JPEG with no visible quality loss (Google). This is usually the single biggest quick win.

2. “Can you add lazy loading to images below the fold?” Images that aren’t visible when the page first loads shouldn’t be loaded until the visitor scrolls down to them. One line of code: loading="lazy".

3. “Are we deferring non-critical JavaScript?” Analytics, chat widgets, social media embeds, and tracking scripts don’t need to load before the main content. They should load after.

4. “Do our images have width and height attributes?” This prevents layout shift. The browser reserves the correct space before the image loads.

5. “Are we using a CDN?” A Content Delivery Network serves your site from a server geographically close to each visitor. Cloudflare offers a free tier that handles this for most small business websites.

6. “Can you run PageSpeed Insights and show me the results?” If your developer can’t explain your Core Web Vitals scores, that tells you something.

None of these are expensive changes. Most take a competent developer an hour or two. And the odds are good that your site has low-hanging fruit to pick - the majority of websites are loading unnecessary scripts before the main content even appears. If you don’t have a developer you trust, or you’re not sure where to start, get in touch and I can point you in the right direction.

The accessibility bonus you get for free

Something that rarely comes up in the Core Web Vitals conversation: fixing your CWV scores often fixes accessibility problems at the same time.

94.8% of the top one million homepages have at least one WCAG accessibility failure, with an average of 51 errors per page (WebAIM, 2025). The most common? Insufficient text contrast, affecting 79.1% of pages.

But the overlap goes deeper than contrast ratios. INP directly maps to keyboard accessibility. When your page is too busy processing JavaScript to respond to a tap, it’s also too busy to respond to a keyboard press. Screen reader users, people navigating with a keyboard or switch device - they all experience the same delay. Fix your INP and you’ve fixed their experience too.

CLS affects focus order. When content shifts unexpectedly, the element a keyboard user has focused on can move off-screen. That’s not just annoying, it can make a site unusable for people with motor disabilities.

The European Accessibility Act took effect in June 2025, mandating accessibility compliance for websites in the EU (European Commission, 2025). Australia’s Disability Discrimination Act has similar requirements. Improving your Core Web Vitals is a step toward meeting both.

Two problems. One set of fixes. That’s a good deal for any small business.

FAQ

What are the three Core Web Vitals in 2026?

The three Core Web Vitals are LCP (Largest Contentful Paint, measuring load speed), INP (Interaction to Next Paint, measuring responsiveness), and CLS (Cumulative Layout Shift, measuring visual stability). INP replaced the older FID metric in March 2024. Google uses all three to assess your site’s user experience.

How much do Core Web Vitals affect Google rankings?

Core Web Vitals are a confirmed ranking signal, but content relevance still outweighs them. Google’s John Mueller described them as “not giant factors” but more than a tiebreaker (Search Engine Journal, 2024). They matter most in competitive niches where multiple pages have similar content quality.

Is WordPress bad for Core Web Vitals?

WordPress isn’t inherently bad, but it has the lowest CWV pass rate of major platforms at 43.44%, compared to Shopify at 75.22% (Search Engine Journal, 2025). The problem is usually plugin bloat and heavy themes, not WordPress itself. A well-optimised WordPress site can score perfectly.

How do I check my Core Web Vitals score?

Go to pagespeed.web.dev, enter your website address, and click “Analyze.” The test takes about 30 seconds and shows you pass/fail grades for each Core Web Vital. Run the mobile test first, as that’s what Google uses for ranking decisions.

What’s the fastest way to improve Core Web Vitals?

Converting images to WebP format and deferring non-critical JavaScript typically deliver the biggest improvements. The Deloitte/Google study found that even a 0.1-second improvement in load time increased retail conversions by 8.4% (web.dev, 2020). Start with the “Opportunities” section of your PageSpeed Insights report.

Do I need a developer to fix Core Web Vitals?

For most fixes, yes. Image optimisation, JavaScript deferral, and caching configuration require some technical knowledge. But checking your scores and understanding the results doesn’t require any technical ability. Run PageSpeed Insights yourself, then share the results with your developer.

Does site speed affect mobile conversions?

Significantly. 53% of mobile visitors abandon sites that take longer than three seconds to load (Google, 2017). The conversion rate drops roughly 4.42% with each additional second of load time in the first five seconds (Portent, 2022). On mobile, speed is revenue.

Nathan Schram is a digital consultant and founder of Little Bear Apps based in Melbourne, Australia. He helps small businesses with web design, SEO, and technology strategy. For a practical guide on checking whether your paid campaigns are delivering results, see How to tell if your Google Ads are actually working.