How to Improve Core Web Vitals: A Practical Guide for Business Websites

To improve Core Web Vitals, make your main content load faster (LCP), make the page respond quickly to taps and clicks (INP) and stop the layout from jumping while it loads (CLS). Google treats a page as good when, for at least 75% of real visits, LCP is 2.5 seconds or less, INP is 200 milliseconds or less and CLS is 0.1 or less (web.dev). The biggest wins usually come from smaller images, less JavaScript, better caching and reserved space for images and ads.

Quick answer: optimise your largest image or text block, cut and delay JavaScript, set width and height on media, and check field data in PageSpeed Insights or Search Console to confirm real users see the improvement.

What are Core Web Vitals?

Metric	What it measures	Good	Needs improvement	Poor
LCP (Largest Contentful Paint)	How fast the main content appears	2.5 s or less	2.5 to 4 s	Over 4 s
INP (Interaction to Next Paint)	How fast the page responds to input	200 ms or less	200 to 500 ms	Over 500 ms
CLS (Cumulative Layout Shift)	How much the layout moves unexpectedly	0.1 or less	0.1 to 0.25	Over 0.25

INP replaced First Input Delay (FID) as a Core Web Vital in March 2024. It measures every interaction during a visit, not just the first one, so slow scripts anywhere on the page now count.

Field data vs lab data

PageSpeed Insights shows two kinds of results:

• Field data comes from real Chrome users over the last 28 days. This is what Google uses as a page experience signal.
• Lab data comes from a single simulated test. It is useful for diagnosing problems, but it can differ from what users experience.

Always check field data in PageSpeed Insights or the Core Web Vitals report in Google Search Console before and after changes. Small sites may not have enough traffic for field data, so use lab tests as a guide.

How to improve LCP

LCP is usually your hero image, a large banner or the main heading block.

1. Find the LCP element. PageSpeed Insights names it in the diagnostics.
2. Make the image smaller. Resize it to its display size and serve WebP or AVIF.
3. Load it early. Do not lazy-load the LCP image. Add a preload hint or fetchpriority=”high”.
4. Speed up the server. Use page caching and good hosting to cut server response time.
5. Remove render-blocking files. Inline critical CSS and defer non-essential CSS and JavaScript.

How to improve INP

INP problems come from JavaScript keeping the browser busy when someone taps or clicks.

1. Cut unused JavaScript. Remove plugins, widgets and libraries you do not need.
2. Delay third-party scripts. Load chat widgets, heatmaps and social embeds after the page settles or on interaction.
3. Break up long tasks. Developers can split heavy scripts so the browser can respond between steps.
4. Simplify heavy pages. Large menus, sliders and filters with lots of DOM elements slow down interactions.

How to improve CLS

CLS happens when content moves after it first appears.

1. Set width and height on images and videos so the browser reserves space.
2. Reserve space for ads, embeds and banners that load later.
3. Avoid inserting content above existing content, such as cookie bars that push the page down.
4. Load web fonts carefully with font-display settings and matched fallback fonts to avoid text jumping.

Core Web Vitals fixes by platform

• WordPress: use a lightweight theme, page caching, image optimisation and fewer plugins. See why WordPress sites slow down.
• Shopify: limit apps, compress theme images and remove app code left behind after uninstalling.
• Custom sites: server-render key content, split JavaScript bundles and optimise images at build time.

Do Core Web Vitals affect SEO?

Yes, but they are one signal among many. Core Web Vitals are part of Google’s page experience signals. Relevant, helpful content still matters most. Faster pages do keep more visitors, which improves enquiries and sales even when rankings do not change.

How long until improvements show up?

Lab tests change immediately. Field data in PageSpeed Insights and Search Console uses a rolling 28-day window, so improvements take up to four weeks to show fully. Use Search Console’s validation feature to track fixed issues.

Get help improving your Core Web Vitals

Our website speed optimization service targets real-user Core Web Vitals, with before-and-after scores. The Core Web Vitals plan covers every page template for $199. For a full technical review, see our SEO audit from $149.

From our projects: Our own site, attors.com, serves prerendered pages from Next.js with preloaded hero images, and we measure every release against the thresholds below before it goes live.

What the research says: A good experience means Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. (Source: Google’s Core Web Vitals guidance.)