Core Web Vitals and SEO: How Page Speed Affects Your Rankings
Core Web Vitals are a set of standardised performance metrics that Google uses to measure the real-world user experience of a web page — specifically how fast it loads, how stable its layout is, and how quickly it responds to user input. Since Google made Core Web Vitals an official ranking signal, poor scores can directly suppress a page’s position in search results regardless of content quality.
Understanding what each metric measures and how to improve it is a practical requirement for any serious SEO programme.
The Three Core Web Vitals Metrics
Largest Contentful Paint (LCP)
LCP measures how long it takes for the largest visible element on the page — typically a hero image, a banner, or a large heading block — to become fully visible in the viewport. Google’s target is an LCP of 2.5 seconds or faster from the moment the page begins loading.
A slow LCP is most commonly caused by unoptimised or oversized images, render-blocking JavaScript or CSS that delays the page from displaying content, slow server response times, and third-party scripts loading before critical content.
Cumulative Layout Shift (CLS)
CLS measures how much the visible content of a page shifts unexpectedly during loading. When images without specified dimensions load and push text down, when fonts load and cause reflow, or when late-loading ads inject into the layout, the result is a high CLS score. Google’s target is a CLS score below 0.1.
Layout instability is a poor user experience — content jumps away from where the user is reading or a button they were about to click moves. Google quantifies this instability and factors it into ranking.
Interaction to Next Paint (INP)
INP replaced First Input Delay (FID) as the responsiveness metric in March 2024. It measures how quickly a page responds visually to all user interactions — clicks, taps, and keyboard input — throughout the full duration of a visit. Google’s target is an INP below 200 milliseconds.
A high INP is most commonly caused by excessive JavaScript execution on the main thread, which blocks the browser from responding to user actions. Heavy third-party scripts — advertising systems, chat widgets, tag managers — are frequent contributors.
Why Core Web Vitals Are an SEO Priority
Google’s Page Experience signal combines Core Web Vitals with mobile-friendliness and HTTPS as inputs to its ranking systems. Google has been explicit that pages meeting the Core Web Vitals thresholds have a ranking advantage, though content relevance and authority remain primary ranking factors.
In practice, this means that in closely competitive search results — where multiple pages have similar content quality and link profiles — Core Web Vitals differences can be the tiebreaker. As the web progressively improves in performance, the threshold for acceptable scores rises.
Beyond rankings, slow and unstable pages reduce conversion rates. Users leave pages that take more than a few seconds to load. Improving Core Web Vitals typically improves both search visibility and the rate at which visitors convert into enquiries.
How to Diagnose Your Core Web Vitals
Google provides two categories of data: lab data (simulated measurements from a controlled environment, available immediately for any URL) and field data (real-user measurements collected from Chrome users visiting your pages, available after sufficient traffic accumulates).
For assessment, use:
Google Search Console’s Core Web Vitals report provides field data segmented by mobile and desktop, with URLs grouped by issue type. PageSpeed Insights (pagespeed.web.dev) provides both lab and field data for individual URLs with specific recommendations. Chrome DevTools’ Performance panel allows detailed profiling of exactly which scripts, resources, and rendering sequences are causing performance issues.
Prioritise field data over lab data when both are available — field data reflects actual user experience conditions including real device and network performance distributions.
Practical Fixes for Each Metric
Improving LCP
Serve images in modern formats (WebP or AVIF) at the correct display size. Add the loading=”eager” and fetchpriority=”high” attributes to the LCP image element so the browser prioritises it. Eliminate render-blocking scripts by deferring non-critical JavaScript. Use a fast hosting environment with low server response times. Implement a content delivery network (CDN) for static assets.
Improving CLS
Always specify width and height attributes on all images and video embeds. Use CSS aspect-ratio containers to reserve space before media loads. Avoid injecting content above existing content after the page has loaded. Load custom fonts with font-display: swap and, where possible, preload critical font files.
Improving INP
Audit and reduce the volume of JavaScript executing on the main thread. Defer or remove third-party scripts that are not critical to the user journey. Break up long tasks (tasks exceeding fifty milliseconds) using scheduler.postTask or setTimeout patterns. Review tag manager implementations — uncontrolled tag deployments are a common source of INP regressions.
Core Web Vitals in the Context of Technical SEO
Core Web Vitals are a component of technical SEO, not a standalone concern. They should be reviewed as part of a comprehensive technical SEO audit alongside crawlability, indexation, structured data, and mobile usability. Improving performance in isolation without addressing other technical issues produces limited ranking gains.
For the full scope of technical and on-page SEO work that supports strong rankings, see our guide to on-page SEO and our professional SEO services.
Technical performance issues — including slow crawl response times caused by a disorganised robots.txt — can compound Core Web Vitals problems. Generate a clean robots.txt to ensure crawlers are not wasting budget on non-essential resources:
Place robots.txt at your domain root, e.g. https://example.com/robots.txt. Test it with Google's robots.txt tester.
If your Core Web Vitals report in Google Search Console is showing poor or needs improvement scores across multiple pages, a technical SEO engagement can identify and prioritise the specific causes. We can assess your site’s performance profile and deliver a prioritised fix list alongside the full SEO programme.
Chat on WhatsAppFrequently asked questions
Are Core Web Vitals the most important SEO ranking factor?
No. Content relevance, topical authority, and backlink quality remain the primary ranking factors. Core Web Vitals are a tiebreaker signal within Google’s Page Experience framework. A page with genuinely useful, well-linked content will outrank a faster competitor on a weaker topic. However, for pages competing closely on content and authority, Core Web Vitals differences are meaningful.
How do I check my Core Web Vitals scores?
Google Search Console provides aggregated field data for your site in the Core Web Vitals report under Experience. For individual page analysis, use PageSpeed Insights at pagespeed.web.dev, which provides both lab scores and field data where available. The Chrome browser’s DevTools Performance panel provides granular analysis of what is causing slowness at a technical level.
What is a passing Core Web Vitals score?
Google’s thresholds are: LCP at or below 2.5 seconds (good), between 2.5 and 4 seconds (needs improvement), above 4 seconds (poor). CLS at or below 0.1 (good), between 0.1 and 0.25 (needs improvement), above 0.25 (poor). INP at or below 200 milliseconds (good), between 200 and 500 milliseconds (needs improvement), above 500 milliseconds (poor).
Does website hosting affect Core Web Vitals?
Yes, significantly. Server response time (Time to First Byte, or TTFB) directly affects LCP. Shared hosting environments with slow response times set a performance ceiling that no amount of front-end optimisation can fully overcome. Upgrading to managed hosting with a fast underlying infrastructure, combined with a CDN for static assets, is one of the highest-leverage investments for LCP improvement.
My Core Web Vitals are good in PageSpeed Insights but poor in Search Console — why?
PageSpeed Insights measures lab data from a simulated environment using a standardised device and network profile. Search Console uses field data — real measurements from actual users on their real devices and connections. If your real users are on slower mobile connections or lower-end devices, field scores will be lower than lab scores. Prioritise Search Console field data as the more accurate representation of actual user experience.