Core Web Vitals: How Site Speed Affects Your Rankings
Core Web Vitals turn "the site feels slow" into three numbers Google can measure — and act on. Here is what they are, why they matter for SEO, and how to actually improve them.
What Core Web Vitals actually measure
Core Web Vitals are three metrics Google uses to put a number on how a page feels to a real user: how fast the main content appears, how quickly the page responds to interaction, and how much the layout jumps around while loading. They are part of Google's page-experience signals, so they influence both rankings and, more directly, whether visitors stay.
Crucially, they are measured from real visitors' devices and connections, not a lab. A site that feels fine on your office fibre can fail on a mid-range phone on mobile data — which is exactly the visitor most Irish businesses cannot afford to lose.
The three metrics, in plain English
Hit all three and you have a page that loads quickly, responds instantly and stays visually stable — the experience people quietly expect and loudly abandon when they do not get it.
| Metric | What it measures | Good target |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | Under 2.5s |
| INP (Interaction to Next Paint) | How quickly the page responds to input | Under 200ms |
| CLS (Cumulative Layout Shift) | How much the layout unexpectedly moves | Under 0.1 |
Why this is an SEO issue, not just a tech one
Google has been explicit that page experience is a ranking factor. It rarely overrides genuinely better content, but when two pages are close on relevance, the faster, more stable one has the edge — and speed compounds with everything else, because slow pages get fewer conversions and more bounces regardless of where they rank.
There is a second, blunter reason: your competitors are improving. Core Web Vitals are a moving benchmark, and standing still means slipping back.
The fixes that move the needle
Most real-world gains come from a short list of causes:
- Oversized images — serve modern formats (AVIF/WebP), set explicit width and height, and never ship a photo far larger than it renders.
- Render-blocking scripts and styles — defer non-critical JavaScript and CSS so content paints first.
- Layout shift — reserve space for images, ads and embeds so nothing jumps as it loads.
- Heavy third-party scripts — audit analytics, chat widgets and trackers; load them async and only where needed.
- Slow hosting or no caching — a good host and sensible caching often deliver the single biggest LCP win.
How to measure it honestly
Use field data, not just lab tools. Google's own reports show what real visitors experienced over the last 28 days, which is what actually feeds rankings — a one-off lab score can look great while real users on slower devices struggle.
Fix the biggest offender first, remeasure, then move to the next. Chasing a perfect score everywhere is a poor use of budget; getting every important page comfortably into the green is the goal.
FAQ
Do Core Web Vitals really affect Google rankings?
Yes — they are part of Google's page-experience signals. They rarely outrank genuinely better content, but among similar pages the faster, more stable one has an advantage, and speed also lifts conversions regardless of ranking.
What is a good Core Web Vitals score?
Aim for LCP under 2.5s, INP under 200ms and CLS under 0.1, measured from real visitors. Passing all three on your important pages is the practical target.
Why does my site pass in one tool but fail in another?
Lab tools test a single simulated visit; field data reflects real visitors on real devices and connections. Field data is what feeds rankings, so trust it over a one-off lab score.
What usually causes a slow site?
Most often oversized images, render-blocking scripts, layout shift from unsized elements, heavy third-party widgets, or slow hosting with no caching. Fixing the biggest offender first gives the fastest win.