Most business owners know their website should be fast. Fewer know that Google has been formally measuring visitor experience since 2021 and incorporating those measurements into search rankings. Core Web Vitals are not a vague recommendation — they are specific, scored metrics, and your website either passes them or it does not.
This article explains what the three Core Web Vitals metrics actually measure, what scores are considered acceptable, what typically causes a website to fall short, and what steps you can take to bring your site into a passing range.
What Core Web Vitals Are
Core Web Vitals are a set of performance measurements that Google uses to assess whether a website provides a good experience to real visitors. The word “real” is worth noting: these metrics are collected from actual Chrome browser users through a dataset called the Chrome User Experience Report, not from synthetic tests run in controlled conditions. Your score reflects how your website actually performs for the people visiting it, on the devices and connections they are using.
There are currently three metrics in the Core Web Vitals set, each measuring a distinct aspect of the page experience: how quickly the main content appears, how responsive the page is to interaction, and how visually stable the layout is as it loads.
The Three Metrics Explained
Largest Contentful Paint (LCP) — perceived load speed
Largest Contentful Paint measures how long it takes for the largest visible element on the page to finish rendering. In practice this is usually the hero image, a large heading, or the main promotional block at the top of the page. It is the metric most closely aligned with the user’s perception of how fast the page loaded.
Google’s threshold for a passing LCP score is 2.5 seconds or under. A score between 2.5 and 4 seconds is rated as needing improvement, and anything above 4 seconds is considered poor. The most common causes of a slow LCP are large, unoptimised images; web fonts that block rendering; and slow server response times.
Interaction to Next Paint (INP) — responsiveness
Interaction to Next Paint replaced First Input Delay as a Core Web Vital in 2024 and provides a more complete picture of how responsive a page is. Where its predecessor only measured the first interaction a user made, INP measures the responsiveness of all interactions throughout the entire visit — clicks, taps, and keyboard inputs — and reports the worst-performing one.
A passing INP score is 200 milliseconds or under. Scores between 200 and 500 milliseconds need improvement, and anything above 500 milliseconds is poor. INP problems typically stem from JavaScript that runs on the main thread, blocking the browser from responding to user input promptly.
Cumulative Layout Shift (CLS) — visual stability
Cumulative Layout Shift measures how much the visible content of a page moves unexpectedly during loading. This is the metric that captures the experience of going to press a button and having it jump out from under you as an image loads above it, or text reformatting as a web font finishes downloading.
CLS is measured on a scale from zero (no unexpected movement) upward. A score of 0.1 or below passes. Between 0.1 and 0.25 needs improvement, and above 0.25 is poor. The most common causes are images and videos without declared dimensions, and content injected above existing page content after the initial load.
A website that shifts its layout as it loads, takes four seconds to show its main image, or freezes for half a second when you click a button is not providing a good experience. Google now measures all three of those things and adjusts rankings accordingly.
How Core Web Vitals Affect Search Rankings
Core Web Vitals became a ranking signal when Google rolled out what it called the Page Experience update. They do not override strong relevance signals; a page with outstanding content and poor Core Web Vitals will still rank above a fast page with thin, irrelevant content. What the metrics provide is a tiebreaker mechanism and a floor below which Google is less willing to surface a result regardless of how relevant it may be.
For competitive search categories — where many businesses are producing broadly similar content and competing for similar queries — the page experience signal becomes more consequential. A competitor whose website passes all three metrics and whose content is comparable to yours has a meaningful advantage.
The mobile weighting
Google’s Core Web Vitals assessment prioritises the mobile experience. This reflects the reality that the majority of web traffic for most businesses now comes from smartphones, and mobile networks and processing power vary considerably. A website that performs well on a desktop but poorly on a mid-range phone on a 4G connection will fail its Core Web Vitals assessment.
This is a common trap for businesses whose websites were designed and tested on fast desktop computers. What feels acceptably fast in that context may fail on the devices most of your prospective customers are actually using.
How to Check Your Current Score
Google provides a free tool called PageSpeed Insights, available at pagespeed.web.dev, which analyses any publicly accessible URL and returns both lab data (a simulated test) and, where available, real user data drawn from the Chrome User Experience Report. It is the most direct way to see your current Core Web Vitals standing.
The report separates mobile and desktop results. Check the mobile score first, as this is what Google weights most heavily. Each metric will show as Good, Needs Improvement, or Poor, and the report provides specific diagnostic information about what is contributing to each score.
Google Search Console also displays Core Web Vitals data in its Core Web Vitals report, aggregated across all the pages of your site with sufficient data. This view is useful for identifying whether problems are isolated to specific page types — product pages, for example — or are site-wide.
Common Causes and How to Address Them
Most Core Web Vitals failures fall into a small number of recurring categories. Understanding which category applies to your site points directly to the fix.
- Unoptimised images are the single most common cause of a poor LCP score. Serving images in a modern format such as WebP or AVIF, sizing them correctly for the screen they will appear on, and using the loading and fetchpriority HTML attributes to ensure the largest image loads as a priority are the primary remedies.
- Render-blocking resources — JavaScript and CSS files that load before the page can be displayed — delay LCP. Deferring non-critical scripts and inlining critical CSS reduces the time before a visitor sees anything at all.
- Slow server response times affect everything. If your hosting is inadequate for your traffic or your server is geographically distant from your visitors, the time before any content can begin rendering will be high regardless of how well the rest of the site is optimised.
- JavaScript that holds the main thread is the primary cause of a poor INP score. Removing or deferring unnecessary third-party scripts — tracking pixels, chatbots, and analytics tools that run on every page — is often the most effective improvement.
- Images and media without explicit width and height attributes shift the layout as they load, causing CLS failures. Declaring the dimensions of all visual content before it loads prevents the browser from having to recalculate the layout when the content arrives.
- Third-party embeds — booking widgets, social media feeds, and cookie consent banners — frequently inject content above the fold after the initial load, causing visible layout shifts. Either loading these elements after the page is stable or reserving space for them in advance addresses the problem.
The majority of Core Web Vitals failures on small business websites are caused by images that are too large, scripts that are too numerous, and hosting that is too slow. Addressing those three things resolves the problem in most cases.
What Good Scores Require in Practice
Passing Core Web Vitals is not an afterthought that can be addressed with a plugin or a single optimisation pass. It is the outcome of decisions made throughout the design and build process: how images are handled, how fonts are loaded, how JavaScript is managed, and what hosting environment the site runs on. A website built with performance as a secondary concern will require significant rework to pass; one built with performance as a primary concern typically passes without additional effort.
Modern frameworks such as Next.js make several of the technical requirements straightforward. Image optimisation, font loading strategies, and code splitting are handled in ways that directly benefit Core Web Vitals scores. A website built correctly on such a framework starts from a much stronger position than one relying on generic page builders or unoptimised templates.
The hosting question
Hosting is frequently overlooked in conversations about website performance, but it has a direct impact on Core Web Vitals. A server that responds slowly to requests — because it is overloaded, geographically distant, or simply underpowered — introduces a delay that no amount of front-end optimisation can fully compensate for. For UK businesses targeting UK visitors, hosting should be on infrastructure with UK or European edge locations that serve pages from a data centre close to the visitor.
Shared hosting plans at the lower end of the market frequently perform poorly on this measure. The cost difference between entry-level shared hosting and a well-configured, faster alternative is modest relative to the impact on performance and therefore on rankings and user experience.
The Practical Takeaway
Core Web Vitals are a measurable, objective assessment of whether your website does its job well at a technical level. They are not an abstract concept but three specific numbers that Google checks against three specific thresholds, using data from real visitors to your site. If your website fails them, that failure is visible to Google and it influences where your pages appear in search results.
For small businesses that rely on organic search to attract enquiries, the practical stakes are meaningful. A website that passes Core Web Vitals and presents good content starts from an honest competitive position. One that fails them is asking Google to overlook a set of verified shortcomings, and Google is less inclined to do so with each update to its ranking systems.
At Bright Eye Digital, performance is built into every website we produce rather than optimised as an afterthought. If you would like us to assess your current site or discuss what a better-performing build might look like for your business, we would be glad to hear from you.