Core Web Vitals Explained: Why Google Rewards Fast Websites
In 2021, Google started using page experience signals (specifically Core Web Vitals) as direct ranking factors. That means your site's speed and stability aren't just user experience issues. They're SEO issues. Here's what each metric measures, what counts as a good score, and how to fix common problems without needing a developer.
The Three Core Web Vitals
LCP measures how long it takes for the largest visible element (usually a hero image or headline) to render. It's the most important of the three because it directly correlates with how fast the page feels. The most common culprit is a large, unoptimised hero image loading from a slow server.
CLS measures how much the visible content shifts position while loading. You've experienced this when you go to tap a button and an image loads above it, moving everything down, and you accidentally tap the wrong thing. Google penalises this because it creates a bad, unstable experience. The usual cause is images without defined dimensions, or ads that load late and push content down.
INP (which replaced FID in 2024) measures how long it takes for the page to visually respond after a user interacts with it, tapping a button, expanding a menu, submitting a form. A page with a high INP feels laggy and unresponsive. Heavy JavaScript that blocks the main thread is almost always the cause.
How to Check Your Current Scores
The fastest way: go to pagespeed.web.dev, enter your URL, and check the Mobile tab. It'll give you a score out of 100 and flag which specific metrics are failing.
For real-world data (from actual users, not a lab test), check Search Console → Core Web Vitals report. This shows you how your pages actually perform for visitors over the past 28 days.
The Most Common Fixes
For a slow LCP, the most effective fix is converting your hero image to WebP or AVIF format and adding fetchpriority="high" to the image tag so the browser prioritises loading it. Serving images through a CDN rather than your origin server also makes a significant difference.
High CLS is almost always caused by images without defined dimensions. Add explicit width and height attributes to every image so the browser reserves the space before the image loads, no more content jumping around as the page fills in.
Poor INP comes down to JavaScript. Audit your JS bundles, remove anything unused, and defer scripts that aren't needed on initial load. If you have heavy calculations happening, move them off the main thread. And if you're on shared hosting, switching to a CDN-based platform like Vercel or Cloudflare Pages often improves all three scores at once, without touching a single line of code.
Quick win: Simply compressing your images with a tool like Squoosh (free, browser-based) and re-exporting them as WebP can move your LCP score from Poor to Good without touching any code.
Does It Actually Affect Rankings?
Yes, but it's one signal among many. A site with excellent Core Web Vitals but thin content won't outrank a slow site with genuinely authoritative content. Google has been clear that page experience is a tiebreaker, not a trump card.
What it does meaningfully affect is bounce rate. A slow site that frustrates visitors into leaving immediately signals to Google that the site isn't serving users well, and that signal compounds over time. Fast sites keep people engaged, and engagement signals do move rankings.
Want better Core Web Vitals scores?
We build sites that score 90+ on PageSpeed out of the box. And if your current site is underperforming, we'll tell you exactly what's dragging your scores down, for free.
Get a free performance audit