Core Web Vitals are three measurements of real user experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Improve them by optimising images, loading fonts and scripts carefully, caching content and reserving space for elements that load late. They are one signal among many, so fast pages help people first.
Key takeaways
- Core Web Vitals measure loading (LCP), responsiveness (INP) and visual stability (CLS).
- Field data from real visitors matters more than a single lab test score.
- Large images, heavy JavaScript, slow servers and late-loading ads or embeds cause most problems.
- Fix the biggest cause on your most important pages first, then measure again.
- Better speed helps visitors and conversions; it does not by itself promise better rankings.
The three metrics in plain English
At the time of writing, Google documents "good" as roughly 2.5 seconds or less for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS, measured at the 75th percentile of visits; check web.dev for current guidance, as thresholds and metrics can change.
Largest Contentful Paint (LCP)
LCP measures how long it takes for the largest visible element in the first screen, often a hero image, a banner or a big block of text, to appear. It answers the visitor's question: "Has the page loaded?" Slow LCP usually comes from heavy images, slow server responses, render-blocking resources or content that waits for JavaScript.
Interaction to Next Paint (INP)
INP measures how quickly a page responds visually after a person clicks, taps or types. It reflects the slowest or near-slowest interactions during a visit. Poor INP is usually caused by long-running JavaScript that keeps the browser busy, such as large bundles, heavy third-party scripts or complicated page updates.
Cumulative Layout Shift (CLS)
CLS measures unexpected movement of content while the page loads. You have felt it when you go to tap a button and an advert pushes it down. It is typically caused by images without dimensions, late-loading embeds or ads, and fonts that swap and change the text size.
Field data versus lab data
Lab data comes from a controlled test run on one device and connection. It is useful for debugging because it is repeatable. Field data comes from real visitors on their own phones and networks, and it is what the Core Web Vitals assessment is based on. A page can look excellent in a lab test on a fast laptop and still be slow for users on mid-range phones with patchy mobile data, which describes many visitors in India. Use both: field data to find out whether you have a problem and lab tools to find out why.
Free tools such as PageSpeed Insights and the reports in Google Search Console show real-user data where there is enough traffic. Low-traffic sites may only have lab data, which is fine for guidance.
How to improve LCP
- Right-size images. Serve images no larger than the space they fill, and use responsive image sizes so phones do not download desktop files.
- Use modern formats. Formats like WebP or AVIF are often smaller than older formats at similar quality, but test your own images.
- Prioritise the main image. Do not lazy-load the hero image, and tell the browser to fetch it early.
- Speed up the server. Cache pages where you can, use a CDN so content is served from near the visitor (our cloud solutions cover hosting and architecture), and fix slow database queries.
- Trim render-blocking files. Remove unused CSS and defer scripts that are not needed for the first view.
How to improve INP
- Reduce the amount of JavaScript shipped. Remove unused libraries and split code so each page loads only what it needs.
- Audit third-party scripts such as chat widgets, tag managers and trackers; each one competes for the browser's attention.
- Break up long tasks so the browser can respond between chunks of work.
- Keep interface updates light, especially in filters, menus and forms.
Our website development work includes Core Web Vitals tuning for this reason: a lot of INP trouble starts in how a site was built, not in a setting.
How to improve CLS
- Always set width and height (or an aspect ratio) on images and videos.
- Reserve space for ads, cookie banners, embeds and late-loading widgets so they do not push content around.
- Load fonts carefully: choose a fallback font with similar proportions and use a font-display setting that avoids sudden jumps.
- Do not insert new content above existing content unless the visitor triggered it.
Common mistakes
- Chasing a perfect lab score on the home page while ignoring product or landing pages that earn the traffic.
- Adding a speed plugin on top of a heavy design instead of removing weight.
- Lazy-loading everything, including the image that defines LCP.
- Installing every marketing tag at launch and never reviewing them.
- Testing only on a fast office connection.
A worked example
Imagine a service business whose homepage hero is a large photo uploaded straight from a camera. The page also loads a chat widget, two analytics tags and a carousel library. A reasonable order of fixes: resize and compress the hero and mark it as high priority (LCP), remove the carousel and defer the chat widget until the visitor scrolls or interacts (INP), and set dimensions on every image and reserve space for the cookie banner (CLS). Then re-test on a mid-range phone over mobile data and compare real-user data a few weeks later, since field reports update gradually.
Do Core Web Vitals affect SEO?
Google has said that page experience, including these metrics, is one of many signals used in search, and that content relevance remains more important. In practice, treat performance as a way to reduce bounce and friction, with any search benefit as a bonus. Speed sits alongside crawlability, indexing and content in a wider technical SEO review, and faster, steadier pages also support conversion by reducing friction.
FAQ
What is a good Core Web Vitals score?
There is no single score; each metric has its own "good", "needs improvement" and "poor" range. See the thresholds above and confirm current values on web.dev. The goal is for most real visits, at the 75th percentile, to fall in the good range.
Why is my mobile score worse than desktop?
Phones have less processing power and often slower networks, so heavy images and JavaScript hurt more. Mobile results are usually the better indicator of what most visitors experience.
How long until improvements show up?
Field data is collected over a rolling period, so changes usually appear gradually over several weeks rather than overnight. Lab tests show the effect immediately.
Do I need a developer to fix this?
Image compression and removing unused plugins can often be done by a site owner. Fixes involving JavaScript, rendering and server setup typically need a developer.
Next steps
Open PageSpeed Insights for your three most valuable pages, note which metric fails and fix the biggest single cause first. If you would like help, you can contact us for a practical review, and our SEO services pair performance with technical audits and reporting.
