How Does Site Speed Affect Rankings?
Core Web Vitals aren't just a technical checkbox. Here's what LCP, INP, and CLS actually measure, why they affect both rankings and sales, and how to check yours free.
Site speed sounds like a technical afterthought, something for developers to worry about while everyone else focuses on content and keywords. That framing undersells it badly. Core Web Vitals are a genuine ranking factor, and more importantly, they measure something your customers feel directly every time they land on your site.
The three metrics, in plain language
- LCP (Largest Contentful Paint): how long it takes for the biggest, most prominent element on the page, usually a hero image or main heading, to fully load and appear. This is your visitor’s real first impression of speed.
- INP (Interaction to Next Paint): how quickly the page responds when someone actually clicks, taps, or types something. A page that looks loaded but feels sluggish to interact with fails here even if it scored well on initial load.
- CLS (Cumulative Layout Shift): how much the page visually jumps around as it loads. You’ve felt this yourself: you go to tap a button and an ad or image loads in above it, shifting everything down at the exact wrong moment. That’s what CLS measures.
Why this is a business number, not just a technical one
Amazon famously found that every 100 milliseconds of added latency cost them measurable sales. More broadly, pages loading within about 2 seconds see meaningfully lower bounce rates than pages taking 5 seconds or more. Slow doesn’t just rank worse. It loses the visitor before they ever get a chance to read your content, decide you’re credible, or convert.
Field data vs lab data: which one Google actually uses
This distinction trips people up constantly. Lab data comes from a controlled, simulated test, tools like Lighthouse running your page in one specific, artificial condition. Field data comes from the Chrome User Experience Report, real measurements from real visitors on real devices and connections. Google’s ranking systems use field data, because it reflects what actually happens to actual people using your site, not a single idealized test run. Lab data is still useful for diagnosing a specific problem, but don’t treat a good Lighthouse score as proof your Core Web Vitals are fine if your field data in Search Console says otherwise.
Where to check your own numbers, free
Search Console has a Core Web Vitals report built in, using your site’s real field data, grouped by URL and by which metric is failing. PageSpeed Insights gives you both lab and field data for any individual page, free, with specific flagged issues and suggested fixes. Neither requires a paid tool to start.
The most common, most fixable culprits
- Unoptimized images: large image files are the single most common cause of a poor LCP score. Compressing images and using modern formats fixes this quickly in most cases.
- Render-blocking scripts: JavaScript and CSS that load before the visible content, delaying everything behind them.
- Missing size attributes on images and ads: the browser doesn’t know how much space to reserve, so content jumps around as things load, hurting CLS.
- Heavy third-party scripts: chat widgets, ad networks, and tracking pixels that each add their own loading delay, often invisibly stacking up.
Where this sits relative to everything else
Perfect Core Web Vitals scores can’t rescue thin, low-quality content, and Google has said as much directly. Think of them as a tiebreaker: when two pages offer similar content quality and authority, the faster, more stable one gets the edge. That makes Core Web Vitals the price of entry in a competitive niche, not a replacement for the fundamentals covered elsewhere in this guide. Fix them, but don’t mistake a fast site for a finished SEO strategy.
