Do you see red or orange scores in PageSpeed Insights or Search Console and does your web developer mention terms like LCP and CLS? In this guide you can read in plain language what Core Web Vitals measure, how bad a red score is and what to tackle first.
What are Core Web Vitals?
Core Web Vitals are three Google metrics for the experience of real visitors on your website. They measure the loading, interactivity and visual stability of a page. LCP measures how fast your page loads, INP how quickly it responds to a click or tap and CLS whether the screen stays still.
Google counts them among the Web Vitals that apply to all web pages and that every site owner should measure. According to web.dev, they turn up in all of Google's tools. That is why you see the same three abbreviations in PageSpeed Insights, in Search Console and in your web developer's report.
Sound familiar? You open an online shop on your phone, the page stays white for a moment and just as you tap Order, the button slides down. You tap a banner by accident. Core Web Vitals make exactly that kind of annoyance measurable.
So a red score is annoying and very fixable, once you know which metric is showing red.
Core Web Vitals measure how your site feels to a real visitor.
LCP, INP and CLS in plain language
Behind the three abbreviations are long technical names. A comparison from everyday life makes them much easier to remember.
LCP, the largest element on screen
LCP stands for Largest Contentful Paint. That is the moment the largest piece of content at the top becomes visible, often a wide photo or a large heading. Google uses this as a measure of how a page loads.
Compare it with dinner at a restaurant. The bread beforehand is nice, but you only judge the kitchen once the main course is on the table. LCP is that main course.
INP, responding to a click or tap
INP stands for Interaction to Next Paint, the time between your action and the next change on the screen. INP tracks all clicks, taps and key presses during a visit. The final value is the longest response, leaving out the outliers.
Think of the light switch in your hallway. If you press it and it stays dark for a second, you press it again. That is how a slow Add to basket button feels to your customer.
INP is the successor to FID, First Input Delay. FID measured only the wait at the first interaction on a page. In 2024, INP became a stable Core Web Vital and took the place of FID.
CLS, a screen that stays still
CLS stands for Cumulative Layout Shift, all the jumps in the layout added together. CLS measures the largest burst of unexpected shifts during the entire lifespan of a page.
You know it from reading a magazine in the wind on the beach. Just as you want to read a sentence, the page flips over. On a website, that happens when a photo or banner loads late and pushes the text down.
Good, needs improvement or poor
Every metric has three zones. Green stands for good, orange for needs improvement and red for poor. These are the thresholds Google gives on web.dev.
- LCP is good when the largest element appears within 2.5 seconds of the page starting to load.
- INP is good at 200 milliseconds or less, needs improvement up to and including 500 milliseconds and is poor above that.
- CLS is good at 0.1 or less and poor above 0.25, with needs improvement in between.
For comparison, 200 milliseconds is a fifth of a second. The CLS figure is a score for the shifting. The lower it is, the calmer your screen.
Google measures those thresholds at the 75th percentile of page loads, separately for mobile and desktop. In plain language, at least three out of four visits must stay within the threshold. A customer's slow phone at a campsite counts just as much as your fast office computer.
According to web.dev, a page only passes when it scores good on all three metrics at that percentile. So two greens and one orange still means a resit.
Three out of four visits must score green, on mobile and on desktop.
Core Web Vitals and SEO
How much do these scores weigh for your place in Google? Google Search says so itself. It strongly recommends that site owners achieve good Core Web Vitals, for success in Search and for a good visitor experience in general.
On the same Search Central page it says that this, together with other aspects of page experience, aligns with what the core ranking systems seek to reward. Core ranking systems are the systems that decide which pages Google puts at the top.
Read those words carefully. Google talks about aligning with what it rewards. Green scores belong to a good page, alongside a clear answer to your visitor's question.
A fast page is also pleasant for anyone who wants to call, book or order. If you want to get more out of the visitors you already have, take a look at conversion optimisation.
Green scores align with what Google rewards. Your content remains the foundation.
Measuring Core Web Vitals in PageSpeed Insights
PageSpeed Insights is Google's free measuring tool. You paste the address of a page into the search field and get two kinds of figures. That difference explains a lot of confusion.
Field data from real visitors
At the top is the field data, measurements from real visitors who use Chrome. A browser such as Chrome is the software someone uses to view websites. From the Chrome User Experience Report, PageSpeed Insights shows the experiences of real users over the past 28 days.
If one page has too few visitors for its own measurement, PageSpeed Insights falls back on the data for your whole domain. Your domain is the address of your entire website. If you change something today, the effect comes into view gradually, because those 28 days keep rolling.
Lab data from Lighthouse
Below that is the lab data. Lighthouse, a testing tool from Google, looks at your page in a simulated environment. Think of it as a test drive on a test track, with a simulated phone and a simulated connection.
The field data tells you how real customers experience your site. The lab data helps you find the cause, because each test shows which parts slow things down.
Imagine the lab shows red and the field data shows green. Then your real visitors enjoy a fast site and the test mainly offers tips. The other way round, green in the lab and red in the field, deserves attention straight away.
The report in Search Console
Search Console is the free environment in which Google shows how your site is doing in Search. Where PageSpeed Insights tests one page, the Core Web Vitals report looks at your entire site.
The report groups your pages by status, by metric type and by URL group. The statuses are called Poor, Need improvement and Good. A URL group is a group of similar pages, for example all your product pages.
That grouping saves a lot of work. If five hundred product pages share the same structure, you fix a problem once in the template. The template is the fixed form on which all those pages are built. If you have a large product range, also read about SEO for webshops.
Having a fix validated
Once a problem is fixed, click Start tracking in the report. Google then starts a 28-day monitoring session. If the problem no longer appears anywhere on your site's URLs during that period, it counts as fixed.
That button only starts the tracking. Re-adding your pages to Google, known as indexing, is separate from that. So patiently give it the full four weeks.
Validation is a 28-day check. Patience is part of it.
What do you tackle first?
A long list of red and orange warnings feels overwhelming. A fixed order keeps it manageable. In Search Console Help, Google itself recommends that you fix the issues labelled Poor first.
Step 1. Start with the status Poor
In Search Console, open the Core Web Vitals report and choose the groups with the status Poor. Work like the first-aid tent at a football tournament, where the most serious cases go first.
Step 2. Choose your most visited pages
Put those groups next to your most popular pages. Your homepage, your best-selling products and the service page with the most enquiries come first. An improvement there is noticed by the largest number of visitors.
Step 3. Work on mobile first
Google assesses mobile and desktop separately. Choose the mobile scores first. Your customer is just as likely to view your site on the sofa, in the waiting room or on the touchline at a match.
Step 4. One metric at a time
Tackle one metric at a time per URL group. That way you will later see in the field data which change made the difference. Then move on to the next group.
Improving LCP
With LCP, everything revolves around the largest element at the top, often a wide photo or a large heading. On web.dev, Google lists four steps to get that element on screen faster.
- Let the most important image start loading as early as possible.
- Make sure that image appears as soon as it has arrived.
- Keep the loading time of that image as short as possible, without losing quality.
- Deliver the first HTML, the foundation of your page, as quickly as possible.
In plain language, step 1 is about priority. The browser needs to know that this image must arrive first. Step 3 often comes down to a smaller image that looks just as sharp.
Step 4 is about your server, the computer your website runs on. If it responds slowly, the whole page waits, including your largest element. Ask your web developer which element determines the LCP on your most important pages.
Improving INP
INP is about what happens after a click. If the browser is busy with other work, your click joins the queue. Your visitor then sees a screen that freezes for a moment.
For INP, Google points on web.dev to two guides, optimising long tasks and optimising input delay. A long task is a hefty piece of work that the browser finishes in one go. Input delay is the time between your tap and the moment the browser starts on it.
That work is often JavaScript, the programming language that makes menus, sliders, pop-ups and chat windows work. Every extra script asks the browser to do more computing. That makes a page full of separate gadgets feel sluggish.
Ask your web developer which scripts really deliver something. Whatever can go, remove. Whatever has to stay should ideally load later, once the page is already usable. If you are unsure what can go, read which things you can cut from your website.
Improving CLS
CLS is all about space. The browser builds your page while the parts arrive. If it knows in advance how large a photo will be, it keeps that spot free.
Google is clear about this on web.dev. Always give images and videos a width and a height. Then your text is in the right place from the very first moment.
On web.dev, Google lists even more causes of layout shifts.
- Ads load late and push the content down.
- Embeds, such as an embedded video or map from another website, only get their size later.
- Content arrives later, such as a promotional bar at the top of the page.
- Web fonts, typefaces that load separately, make the text jump once they arrive.
For banners and ads, it works like a café with a Reserved sign on the table. You keep the spot free, even while the guest is still on the way. When the banner arrives, everything else simply stays put.
A fixed spot for every block keeps your screen calm.
Help with improving Core Web Vitals
Some improvements you can make yourself, such as shrinking photos before you put them on your site. Others sit deep in the template, the server or the scripts. Then it helps if someone oversees the whole chain.
We treat speed and Core Web Vitals as one part of technical SEO. For each URL group, we find the cause, carry out the fix and follow the field data until the status shows Good.
A green site stays green with regular attention. New photos, an extra script or a different banner can make the scores drop again. Regular website maintenance keeps an eye on that development.
Want a complete picture of your site first? An SEO audit maps out all the bottlenecks. Feel free to schedule a call with Dominic to go through your red scores together. He is your dedicated point of contact and translates every abbreviation into plain language.
Frequently asked questions about Core Web Vitals (FAQ)
What are Core Web Vitals?
Three Google metrics for the experience of real visitors. LCP measures loading, INP responding to a click or tap and CLS shifts in the layout. According to web.dev, they apply to all web pages.
What do LCP, INP and CLS mean?
LCP stands for Largest Contentful Paint, the moment the largest element appears on screen. INP stands for Interaction to Next Paint, the response time after a click. CLS stands for Cumulative Layout Shift, the shifting of your page.
How can I measure Core Web Vitals?
Use PageSpeed Insights for one page and the Core Web Vitals report in Search Console for your whole site. PageSpeed Insights shows field data from real users over 28 days and lab data from Lighthouse.
Do Core Web Vitals count for SEO?
Google Search strongly recommends good Core Web Vitals for success in Search. Together with other aspects of page experience, that aligns with what the core ranking systems seek to reward. Your content remains the foundation.
What should I improve first?
Start with the status Poor in Search Console, as Google itself recommends. Within that, choose your most visited pages and work on mobile first.
Why do my scores in PageSpeed Insights differ from each other?
At the top is field data from real visitors, below that lab data from a simulated environment. So they measure different things. Use the field data for your verdict and the lab data to find causes.













