Core Web Vitals Are a Tiebreaker Not a Ranking Factor

A client called me last fall convinced he had found the reason his traffic dropped. Every URL on his site passed Core Web Vitals. Green scores across the board in Search Console, mobile and desktop. He had spent two months and a real chunk of his budget getting there, and his rankings had still slid after a core update. He wanted to know what was left to fix on the performance side. The honest answer was nothing. Performance was never the problem. He had optimized the one part of his site that Google treats as a tiebreaker and left the parts that actually decide who ranks untouched. I watch some version of this play out every few months, and it almost always starts with someone treating Core Web Vitals like a ranking lever instead of what they are.

What core web vitals actually are

Core Web Vitals are three metrics Google uses to measure real user experience: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A page passes Core Web Vitals when 75 percent of real Chrome visits hit the good thresholds, meaning an LCP under 2.5 seconds, an INP under 200 milliseconds, and a CLS under 0.1.

That is the whole definition, and what it leaves out is the interesting part. Nothing about content. Nothing about links. Nothing about whether your page answers the question someone searched. Core Web Vitals measure how a page feels to load and use, and that is the entire job. Google bundles the three metrics under a wider idea it calls page experience, which also folds in HTTPS and mobile friendliness. But the metrics themselves are a performance score, not a quality score, and Google has been consistent that one does not substitute for the other.

But the metrics themselves are a performance score, not a quality score, and Google has been consistent that one does not substitute for the other.

Are core web vitals a ranking factor or just a tiebreaker

Core Web Vitals are a confirmed ranking factor, and the confusion starts the moment you ask how much that admission is actually worth. Google says as much in its own documentation on Core Web Vitals and search results, where the careful wording is that good vitals align "with what our core ranking systems seek to reward." Read that line twice, because it is doing a lot of quiet work. It does not say Core Web Vitals rank your page. It says they align with what the ranking systems already reward, which is a far softer claim than the one most SEO blogs repeat.

When the page experience update first rolled out, Google framed it plainly as a tiebreaker. The guidance said that when many pages are similar in relevance, page experience can become much more important for visibility. That is tiebreaker language, in writing, from Google. John Mueller later pushed back on the pure tiebreaker label, saying Core Web Vitals are "more than a tie-breaker, but it also doesn't replace relevance," and that being faster than a competitor "doesn't necessarily mean that you will jump to position number one." So Google's own position nets out to this: yes it counts, no it will not rescue weak content, and relevance still towers over it. On every site I have audited, that adds up to tiebreaker behavior. Core Web Vitals move the needle when everything else is close, and they sit on the bench when it is not.

Why page experience is a signal not a ranking system

The detail almost nobody mentions is that Google quietly demoted the whole apparatus. In April 2023, Google page experience removed from ranking systems. Danny Sullivan explained that page experience was never a ranking "system" at all, it is a ranking "signal" that other systems use. That is not a cosmetic rewrite. A system is machinery that scores and orders pages. A signal is an input the machinery reads. Core Web Vitals are an input.

This matters because it tells you where the weight actually sits. Core Web Vitals feed the core ranking systems the same way many other inputs do, and those systems are overwhelmingly built around relevance and authority. If you want to understand how Google decides a site is worth trusting before it ever weighs a tenth of a second of layout shift, that work happens in the domain-level scoring I broke down earlier, and a fast page does not buy you a seat at that table. A good vitals score is a tie-breaking input applied after the systems have already decided your page belongs in the conversation.

The three metrics and the thresholds that actually matter

People talk about Core Web Vitals like a single grade. They are three separate metrics, each measuring a different slice of the user experience, and each with its own threshold. You have to pass all three at the 75th percentile of real visits before Google calls a page good. That percentile detail trips up most site owners. You are not graded on your best day or your fastest device. You pass only when three quarters of your actual users, on the phones and networks they really use, clear the threshold. Core Web Vitals only score real user experience, never a lab simulation.

Largest Contentful Paint (LCP) measures loading

Largest Contentful Paint marks when the largest piece of content, usually a hero image or a headline block, finishes loading for the user. Good LCP is under 2.5 seconds. Slow server response, render-blocking JavaScript, and oversized images are the usual loading culprits, and a content delivery network plus compressed images fixes most of it.

Interaction to Next Paint (INP) measures responsiveness

Interaction to Next Paint measures how fast the page reacts to every interaction a user makes in a session, every tap, click, and keypress, and a good INP is under 200 milliseconds. INP replaced First Input Delay in March 2024 because FID only judged the first interaction and let sluggish pages look fine. Heavy JavaScript on the main thread is what wrecks the responsiveness real users feel.

Cumulative Layout Shift (CLS) measures visual stability

Cumulative Layout Shift scores how much the layout jumps while the page loads, the visual stability a user notices when a button slides under their thumb. Good CLS is 0.1 or less. The fix is dull and reliable: set explicit width and height on images and reserve space for ads and embeds so nothing shoves your content down half a second after it appears. None of this is mysterious, which is exactly why Core Web Vitals make a poor place to spend your ranking budget.

Taken together, LCP, INP, and CLS are Google's attempt to put a number on user experience: how fast the main content paints, how quickly the page answers a user, and how steady it stays under them. None of the three metrics touches whether your content is any good. A perfect Largest Contentful Paint on a page nobody wants to read still ranks like a page nobody wants to read.

How to measure core web vitals without fooling yourself

The fastest way to waste a week is to chase a Lighthouse score. Whether your weak spot is LCP, INP, or CLS, you cannot improve the metrics you are measuring in the wrong place. Lighthouse and the lab data in PageSpeed Insights run a simulation on one machine under controlled conditions. That is fine for debugging, but it is not what Google ranks on. Google ranks on field data, the real Chrome User Experience Report numbers gathered from the actual users visiting your site. You can have a 100 lab score and still fail Core Web Vitals in the field because your real users are on mid-range phones and congested networks, and their loading experience is the only one that counts toward search.

Trust the field data. The Core Web Vitals report in Google Search Console groups your URLs by status from real CrUX data and is the closest thing to what Google sees. Use PageSpeed Insights for the field reading on a specific URL, then drop into Lighthouse or Chrome DevTools only to diagnose the cause. This is the kind of distinction between what gets measured and what gets ranked that runs through all of what technical SEO actually means once you stop chasing scores and start reading the right number.

When core web vitals are worth fixing and when they are not

The business case for Core Web Vitals is stronger than the ranking case, because a faster and steadier page is a better user experience whether or not it ever moves you in search, and that is the honest way to sell the work. Google's own figures say users are 24% less likely to abandon pages. Separate bounce rates climb with load time. Those are conversion and revenue numbers, not ranking numbers, and they are the real reason to care.

Less likely to abandon (Core Web Vitals)24 percent

Bounce rate increase (1-3s load)32 percent

Bounce rate increase (6s load)106 percent

Source: Google

So here is how I prioritize it. If a page is already competitive on relevance and authority and is stuck just outside where it should sit in the search results, Core Web Vitals are worth fixing, because that is the exact tiebreaker scenario where the signal earns its keep. If a page is not ranking because the content is thinner than the competition or the site has no link equity reaching it, a faster LCP changes nothing, and the effort belongs in how authority actually flows through your internal links instead. I have watched sites pass Core Web Vitals on every URL and lose rankings anyway, and I have watched pages with a mediocre CLS hold the top spot for months because nothing else came close on relevance. The score is a tenth-place tiebreaker, and you only reach for it once the first nine places are settled. When performance genuinely is the bottleneck, that is the point to bring in real technical SEO rather than running another Lighthouse pass.

Core web vitals are a tiebreaker so treat them like one

The reason this matters is opportunity cost. Every hour you spend shaving 300 milliseconds off an already-passing page is an hour not spent on the content depth and links that move rankings far more. Core Web Vitals deserve a place in your process. They do not deserve the front of the line. Get them into the good range, keep them there, and move on to the work that actually decides who ranks. That ordering, performance as a finishing touch rather than the foundation, is the same discipline behind the Nashville SEO playbook I run every engagement on. Treat Core Web Vitals as the tiebreaker Google built them to be, and stop letting a green score convince you the hard work is done.

By Michael McDougald