How to Improve Core Web Vitals: Fixing the 3 Metrics
A plain guide to Google's Core Web Vitals for business owners: what each metric measures, where to find your real scores, and the practical fixes that usually move them in the right direction.

Quick answer
To improve Core Web Vitals, first check real-user data in Search Console or PageSpeed Insights, then fix the metric that fails. Speed up the main image and server response for LCP, cut heavy JavaScript and third-party scripts for INP, and reserve space for images, fonts and banners for CLS. Re-measure after changes, since field data updates slowly.
In this article
Get a free auditIf you want to improve Core Web Vitals, it helps to know that each of the three metrics measures a different kind of frustration, and each has different causes. A site can load quickly yet feel sluggish when tapped, or look fast but jump around as it loads. Fixing the wrong thing wastes time and budget. This guide explains what each metric means, how to find the real cause and which fixes usually make a difference.
What do Core Web Vitals measure?
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors.
| Metric | What it measures | What a visitor notices |
|---|---|---|
| LCP, Largest Contentful Paint | How long the main content takes to appear | The page seems slow to load |
| INP, Interaction to Next Paint | How quickly the page responds to taps and clicks | Buttons and menus feel laggy |
| CLS, Cumulative Layout Shift | How much the layout moves while loading | Text jumps and people tap the wrong thing |
Google publishes thresholds for each metric and rates pages as good, needs improvement or poor. INP replaced an older responsiveness metric, so advice written a few years ago may talk about a different measure.
These metrics are one of many signals in search. They rarely outrank relevant content, but they do affect how many visitors stay long enough to enquire.
Where can you find your real scores?
There are two kinds of data, and the difference matters.
Field data comes from real Chrome users visiting your site over recent weeks. This is what Google uses. You find it in the Core Web Vitals report in Google Search Console and at the top of PageSpeed Insights, where enough traffic exists.
Lab data is a single simulated test, shown lower down in PageSpeed Insights and in browser developer tools. It is useful for diagnosing problems and testing fixes, but it can differ from what real visitors experience.
Before you try to improve Core Web Vitals, start with Search Console. It groups pages with similar problems, so you can see whether an issue affects one template, such as every product page, or the whole site. Fixing a template usually fixes hundreds of URLs at once.
How to improve Core Web Vitals for loading (LCP)
LCP is usually the hero image, a large heading or a banner at the top of the page. It is often the quickest metric to move, which makes it a sensible place to improve Core Web Vitals first. To speed it up:
- Serve the main image at the right size, in a modern format such as WebP or AVIF, and do not lazy-load it. Lazy loading suits images further down the page, not the first one.
- Tell the browser about it early, using a preload hint or high fetch priority for that image.
- Reduce server response time with page caching, a content delivery network and hosting that suits your traffic.
- Cut render-blocking CSS and fonts, so the browser can paint the page sooner.
- Avoid sliders at the top of the page. They tend to load several large images and delay the main one.
For sites serving the GCC, India, the UK and Australia from one server, a CDN helps a lot, because it serves files from a location nearer each visitor.
Fixing slow responses (INP)
INP problems come from JavaScript keeping the browser busy, so it cannot react when someone taps. To improve Core Web Vitals here, you mostly remove work rather than add anything.
Common causes on business sites:
- Chat widgets, heatmap tools, ad pixels and review widgets all loading at once
- Page builder add-ons that load scripts on every page, even where unused
- Large menus or filters that run heavy code on each click
- Old libraries kept for features nobody uses
Start by listing every third-party script and asking whether it still earns its place. Remove what you can. Delay the rest until after the page has loaded or until the visitor interacts, which suits chat widgets well.
On shops, product filters and add-to-cart buttons are frequent offenders. Test them on a mid-range phone, not only a fast laptop, since that is closer to what most visitors use.
Stopping layout shift (CLS)
Layout shift happens when something appears or changes size after the page has started showing. The fixes are mostly about reserving space.
- Set width and height on images and videos, so the browser knows how much room to leave.
- Reserve space for banners and embeds, such as cookie notices, promotional bars and maps.
- Use font fallbacks that match your web font, so text does not reflow when the real font loads.
- Avoid inserting content above what the visitor is reading, for example late-loading notices at the top.
Fonts are an easy one to miss. On our redesign of the VF Photonix site, metric-matched fallback fonts were one of the steps that kept layout shift low, alongside trimming unused CSS. The finished site scores 95 on mobile and 99 on desktop in Google PageSpeed.
Platform notes: WordPress, Shopify and page builders
WordPress
Most WordPress problems trace back to too many plugins, a heavy theme or page builder assets loading everywhere. A caching plugin helps, but it cannot fix a page that is simply too heavy. Audit plugins first, then cache. Lean WordPress development from the start avoids most of the problem.
Shopify
Shopify hosting is fast, so issues usually come from apps and theme code. Uninstalled apps can leave scripts behind in the theme, so check the code after removing any app.
Page builders
Elementor and similar builders can produce good scores, but only with care: fewer widgets, unused features switched off and no stacked add-on packs. The builder rarely causes the problem on its own. The way it is used usually does.
How to improve Core Web Vitals and keep them good
When you set out to improve Core Web Vitals, work in this order:
- Check Search Console to find which metric and which page groups fail.
- Use lab tests to find the cause on a representative page.
- Fix the template, not single pages.
- Re-test in the lab, then wait for field data to catch up over the following weeks.
The last step needs patience. Field data covers several weeks of visits, so improvements show gradually.
Keeping scores good is a separate job. New plugins, marketing scripts and large uploaded images slowly undo the work. A short monthly speed check, built into website maintenance, catches that drift early.
If you would rather hand the work over, our website speed optimisation service will improve Core Web Vitals without changing your design or content, and measures the results before and after.
Related service Speed OptimisationFAQ
Common questions
Do Core Web Vitals affect Google rankings?
They are part of Google's page experience signals, so they can play a role, but relevance and content quality matter far more. A fast page with weak content will not outrank a slower page that answers the search much better. The bigger benefit is usually commercial: pages that load quickly and respond smoothly keep more visitors long enough to enquire or buy.
Why does PageSpeed Insights show different scores each time?
The lab test at the bottom of the report is a single simulated visit, and results vary with server load, network conditions and third-party scripts. Small swings are normal. Focus on the field data at the top, which reflects real visitors over recent weeks, and on trends over time rather than one test result.
How long does it take to see Core Web Vitals improve?
Lab tests show the effect of a fix straight away. Field data in Search Console and PageSpeed Insights is based on several weeks of real visits, so it changes gradually. Expect to wait a few weeks after a fix before the report reflects it. Pages with little traffic may not have field data at all.
Will a faster hosting plan fix my Core Web Vitals?
Sometimes, mainly for LCP when the server is slow to respond. Hosting will not fix layout shift, oversized images or heavy JavaScript, which are the more common causes. Check where the time goes before upgrading. Moving to better hosting while the page itself stays heavy often gives a smaller gain than people expect.


