Article
Core Web Vitals Explained
Core Web Vitals are Google’s names for whether a page loads its main content quickly (LCP), responds to input (INP), and stays visually stable (CLS). They are user metrics first. Search may use them as one of many signals. They are not a ranking cheat code.
WEBCETRA Editorial · · · 10 min read
The canonical explainer is on web.dev (https://web.devexplorevitals). This article translates the letters into what a business owner should ask a developer to change. Pair it with blog/how to improve website speed.
Contents
- Why these three metrics exist
- LCP — Largest Contentful Paint
- INP — Interaction to Next Paint
- CLS — Cumulative Layout Shift
- Lab versus field, and whose laptop you are testing
- What is worth fixing first
- What Vitals do not replace
- How to talk about this with a vendor
Why these three metrics exist
Lab scores were easy to game and did not match how a phone on 4G feels. Field data — how real users experienced the page — is the number that matters for Core Web Vitals in Search Console.
A beautiful desktop Lighthouse screenshot can hide a failing mobile LCP. Optimise for the field, then use the lab to debug.
LCP — Largest Contentful Paint
LCP asks: how long until the main content (often a hero image or a large heading) appears. Slow servers, huge images, and render-blocking fonts are typical causes.
Fix the LCP element, not a widget in the footer. Preload the hero image. Do not lazy-load it. Compress it. If the LCP is a carousel of five photos, you designed a slow LCP on purpose.
INP — Interaction to Next Paint
INP replaced FID as the interactivity vital. It asks whether taps and clicks feel dead because the main thread is busy with JavaScript.
Chat widgets, tag managers, sliders and heavy frameworks are usual suspects. Reduce third parties. Break up long tasks. Marketing sites rarely need an application-sized JS bundle on every URL.
CLS — Cumulative Layout Shift
CLS asks whether the page jumps while loading. Images without dimensions, ads and embeds that pop in, and webfonts that swap late are typical.
Reserve space. Set width and height. Do not inject a cookie banner that pushes the H1 after first paint if you can avoid it. Cookie banners still need to be operable — accessibility is not optional (https://www.w3.org/WAI/WCAG22quickref).
Lab versus field, and whose laptop you are testing
Lighthouse is a lab on a simulated device. Search Console shows field data for your users when there is enough traffic. PageSpeed Insights shows both where available.
Test the money templates on a mid-range Android on cellular. Office Wi-Fi on a new Mac is a vanity environment. Mobile-specific UX is blog/mobile friendly website guide.
What is worth fixing first
If LCP is failing, start with images, server response and fonts. If INP is failing, start with third-party JS. If CLS is failing, start with dimensions and embeds. Do not install five optimisation plugins that fight.
Technical SEO should keep the page crawlable while you tune — blog/technical seo checklist. Speed work that noindexes the site is not a win.
What Vitals do not replace
A fast empty page still loses to a slower page that answers the query. Google’s quality and relevance documentation lives at https://developers.google.comsearchdocs. Vitals are a participation tax for being usable.
Do not chase a 100 lab score by stripping the contact form. Conversion is the business metric; Vitals are how it feels to get there.
How to talk about this with a vendor
Ask for field status on mobile for home, service and product templates. Ask what they will change this month. “We will install a cache plugin” is not a plan if the LCP is a 4 MB video.
WEBCETRA treats performance as part of services/web development, not a bolt-on. If your theme cannot emit reasonable HTML, the honest fix is a rebuild — cost context in blog/how much does a business website cost.
Questions
Do passing Vitals make us rank first?
No. They may reduce the drag of being painfully slow. Content, intent and competition still decide most rankings.
Why does Search Console disagree with Lighthouse?
Different users, devices and cache states. Field data is the contract for Vitals. Use Lighthouse to find suspects.
How often should we re-test?
After launch, after adding apps or ads, and when Search Console flags a template. Continuous weekly panic is less useful than a performance budget.
Author
WEBCETRA Editorial. Practical articles from WEBCETRA on websites, SEO and digital systems. Written for business readers, not for ranking tricks.
Further reading on Google Search Central (developers.google.com/search/docs), Core Web Vitals on web.dev, and accessibility on the WCAG 2.2 quick reference.