If a page takes too long to feel usable, most visitors leave before they even see what it says. Core Web Vitals is Google’s attempt to measure that feeling with numbers, and it now plays a real, if modest, part in how your website ranks. Understanding what it actually measures — and what it doesn’t — makes it much easier to know where to spend your time when a site feels slow.
What Is Core Web Vitals?
Core Web Vitals is a set of three measurements Google uses to judge the real-world experience of loading and using a web page. Rather than testing a page in a lab under perfect conditions, Core Web Vitals is largely built from data collected from actual visitors using Chrome, which makes it a fairly honest picture of what people experience on your site. It sits inside a broader group of signals Google calls page experience, alongside things like mobile-friendliness and whether a page uses HTTPS, but Core Web Vitals is the part that’s genuinely measured rather than simply checked as present or absent.
LCP, CLS, and INP Explained
The three metrics are Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint. LCP measures how long it takes for the biggest visible element, usually a heading or hero image, to appear on screen. CLS measures how much the page jumps around while it loads. INP measures how quickly the page responds once someone actually clicks, taps, or types.
- LCP under 2.5 seconds is considered good
- CLS under 0.1 is considered good
- INP under 200 milliseconds is considered good
Why Core Web Vitals Is a Website Ranking Factor
Google has been public about wanting search results to reward pages that are pleasant to use, not just pages stuffed with the right keywords. Core Web Vitals became part of that picture because it’s measurable at scale, across billions of pages, without needing a human to judge each one.
How Google Uses Core Web Vitals in Search Rankings
In practice, Core Web Vitals behaves more like a tie-breaker than a primary ranking signal. If two pages answer a search query equally well, the one that loads faster and feels more stable is more likely to edge ahead. It rarely helps a poorly written page outrank a genuinely useful one, but it can quietly cost you position against a close competitor.
What Causes Poor Core Web Vitals Scores
Most Core Web Vitals problems trace back to a small number of causes, repeated across thousands of websites we’ve reviewed over the years.
Common Website Ranking Factor Speed Issues
- Oversized, uncompressed images loaded at full resolution on mobile
- Web fonts that swap in late and shift the whole layout
- Too many plugins or scripts loading on every single page
- Cheap or overcrowded hosting with slow server response times
- Pop-ups or cookie banners that push content down after it’s already rendered
How to Check Your Core Web Vitals Score
You don’t need to guess. Google’s PageSpeed Insights and Search Console’s Core Web Vitals report both show real, field-collected data for your own site, broken down by page and by device. Lab tools like Lighthouse are useful for debugging a specific problem, but the field data is what actually reflects your visitors’ experience and what influences ranking.
Tools for Testing Core Web Vitals
PageSpeed Insights is the simplest starting point since it shows both lab and field data side by side. Search Console’s report is better for spotting patterns across your whole site, since it groups similar pages together and flags which specific issue is dragging the score down.
Does Core Web Vitals Affect Mobile and Desktop Rankings Differently?
Google evaluates Core Web Vitals separately for mobile and desktop, and for most businesses, mobile is the version that actually decides your ranking, since Google primarily indexes and ranks based on the mobile version of a page. A site that scores well on a fast office desktop but poorly on an average phone over a patchy connection is still, in Google’s eyes, a poor experience.
Mobile Core Web Vitals Ranking Factor Speed Considerations
Mobile devices typically have less processing power and slower, less consistent networks than desktop machines, so the same page often performs worse on mobile even with identical code. This is why a Core Web Vitals check that only looks at desktop results can be misleading — it can show a passing score while the mobile experience, the one most visitors actually get, is quietly failing.
- Test mobile and desktop separately, not just one or the other
- Prioritise fixes that affect mobile first, since that’s usually the larger share of traffic
- Re-test after any theme, plugin, or page builder update, since these regularly reintroduce issues
Core Web Vitals Myths Worth Retiring
A few misconceptions come up often enough that they’re worth addressing directly, since believing them tends to lead to wasted effort in the wrong place.
Common Misunderstandings About This Website Ranking Factor
The first is assuming a perfect Core Web Vitals score guarantees a top ranking — it doesn’t; it’s one signal among many, and strong, relevant content will still outrank a technically faster page that doesn’t answer the search query as well. The second is assuming a single test result is reliable — field data is based on a rolling 28-day average of real visitors, so one good or bad test doesn’t tell the whole story. The third is assuming this is purely a developer’s problem — content decisions, like adding a large embedded video or an autoplaying carousel, affect these scores just as much as the underlying code.
Not sure where your site stands?
We can run a Core Web Vitals check across your site and tell you honestly what’s worth fixing first.
Get a Core Web Vitals CheckHow We Build Websites With Core Web Vitals in Mind
This isn’t something we bolt on at the end. Our website development process treats performance as a build requirement from the planning stage, not a fix-it-later task, which is a large part of why cheap web design ends up costing more once you factor in the traffic a slow site quietly loses. Every build goes through a staging environment and a Core Web Vitals check before it ever reaches production, so problems get caught while they’re still cheap to fix, not months after launch when they’ve already cost you rankings.
We also treat this the same way we treat AI visibility — the same instinct that makes a page fast for a human visitor tends to make it easier for AI search tools to read and cite it too. A bloated page with dozens of unnecessary scripts is slow for a person and difficult for a crawler to parse quickly, so the fix genuinely serves both audiences at once rather than being a trade-off between them.
Core Web Vitals FAQs
Core Web Vitals are three measurements Google uses to judge how a page feels to use: how fast the main content appears, how stable the layout is while loading, and how quickly the page responds when someone clicks or taps something.
Yes, it’s part of Google’s page experience signals, though content relevance still matters far more. Core Web Vitals tends to act as a tie-breaker between pages that are already well matched to a search query.
Google considers a page to be “good” when Largest Contentful Paint is under 2.5 seconds, Cumulative Layout Shift is under 0.1, and Interaction to Next Paint is under 200 milliseconds, measured from real visitor data.
The underlying metrics have changed a handful of times since launch, most notably when Interaction to Next Paint replaced First Input Delay. The thresholds themselves are reviewed periodically but don’t change often.
Some issues, like oversized images or too many active plugins, can be fixed without code. Layout shift and slow server response usually need someone who can look at the site’s actual build, not just its settings.
Website Design for Law Firms
Built for credibility, accessibility, and turning visitors into consultations.
