Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how quickly the main content appears, how quickly the page reacts when you tap something, and how much the layout jumps about while loading. Your site is fast enough, by Google’s definition, when at least 75% of visits score “good” on all three.
They do affect Google rankings, though less than many agencies suggest. The stronger reason to care is that a slow, jumpy page loses customers before they have read a word.
- The targets are 2.5 seconds for loading (LCP), 200 milliseconds for responsiveness (INP) and 0.1 for layout stability (CLS).
- INP replaced the older FID measurement in March 2024. The three metrics and their thresholds have not changed since.
- Test for free with PageSpeed Insights, and trust the real-user section over the 0 to 100 score.
- Google’s Chrome team says 40% of sites in its real-user data miss the loading target, and about a quarter miss the layout one.
What LCP, INP and CLS measure
| Metric | In plain English | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the biggest thing on screen, usually the main image or headline, has appeared | 2.5 seconds or less | More than 4 seconds |
| Interaction to Next Paint (INP) | How long the page takes to respond visibly when someone taps, clicks or types | 200 milliseconds or less | More than 500 milliseconds |
| Cumulative Layout Shift (CLS) | How much the content moves around unexpectedly as the page loads | 0.1 or less | More than 0.25 |
Anything between good and poor is labelled “needs improvement”. These thresholds come from Google’s web.dev documentation, and they are judged at the 75th percentile of visits, with mobile and desktop assessed separately. In other words, three out of four visits have to be good. One fast load on your office broadband proves nothing.
CLS is the one people recognise once it is described. You go to tap “Add to basket”, an image finishes loading above it, everything shifts down and you tap an advert instead. That is a layout shift.
If you have read older guides mentioning First Input Delay (FID), that has gone. Google formally made INP a Core Web Vital in March 2024, replacing FID. Google describes INP as a more comprehensive measure of responsiveness than the one it replaced. Its documentation lists all three current metrics as stable and says stable metrics won’t change more than once a year. As of November 2026 the set is the same.
How many websites pass?
Fewer than you might hope. Google’s Chrome team, in its web.dev guide to the most effective fixes, says 40% of sites in the Chrome UX Report (real data from Chrome users) don’t meet the recommended LCP threshold, and about a quarter don’t meet the CLS one. Loading speed is the one most sites trip over.
Source: Google web.dev, The most effective ways to improve Core Web Vitals
We looked for a current, checkable pass rate for UK websites broken down by platform and could not confirm one, so we haven’t quoted a figure. What we can say from building and fixing sites is that the platform matters less than how it is set up.
WordPress is not slow by nature. Hosted builders control the hosting, the theme and what you are allowed to add, so there are fewer ways to make a mess. WordPress hands you the keys. A well-built WordPress site on decent hosting can pass comfortably. When one fails, the usual suspects are cheap hosting, a heavy theme and too many plugins. We compare the two main shop platforms in Shopify or WooCommerce.
How to test your own site
Step 1 of 5
Run PSI
Enter a key page at pagespeed.web.dev and read the real-user assessment first.
Step 2 of 5
Check Console
Open the Core Web Vitals report in Search Console to see which page groups fail.
Step 3 of 5
Fix loading
Compress the main image, stop lazy-loading it and turn on caching.
Step 4 of 5
Trim scripts
Remove unused plugins, apps and tags, and delay chat and marketing scripts.
Step 5 of 5
Recheck
Wait 28 days for field data to update before judging the fix.
You need two free tools, both from Google.
PageSpeed Insights
Go to pagespeed.web.dev, enter a page address and look at the top section first. This is field data: what real Chrome users experienced over the previous 28-day collection period, with a pass or fail for the Core Web Vitals assessment. If the page hasn’t had enough visitors, the tool falls back to figures for your whole site. A very quiet site may show no real-user data at all.
Below that is the lab test and the familiar score out of 100, where Google counts 90 or above as good. Lab data is a single simulated load. Google describes it as useful for debugging but says it “may not capture real-world bottlenecks”. So a score of 60 with a passing field assessment is fine, and a score of 95 with a failing one is not. The lab test also can’t measure INP, since nobody is clicking.
Search Console
The Core Web Vitals report in Google Search Console groups all your pages into good, needs improvement and poor, using the same real-user data. It is the quickest way to spot that, say, every product page is failing while the homepage passes.
Because field data covers a 28-day window, a fix takes about a month to show fully. Check again after four weeks before deciding whether it worked.
How much do Core Web Vitals affect Google ranking?
Google’s page experience documentation says “Core Web Vitals are used by our ranking systems”, and its Core Web Vitals page recommends achieving good scores “for success with Search”. It then tempers this twice. Good results don’t guarantee top rankings, and Google “always seeks to show the most relevant content, even if the page experience is sub-par”.
Our reading: relevance and quality decide most rankings, and speed separates pages that are otherwise close. If your site is failing badly, fix it. If it already passes, shaving another 200 milliseconds won’t move you up, and the budget is better spent on content or on the things in our guide to how long SEO takes.
Google also lists page experience among the basics worth keeping up for its AI search features, which we cover in what AI Overviews mean for UK websites.
Common fixes for WordPress and Shopify sites
Slow loading (LCP)
According to the 2024 Web Almanac, cited by Google’s Chrome team, 73% of mobile pages have an image as their largest element. So start with the main image.
- Resize and compress the hero image and serve a modern format such as WebP. A banner photo uploaded straight from a camera is a typical culprit.
- Don’t lazy-load the main image. Lazy loading suits images further down the page, and applied to the top one it delays the very thing being measured.
- Replace homepage sliders with a single image.
- On WordPress, pay for decent hosting and turn on page caching. Google’s Chrome team also recommends a content delivery network to cut server response time.
- On Shopify, the hosting is handled, so look at the theme and at how many apps load scripts on every page.
Sluggish response (INP)
The usual cause is too much JavaScript. Chat widgets, pop-ups, review carousels, analytics tags and tracking pixels each add work for the browser.
- Audit plugins and apps, and remove what you don’t use. Each one you keep should earn its place.
- Load chat and marketing scripts after the page is usable, or only once a visitor has given consent. A properly set up consent tool helps here, and our post on cookie banner rules explains what it must do anyway.
- Be wary of heavy page builders stacked on heavy themes.
Jumping layout (CLS)
- Give every image and video a set width and height so the browser reserves the space. The Web Almanac found 66% of pages had at least one image without them.
- Reserve space for cookie banners, announcement bars and embedded content so they don’t push the page down when they arrive.
- Keep web fonts to one or two families so text doesn’t reflow when they load.
If the theme itself is the problem, patching has limits. A rebuild on a lighter theme is sometimes cheaper than months of tuning, and our guide to what a website costs in the UK sets out what drives the price.
Common questions
My PageSpeed score is 45. Should I panic?
No. Look at the Core Web Vitals assessment above it. If real users are getting good scores, the lab number is a to-do list, not an emergency.
PageSpeed Insights shows no real-user data for my site. What now?
It means too few Chrome users have visited for a reliable sample. Use the lab results as a guide and test on an ordinary phone over mobile data.
If your site is failing and you would like to know whether to fix or rebuild, our websites team can run the tests and tell you straight.
Sources
- Google web.dev: Web Vitals (last updated 31 October 2024)
- Google web.dev: How the Core Web Vitals metrics thresholds were defined (last updated 7 May 2025)
- Google web.dev: Interaction to Next Paint is officially a Core Web Vital (12 March 2024)
- Google web.dev: The most effective ways to improve Core Web Vitals (last updated 31 October 2024)
- Google Search Central: Understanding page experience in Google Search results (accessed November 2026)
- Google Search Central: Understanding Core Web Vitals and Google search results (last updated 10 December 2025)
- Google for Developers: About PageSpeed Insights (accessed November 2026)
- Google Search Central: AI features and your website (last updated 10 December 2025)
- HTTP Archive: Technology Report, Core Web Vitals by technology, United Kingdom, mobile (October 2026)