Core Web Vitals: What They Are and Why They Affect Your Rankings

A website page taking five seconds to load, a menu that won't open when tapped, text jumping around as the page settles: these are not framing problems. They are the reason a visitor leaves before reading a word. Google has been measuring experiences like these since 2021, and pages that frustrate visitors appear lower in search results than pages that don't. Your content may be stronger than your competitor's. Your page experience may not be.

What are Core Web Vitals?

Core Web Vitals are a set of three page-experience signals Google uses to measure how a real visitor experiences a web page: how fast the main content loads, how quickly the page responds to a first tap or click, and how much the layout shifts unexpectedly while the page is still settling. Each signal has a defined threshold separating a good score from one needing improvement.

Key Takeaways

• Core Web Vitals measure three things: loading speed, interactivity, and visual stability, each with a specific numeric threshold.
• Google confirmed Core Web Vitals as a ranking signal in its 2021 Page Experience update, and the signals remain active in 2026.
• A page scoring poorly on even one signal can lose ground to a competitor whose content is weaker but whose experience is faster.
• Most small business websites fail on Largest Contentful Paint, usually because of uncompressed images and slow hosting.
• You can check your scores for free using Google Search Console's Core Web Vitals report and PageSpeed Insights.
• Fixing Core Web Vitals is not a once-off project; scores shift as you add content, plugins, and new media to your pages.

The Three Signals and What They Measure

Each of the three Core Web Vitals captures a different moment in a visitor's experience, and each has a threshold Google uses to classify a page as good, needing improvement, or poor.

How your pages are scored across all three Core Web Vitals signals

Core Web Vitals are Google's clearest technical SEO signal for user experience: if your pages load slowly or shift as they load, your rankings reflect that instability.

| Signal | What It Measures | Good | Needs Improvement | Poor |

|---|---|---|---|---|

| LCP (Largest Contentful Paint) | Time for the main content to load | Under 2.5 s | 2.5 s to 4.0 s | Over 4.0 s |

| INP (Interaction to Next Paint) | Delay between input and visual response | Under 200 ms | 200 ms to 500 ms | Over 500 ms |

| CLS (Cumulative Layout Shift) | Amount of unexpected layout movement | Under 0.1 | 0.1 to 0.25 | Over 0.25 |

Largest Contentful Paint (LCP) is the time it takes for the biggest visible element on the page, typically the main image at the top or a large heading, to finish rendering. Visitors do not read timing reports; they feel the wait. A page taking four seconds to render its main content loses attention before the content even arrives.

Interaction to Next Paint (INP) replaced First Input Delay in March 2024 as the interactivity signal. Where FID measured only the first click, INP measures the worst interaction delay across the full visit. A visitor who clicks a menu item, a button, or a form field and sees nothing happen for half a second is experiencing a failing INP score.

Cumulative Layout Shift (CLS) measures how much the layout moves around after the initial render. A news site loading its article and then shunting the text down when an advertisement appears above it is producing layout shift. The visitor reads the wrong paragraph, or taps the wrong button, because the page moved under their finger.

Why Google Treats Page Experience as a Ranking Factor

Google's core interest is sending visitors to pages they will find useful and pleasant. A slow, unresponsive, or visually unstable page is none of those things, so Google uses experience signals as a tiebreaker when content quality is otherwise comparable.

The Page Experience ranking signals documentation from Google Search Central confirms Core Web Vitals form part of the ranking criteria, alongside mobile-friendliness and HTTPS. Google is direct: a great page experience does not override great content, but between two pages of equal quality, the one with better experience scores will tend to rank higher.

For small businesses, this tiebreaker matters more than it does for large publishers. A plumbing company in Dublin and its three local competitors may publish broadly similar service pages. The one with a sub-2.5-second LCP and a CLS score below 0.1 is sitting on a structural advantage costing the others nothing to close, but few of them will.

The Most Common Failures on Small Business Sites

Most small business websites fail Core Web Vitals on LCP, and the cause is almost always the same: a large, uncompressed image sitting at the top of the page.

A photography studio in Nairobi uploads portfolio images directly from a camera at four megabytes each. The browser has to download the full image before it can display it. LCP climbs past five seconds, the page falls into the poor band, and the studio's competitor with a faster phone camera and a hosting plan compressing images on upload ranks above them for every relevant search in the city.

The second common failure is CLS caused by web fonts and third-party scripts loading after the initial render. A page using a custom typeface and pulling in a chat widget, a cookie banner, and a social media embed is stacking four separate layout-shift events before a visitor has read a word.

INP failures tend to appear on sites built with heavy JavaScript frameworks where the browser is still executing scripts when a visitor tries to interact. A Johannesburg-based e-commerce store running a large WooCommerce theme with twelve active plugins can produce INP scores above 600 milliseconds on a mid-range Android phone, which represents most of its actual visitors.

How to Check Your Core Web Vitals Scores

Google gives you two free tools, and they measure slightly different things. Understanding the difference stops you from chasing the wrong number.

Google Search Console shows your field data: real measurements collected from real visitors using the Chrome User Experience Report (CrUX). The Core Web Vitals report in Search Console groups your URLs into good, needing improvement, and poor, based on what your actual audience experienced over the past 28 days. This is the data Google uses for ranking. If your site is new or low-traffic, CrUX may not have enough data to populate the report.

PageSpeed Insights shows both field data (where available) and lab data: a simulated test run by Lighthouse under controlled conditions. Lab data is useful for diagnosing specific problems because it tells you what is causing a slow LCP or a high CLS score. The PageSpeed Insights tool is free and requires no account.

The Chrome User Experience Report documentation explains how the field data is collected and aggregated, which helps when you are trying to understand why your Search Console scores differ from your PageSpeed Insights scores. They are measuring the same signals in different ways, and both are worth reading.

Fixing LCP: The Highest-Priority Task

For most small business sites, closing the LCP gap is the single most valuable technical improvement available, because it is where the largest number of pages are failing by the widest margin.

The fix starts with images. Any image sitting in the first visible area of a page, what developers call the viewport, should be compressed, resized to its display dimensions, and served in a modern format such as WebP. A four-megabyte JPEG can become a 180-kilobyte WebP with no visible quality loss, and the LCP score drops accordingly. The web.dev guidance on LCP covers the full set of contributing factors, including render-blocking resources and slow server response times.

After images, slow hosting is the second most common LCP cause. A shared hosting plan in a data centre on a different continent from your visitors adds latency that no amount of image compression can fully offset. A Cape Town restaurant whose hosting sits on a server in Singapore is handing a measurable disadvantage to every local visitor before the page has started loading.

Moving to hosting with a server location closer to your main audience is not a glamorous fix, but it moves the LCP number more reliably than most plugin-based solutions.

CLS and INP: The Fixes Most Sites Overlook

CLS is fixable with two changes most developers can make in an afternoon, yet a large proportion of small business sites remain in the poor band for years because no one identifies it as the problem.

The first fix is reserving space for every element loading after the initial render. An image without declared width and height attributes in the HTML causes layout shift because the browser does not know how much space to hold until the image arrives. Adding those two attributes, or using CSS aspect-ratio containers, tells the browser the space dimensions in advance. The page stops jumping.

The second fix is loading web fonts with `font-display: optional` or `font-display: swap` in the CSS, and preloading the font files so they arrive before the first render rather than after it. A font swapping in after the initial text render is a reliable source of CLS on content-heavy pages.

INP improvements are more varied, but the most consistent gain on WordPress and similar CMS sites comes from reducing the number of third-party scripts executing on page load. Each analytics tag, marketing pixel, chat widget, and social share button runs JavaScript competing for the browser's main thread. A visitor trying to tap a navigation link while six scripts are still running gets an INP failure. Auditing and removing scripts you are no longer using is, in most cases, a faster win than rewriting theme code.

Speed is one ranking lever, and internal linking is the underrated one that spreads authority through your site.

Closing reflection on small wins that compound

Core Web Vitals feel like a technical problem because they come with numbers and thresholds. The underlying problem is simpler: a slow, unstable page frustrates visitors, and Google notices. The fixes are not glamorous. Compress the image, declare its dimensions, drop the scripts you are no longer using, and move to a hosting plan with servers near your audience.

None of those tasks require a developer on retainer. They require someone who knows what to look for and enough time to carry out the changes. The scores improve, the ranking signal improves, and your visitors get the experience your content was already worth.

You shouldn't have to guess which page-experience problem is costing you rankings. With Zahavah Studio you won't.

Contact Zahavah Studio to start a technical audit that identifies your Core Web Vitals failures and tells you exactly what to fix first.

There are questions arising every time someone starts working through Core Web Vitals scores, and most of them are about how much the signals matter relative to everything else going on in search.

Frequently Asked Questions

Do Core Web Vitals directly affect your rankings on every page?

Core Web Vitals apply at the URL level, not the domain level, so each page on your site has its own set of scores. A fast homepage does not compensate for a slow service page.

Google's Search Console Core Web Vitals report shows you which specific URLs are failing and groups them by issue type, which makes it possible to prioritise the pages likely generating the most traffic before working down through the rest. Pages with no field data, typically because they receive very little traffic, are not assessed in the ranking signal.

How much does a poor Core Web Vitals score affect rankings?

Google has stated consistently that Core Web Vitals act as a tiebreaker rather than a primary ranking signal. A page with genuinely helpful, authoritative content will outrank a fast but shallow page. In practice, the tiebreaker matters most in competitive local and service categories where multiple pages are broadly similar in content quality. A Manchester solicitor competing for the same queries as four other firms with comparable content and similar backlink profiles is in exactly the situation where a 0.8-second LCP advantage translates into a measurable ranking difference.

What is the difference between lab data and field data for Core Web Vitals?

Lab data, produced by tools like Lighthouse and PageSpeed Insights, simulates a page load under controlled conditions using a fixed device profile and network speed. Field data comes from real visitors using the Chrome browser, collected through the Chrome User Experience Report. Google uses field data for its ranking signal, not lab data.

Lab data is useful for diagnosing problems because it identifies what is slowing the page down. Field data tells you what real visitors on real devices and real connections are experiencing. The two numbers often differ, sometimes significantly, on mobile-heavy audiences.

Will fixing Core Web Vitals improve my conversion rate as well as rankings?

The evidence here points consistently in one direction. A Google and Deloitte study on mobile site speed found a 0.1-second improvement in mobile load time improved retail conversion rates by 8.4 percent. The mechanism is straightforward: a visitor waiting for a page to respond is a visitor whose attention is drifting.

Fixing LCP keeps more visitors on the page long enough to read it, and reducing CLS stops accidental taps on the wrong element during checkout or form completion. Ranking improvements and conversion improvements tend to arrive from the same set of fixes.

How often should I check my Core Web Vitals scores?

Google Search Console updates the Core Web Vitals report on a rolling 28-day basis, so checking monthly gives you a representative picture without over-reacting to short-term fluctuations. The most important time to check is immediately after a significant site change: a theme update, a new plugin, a redesign, or a new media-heavy page template.

Any of those can shift CLS or LCP scores substantially. Running PageSpeed Insights on a sample of your key pages before and after a deployment takes less than ten minutes and catches problems before they compound in the field data.

Everything on this blog is written to help you understand SEO, content strategy, and digital marketing. It is for information only. Nothing here is professional legal, financial, or technical advice. SEO results depend on your industry, your competition, and how search engines change over time. If you are making a significant business decision, speak to a qualified professional first. Zahavah Studio works hard to keep this content accurate and current, but is not liable for decisions made based on what you read here.

Leave a comment