Google introduced Core Web Vitals in 2021 and made them a ranking signal. Since then, the term has floated around the SEO world in a way that makes it sound either catastrophically important or impossibly technical, depending on who you're reading.
The actual concept is simpler than the jargon suggests.
What Google is trying to measure
Google's business model depends on sending people to good web pages. If users consistently click search results that load slowly, shift around as they're reading, or feel unresponsive to taps and clicks, those users trust Google less and use it less.
Core Web Vitals are Google's attempt to quantify "is this page annoying to use?" into three measurable numbers. Each one corresponds to a specific frustration.
The three metrics
Largest Contentful Paint (LCP) — how fast it loads
LCP measures how long it takes for the main visible content of the page to appear — usually the hero image or the headline. Google considers anything under 2.5 seconds good. Over 4 seconds is poor.
A page that takes five seconds to show its main content loses around 25% of visitors before it finishes loading. Those visitors hit back and click the next result, which tells Google this page wasn't satisfying.
Interaction to Next Paint (INP) — how fast it responds
INP measures how fast the page reacts when a user clicks or taps something. Under 200 milliseconds is good. Over 500 milliseconds is poor.
Think of the form that takes a second to register your tap, the menu that hesitates before opening, the button you have to press twice. These interactions don't feel broken to the developer who built them on a fast machine — they feel broken to the person using a three-year-old phone on a mid-range connection.
Cumulative Layout Shift (CLS) — how much it jumps around
CLS measures how much the page layout moves while loading. Images loading in and pushing text down. A cookie banner appearing over the button you were about to click. Ads loading and shifting everything else.
Google considers a CLS score under 0.1 good. It's a dimensionless number rather than a time measurement, because it's measuring visual displacement — how far content travels from where you first saw it.
What scores should you be targeting?
Good: LCP under 2.5s, INP under 200ms, CLS under 0.1. Needs improvement: LCP 2.5–4s, INP 200–500ms, CLS 0.1–0.25. Poor: beyond those ranges.
Check yours at pagespeed.web.dev. The mobile score matters more than desktop — Google indexes the mobile version of your site first.
What actually moves the needle
For most small business websites, the biggest gains come from three places:
Image optimisation. Uncompressed images are the most common cause of poor LCP. A hero image that's 3MB should be under 300KB. Compress everything, serve in WebP format, and specify dimensions in your HTML.
Reducing layout shift. Specify image dimensions. Load fonts early. Set aside space for ads or embeds before they load. These prevent elements from jumping when the page finishes loading.
Faster hosting. Your server response time is LCP's foundation. A shared hosting server that takes 800ms just to respond will never have a good LCP score regardless of what else you optimise.
None of this requires rebuilding your website. But it does require someone to actually check the scores and work through the list systematically.
Frequently asked questions
How do I check my Core Web Vitals score?
Go to pagespeed.web.dev, enter your URL, and click Analyze. Google runs your page through their real-world performance measurement and gives you scores for each metric. Run it on your mobile version — that's the one Google uses for ranking.
Does a poor Core Web Vitals score directly hurt my Google ranking?
Yes, as a tiebreaker signal. If two pages are equally relevant for a search query, the one with better Core Web Vitals scores ranks higher. It's not the primary ranking factor — content relevance still matters most — but for competitive terms, it can be the difference.
What's the most common cause of a poor LCP score?
Unoptimised images. A hero image that's 3MB instead of 300KB is the most common culprit. Compress your images, serve them in modern formats (WebP), and specify width and height attributes so the browser knows how much space to reserve.
Can I fix Core Web Vitals without a developer?
Some fixes are straightforward without technical knowledge — compressing images, removing unused plugins on WordPress, switching to faster hosting. Others (server response time, JavaScript optimisation, render-blocking resources) require developer involvement.
Yash
Founder & Principal Consultant, Ynexgen
Yash leads Ynexgen, helping small and mid-sized businesses turn technology into a stronger foundation for growth — 7+ years across Salesforce CRM, websites, and AI adoption.
