Core Web Vitals Explained for Business Owners

Core Web Vitals are three metrics Google uses to measure how fast and smooth your website feels to real visitors. Since 2021, they have been a confirmed Google ranking factor, meaning they directly influence where your site appears in search results.

Despite their importance, most business owners have never heard of Core Web Vitals, or have heard the term but have no idea what it means. This guide explains all three metrics in plain language, why they matter for your business, and what you can do about them.

The Three Core Web Vitals

Largest Contentful Paint (LCP) - How Fast Your Page Loads

LCP measures how long it takes for the main content of your page to become visible. Specifically, it tracks when the largest element in the viewport (usually a hero image, heading, or large text block) finishes rendering.

What the scores mean:

• Good: under 2.5 seconds
• Needs improvement: 2.5 to 4.0 seconds
• Poor: over 4.0 seconds

Why it matters: When someone clicks through to your website from Google, they expect the page to load quickly. If they are staring at a blank screen for four seconds, many will hit the back button and click a competitor’s result instead.

Common causes of poor LCP:

• Large, uncompressed images (the most common cause)
• Slow server response times from cheap hosting
• Render-blocking JavaScript and CSS
• Heavy page builder frameworks loading unnecessary code
• Web fonts loading slowly or blocking page render

Interaction to Next Paint (INP) - How Responsive Your Page Feels

INP replaced First Input Delay (FID) as a Core Web Vital in 2024. It measures how quickly your page responds when someone interacts with it - clicking a button, tapping a link, typing in a form, or selecting a menu item.

What the scores mean:

• Good: under 200 milliseconds
• Needs improvement: 200 to 500 milliseconds
• Poor: over 500 milliseconds

Why it matters: When a visitor clicks something on your page, they expect an immediate response. If there is a noticeable delay between their click and the page reacting, it feels broken. Even a 300 millisecond delay feels sluggish and creates a poor user experience.

Common causes of poor INP:

• Heavy JavaScript execution blocking the main thread
• Too many third-party scripts (analytics, chat widgets, ad trackers)
• Complex page builder frameworks processing interactions
• Poorly optimised event handlers
• Large DOM size (too many HTML elements on the page)

Cumulative Layout Shift (CLS) - How Stable Your Page Is

CLS measures how much your page layout shifts around while it is loading and being used. You have probably experienced this: you start reading text on a page, and suddenly the content jumps down because an image or ad loaded above it. That is layout shift.

What the scores mean:

• Good: under 0.1
• Needs improvement: 0.1 to 0.25
• Poor: over 0.25

Why it matters: Layout shift is not just annoying - it causes real problems. Visitors accidentally click the wrong button because the page shifted at the exact moment they tapped. They lose their place while reading. It makes your site feel unstable and unprofessional.

Common causes of poor CLS:

• Images without width and height attributes (the browser does not know how much space to reserve)
• Ads or embeds loading without reserved space
• Web fonts loading and causing text to reflow (Flash of Unstyled Text)
• Dynamic content being injected above existing content
• Late-loading CSS changing the page layout

Why Core Web Vitals Matter for Your Business

They Affect Your Google Rankings

Google has confirmed that Core Web Vitals are a ranking signal. While they are not the most powerful signal (content relevance and backlinks still dominate), they serve as a tiebreaker. When two pages are equally relevant for a search query, the one with better Core Web Vitals gets the edge.

In competitive markets where many businesses have decent content and similar authority, Core Web Vitals can be the difference between page one and page two.

They Affect User Behaviour

Even setting aside Google rankings, poor Core Web Vitals directly impact your business:

• Slow sites lose visitors. Research consistently shows that each additional second of load time increases bounce rate. A site that loads in five seconds has a significantly higher bounce rate than one that loads in two seconds.
• Unresponsive sites lose conversions. If your contact form feels sluggish or your “Get a Quote” button takes half a second to respond, visitors question whether the form even works.
• Unstable sites lose trust. Layout shifts make your business look unprofessional. If your website cannot load smoothly, potential customers wonder what your actual service will be like.

They Affect AI Search Visibility

As AI search tools like Google AI Overviews and ChatGPT web search become more common, site performance matters in a new way. AI systems prefer to cite and recommend sites that provide a good user experience. A slow, unstable site is less likely to be referenced in AI-generated answers than a fast, clean one. Read more about this in our guide on how AI search is changing SEO.

How to Check Your Core Web Vitals

Google PageSpeed Insights

Visit pagespeed.web.dev and enter your URL. You will get both lab data (simulated test) and field data (from real visitors). The field data section shows your actual Core Web Vitals scores based on the Chrome User Experience Report.

Focus on the field data if it is available. Lab data is useful for diagnosing specific issues but does not always reflect real-world performance.

Google Search Console

In Google Search Console, navigate to “Core Web Vitals” under the “Experience” section. This shows you how your pages perform across your entire site, grouped by status (good, needs improvement, poor).

The advantage of Search Console is that it shows you which specific pages have issues, making it easier to prioritise fixes.

Chrome DevTools

For a more technical analysis, open Chrome DevTools (right-click on your page and select “Inspect,” then go to the “Performance” tab). This shows you exactly what is happening during page load and which elements are causing issues.

Why Page Builders Destroy Core Web Vitals

One of the most common reasons Australian small business websites fail Core Web Vitals is page builders. Tools like Elementor, Divi, Wix, and Squarespace generate bloated HTML, CSS, and JavaScript that slows everything down.

A typical page builder site loads:

• Hundreds of kilobytes of unused CSS
• Multiple JavaScript frameworks
• Dozens of unnecessary font files
• Deeply nested HTML elements that create a massive DOM

The result is poor LCP (too much code to process before the page renders), poor INP (too much JavaScript blocking interactions), and often poor CLS (dynamic elements loading unpredictably).

This is why we take a code-first approach to website builds. When you write clean, minimal code instead of relying on a page builder, you can achieve perfect or near-perfect Core Web Vitals scores. Our sites typically load in under one second and score 95 or above on PageSpeed Insights.

For a deeper look at this topic, read our guide on why your website is slow.

How to Improve Your Core Web Vitals

Quick Wins (Do These First)

1. Compress and resize images. Convert to WebP format, serve appropriately sized images for each screen size, and compress aggressively. This is often the single biggest improvement you can make.
2. Add width and height to all images. This tells the browser how much space to reserve, preventing layout shift.
3. Preload your largest image. If your above-the-fold content includes a hero image, add a preload link in your HTML head.
4. Remove unused plugins and scripts. Every third-party script adds weight. Remove anything you are not actively using.

Medium-Term Improvements

5. Optimise font loading. Use font-display: swap, preload critical fonts, and limit the number of font variants you load.
6. Defer non-critical JavaScript. Scripts that are not needed for the initial page render should load after the page is visible.
7. Upgrade your hosting. Slow server response times cannot be fixed with code optimisation alone. Quality hosting with Australian data centres makes a significant difference.
8. Implement lazy loading. Images below the fold should only load when the visitor scrolls to them.

Long-Term Solution

9. Rebuild on a clean codebase. If your site is built on a page builder, no amount of tweaking will achieve the same performance as a clean, code-first build. Our website rebuild service replaces bloated page builder code with minimal, performant HTML, CSS, and JavaScript.

Frequently Asked Questions

Q: Do Core Web Vitals really affect rankings?

Yes. Google has confirmed they are a ranking signal. The effect is most noticeable in competitive searches where multiple results have similar content quality. In those situations, better Core Web Vitals give your pages an edge. They are not going to override poor content or lack of relevance, but they can be the deciding factor between otherwise similar pages.

Q: My PageSpeed score is low but my site seems fast. Why?

PageSpeed Insights scores are based on lab tests using simulated slow connections and devices. Your site might feel fast on your laptop with fast internet, but load slowly on a mobile phone with average connectivity, which is how most of your visitors experience it. The field data section shows how real users actually experience your site.

Q: Can I pass Core Web Vitals on WordPress?

It is possible but difficult, especially with page builders. A stripped-down WordPress site with minimal plugins, a lightweight theme, good hosting, and careful optimisation can pass. But it requires significant ongoing effort compared to a code-first build that achieves great scores by default.

Q: How often should I check my Core Web Vitals?

Check monthly at minimum. Core Web Vitals can change when you add new content, install plugins, change hosting, or when third-party scripts update. Our ongoing SEO service includes monthly Core Web Vitals monitoring so issues are caught before they affect rankings.

Q: What is a good PageSpeed Insights score?

Aim for 90 or above on both mobile and desktop. Scores of 50 to 89 indicate room for improvement, and below 50 is poor. Most page builder sites score between 20 and 60 on mobile. Code-first sites typically score 90 to 100.

Our Data: A Real Core Web Vitals Before / After

The numbers below are from a verified aiRANKSEO rebuild of a Melbourne cleaning business. The site moved from WordPress + a heavy page-builder theme onto Astro on Cloudflare’s global CDN, with the explicit goal of crossing every Core Web Vitals threshold. Full case study: Melbourne cleaning business.

Metric	Threshold (“good” per web.dev)	Before (mobile)	After (mobile)	Result
Largest Contentful Paint (LCP)	<= 2.5 s	4.1 s	1.4 s	Fail -> Pass with 1.1s of headroom
Cumulative Layout Shift (CLS)	<= 0.10	0.24	0.00	Fail -> Pass (perfect)
Total Blocking Time (TBT)	<= 200 ms	1,840 ms	65 ms	Fail -> Pass
First Contentful Paint (FCP)	<= 1.8 s	2.7 s	0.9 s	Fail -> Pass
Time to First Byte (TTFB)	<= 800 ms	920 ms	148 ms	Fail -> Pass
PageSpeed Insights (mobile) score	n/a	38	96	+58
Days to ship	n/a	n/a	35	—

What the ranking lift was. Crossing the 2.5s LCP threshold on competitive AU queries is typically worth 2-5 ranking positions inside the recrawl window. The cleaning business measured: one page reached #1 in Australia for its target query within 35 days of launch; organic sessions rose +151% in the following 30 days; form submissions rose +300% across the 90-day window. The PSI numbers explain the ranking move; the ranking move explains the conversion lift.

Note on field vs lab. The numbers above are PSI lab scores (Lighthouse via Slow-4G + 4x CPU throttle). Field CrUX populates after ~28 days of sustained real-user traffic and is what Google actually uses for ranking. For a site rebuild, lab scores are the leading indicator; field scores are the lagging confirmation.

Sources and Further Reading

• web.dev — Core Web Vitals — the official definitions and “good / needs improvement / poor” thresholds for LCP, INP, and CLS
• web.dev — Largest Contentful Paint (LCP) — deep documentation on what counts as the LCP element and how to fix it
• Google PageSpeed Insights — the free testing tool that returns the same scores Google uses internally
• Chrome User Experience Report (CrUX) — field-data source Google uses to score real-user performance for ranking

---

Want to know your Core Web Vitals scores and what it would take to fix them? Request a free audit and quote - we will test your site and show you exactly what needs improving.