Projects

Core Web Vitals: 7 Powerful Fixes for Better Performance

Core Web Vitals – Core Web Vitals Explained: LCP, INP and CLS

In this guide: Core Web Vitals explained in plain English: what LCP, INP, and CLS measure, how to improve each one, and the best tools to measure them.

Core Web Vitals are Google’s way of measuring how a web page feels to real users: how fast the main content appears, how quickly the page responds, and whether the layout stays stable. They’re part of Google’s page experience signals and a practical guide to building better websites.

Here’s what each metric means and how to improve it.

What Core Web Vitals are

There are three Core Web Vitals:

Metric Measures Good Needs improvement Poor
LCP — Largest Contentful Paint Loading ≤ 2.5 s 2.5–4.0 s > 4.0 s
INP — Interaction to Next Paint Responsiveness ≤ 200 ms 200–500 ms > 500 ms
CLS — Cumulative Layout Shift Visual stability ≤ 0.1 0.1–0.25 > 0.25

Google evaluates them using real-user data from Chrome users (the Chrome User Experience Report), at the 75th percentile — meaning 75% of visits should meet the “good” threshold.

INP replaced the older FID (First Input Delay) metric in 2024 because it better reflects responsiveness throughout the whole visit.

LCP: improve loading in Core Web Vitals

Core Web Vitals LCP thresholds: good up to 2.5 seconds and poor above 4 seconds
LCP threshold diagram. Source: Google web.dev.

LCP measures when the largest visible element — usually a hero image, featured image, or large heading — finishes rendering.

Common causes of poor LCP:

  • Slow server response (high Time to First Byte).
  • Large, unoptimized hero images.
  • Render-blocking CSS and JavaScript.
  • Lazy-loading the hero image (it should load immediately).
  • Web fonts delaying text rendering.

How to improve:

  1. Improve server response: quality hosting, page caching, and a CDN.
  2. Optimize the LCP image: correct dimensions, WebP/AVIF, and compression.
  3. Don’t lazy-load the hero image; consider adding fetchpriority="high" to it.
  4. Preload critical resources such as the hero image or main font.
  5. Reduce render-blocking resources: inline critical CSS and defer non-critical JavaScript.

INP: improve responsiveness in Core Web Vitals

Core Web Vitals INP thresholds: good up to 200 milliseconds and poor above 500 milliseconds
INP threshold diagram. Source: Google web.dev.

INP measures how quickly the page visually responds after a user interaction — a click, tap, or key press. It reports one of the slowest interactions during the visit.

Common causes of poor INP:

  • Heavy JavaScript running on the main thread.
  • Third-party scripts (chat widgets, ads, trackers).
  • Large, complex DOM (too many HTML elements).
  • Expensive event handlers (for example, filters or menus that do too much work).

How to improve:

  1. Reduce and delay JavaScript, especially third-party scripts.
  2. Break up long tasks so the browser can respond between chunks of work.
  3. Keep the DOM smaller — simpler themes and page builders help.
  4. Load scripts only where needed (for example, a slider script only on pages with sliders).
  5. Test with real interactions — open menus, submit forms, filter products.

CLS: improve stability in Core Web Vitals

Core Web Vitals CLS thresholds: good up to 0.1 and poor above 0.25
CLS threshold diagram. Source: Google web.dev.

CLS measures unexpected layout movement — when text jumps because an image, ad, or banner loads late. It’s why you sometimes click the wrong button.

Common causes:

  • Images and videos without width and height attributes.
  • Ads, embeds, and iframes without reserved space.
  • Cookie banners or notices inserted at the top of the page.
  • Web fonts swapping and changing text size.
  • Content injected above existing content.

How to fix:

  1. Always set width and height (or aspect-ratio) on images and videos.
  2. Reserve space for ads and embeds with fixed containers.
  3. Show banners as overlays instead of pushing content down.
  4. Use font-display strategies and matching fallback fonts to reduce shifts.
  5. Avoid inserting content above what the user is already reading.

Tools to measure Core Web Vitals

  • PageSpeed Insights: real-user field data (if available) plus lab diagnostics for a single URL.
  • Google Search Console → Core Web Vitals report: site-wide status grouped by similar pages.
  • Chrome DevTools → Performance panel: record interactions and find long tasks and layout shifts.
  • Lighthouse: lab testing for LCP and CLS (INP requires real interactions; Lighthouse uses Total Blocking Time as a proxy).
  • Chrome DevTools live metrics: use the Performance panel; support for the old Web Vitals extension has ended.

Field vs lab data: field data reflects real users over the past 28 days; lab data is a single simulated test. Prioritize field data for decisions, and use lab data to diagnose.

After fixing issues, it can take up to 28 days for field data to fully reflect improvements. Use Validate Fix in Search Console to track progress.

Key Takeaways: Core Web Vitals

  • LCP = loading, INP = responsiveness, CLS = visual stability.
  • Aim for LCP ≤ 2.5 s, INP ≤ 200 ms, and CLS ≤ 0.1 at the 75th percentile.
  • Fix LCP with faster servers and optimized hero images.
  • Fix INP by reducing JavaScript and third-party scripts.
  • Fix CLS by reserving space for images, ads, and banners.

What is LCP in Core Web Vitals? A practical example

LCP stands for Largest Contentful Paint. Imagine a visitor opening a service page on a phone: the navigation appears first, then a heading, and finally a large product image. If that image is the largest eligible element in the visible area, its appearance can determine LCP. A quick spinner or an early logo does not mean the main content is ready. The useful question is when the visitor can actually see the page’s principal content.

Consider this illustrative situation, not a Hostreta benchmark: a page receives its HTML quickly, but the hero photograph is only discovered after a stylesheet downloads. Compressing the photograph helps its transfer, but the delayed discovery remains. Inspect the request waterfall before choosing a fix. An image that starts downloading late needs a different intervention from an image that starts immediately but is unnecessarily large.

Core Web Vitals reporting also depends on the device and viewport. A desktop visitor might see a large background photograph while a mobile visitor sees a text heading as the largest element. Check both layouts rather than assuming that the featured image is always the LCP element. If you change the template, identify that element again before comparing results.

7 practical fixes for better Core Web Vitals

Use the following sequence as a Core Web Vitals diagnostic workflow. Each step has a specific purpose and a way to check whether the change helped. Apply changes on a staging copy when possible, keep a backup, and check important forms after deployment. Avoid enabling several overlapping optimization features at once because you will lose the ability to explain which change caused an improvement or a regression.

1. Establish a Core Web Vitals baseline

For your Core Web Vitals audit, choose representative URLs: the homepage, a long article, a category page, and a commercial landing page. For a store, include a product page and check the shopping workflow separately. Record the date, URL, device setting, test conditions, and any relevant cache state. Keep field and laboratory Core Web Vitals measurements in separate columns. A single Core Web Vitals test result is a clue, not a complete description of every visitor’s experience.

Run several comparable laboratory tests rather than celebrating the best score. Record the range and investigate inconsistent results. If the first request is slow but later requests are fast, note whether page caching or a remote connection is involved. Do not compare a warm desktop test against a cold mobile test and attribute the difference entirely to your latest plugin change.

A useful Core Web Vitals worksheet includes the metric, observed value, affected template, suspected cause, proposed change, owner, and verification date. Add a column for business checks such as whether a contact form still works. This turns Core Web Vitals work into an accountable maintenance process instead of a series of unrelated score-chasing experiments.

2. Improve Core Web Vitals by prioritizing the main image

Find the actual LCP element in a performance recording. If it is an image, inspect its rendered size and downloaded size. A photograph displayed at a modest width should not require the original camera file. Use appropriately sized images and responsive image markup so a smaller device can receive a suitable resource. Confirm that compression has not made text or product details unreadable.

Do not lazy-load the image that is needed immediately in the first screen. Loading priority and preload can be useful when a critical resource is discovered too late, but adding priority hints to every image defeats the purpose. Treat priority as a limited signal. Recheck the waterfall after a change to confirm that the intended image starts earlier without delaying other essential resources.

For WordPress, inspect the final HTML rather than assuming that a media setting is doing what its name suggests. A theme, image optimizer, and lazy-loading plugin may all change the same image. Check that only the necessary optimization is applied. If a slider creates several competing hero images, consider whether a single static image would communicate the same message more reliably.

3. Diagnose server delays affecting Core Web Vitals

A slow initial response can affect everything that follows, but it is only one part of loading. Compare the initial document request with the remaining work. If the document arrives quickly and the main content still appears late, examine resource discovery, transfer, styles, and rendering before deciding to buy a larger server. Hosting changes cannot directly remove expensive browser-side scripts.

Review page caching for public pages and confirm that private content remains private. Logged-in pages, personalized account information, carts, and checkout screens require particular care. A fast response is not a successful optimization if it serves one customer’s data to another visitor. Read the configuration and test the site’s actual workflows before broadening cache rules.

A CDN can help distribute eligible resources, but measure performance from the audience you serve. For a site targeting the United States, Canada, Britain, Ireland, Australia, and New Zealand, geographic distance and delivery paths can differ. Document the locations used for synthetic tests. Those tests help investigate delivery; they do not replace real-user measurements from each market.

4. Improve responsiveness within Core Web Vitals

For INP, identify the interaction that feels slow. Open the mobile navigation, type into search, expand an accordion, change a filter, and submit a test form. Record the steps in DevTools and look for work that prevents the next visual update. A page can load reasonably quickly yet become unresponsive when a visitor first tries to use it.

List third-party features such as chat, advertising, analytics, social sharing, and embedded videos. Ask whether each feature needs to run immediately on every page. Remove unused features or load them only where needed. Delay settings require functional testing: a menu that only starts working after an unexpected extra tap is a regression even if an automated score improves.

If a custom interaction performs substantial computation, separate the urgent visual feedback from work that can happen later. Give the user an understandable loading or progress state where appropriate. Developers should inspect long tasks and repeated layout work rather than randomly deferring every script. Reproduce the original interaction after each change to ensure that the actual delay is reduced.

5. Stabilize layouts for better Core Web Vitals

For CLS, inspect what moves and what causes the movement. An image may push text downward, but the underlying problem can be missing dimensions. A late advertising slot may expand above a paragraph. An embedded video may load into a container with no reserved height. Identify the responsible component rather than only the element that visibly jumped.

Give images and videos dimensions or a suitable aspect ratio. Reserve a realistic space for embeds and advertisements across responsive layouts. Test narrow screens where an embed’s proportions may differ. If an advertisement is absent, consider how the empty slot behaves; collapsing a large reserved space while someone is reading can create another disruptive movement.

Check cookie notices, newsletter prompts, and font changes as well. An overlay should remain usable and accessible without concealing essential controls. Review headings and buttons after the web font loads. The objective of Core Web Vitals work is a stable, usable page, so avoid a cosmetic fix that simply hides important content or blocks interaction.

6. Audit Core Web Vitals across templates

A Core Web Vitals problem shared by hundreds of articles often belongs to the template. Review the header, sidebar, featured image, sharing controls, related posts, advertising slots, and footer. Improvements to common components can help many pages, while content-specific changes may affect only one article. Start with components that affect the largest number of important visits and can be changed safely.

In WordPress, keep an inventory of active features and the pages that require them. Two plugins can independently provide caching, image loading, or script optimization. Overlapping controls make troubleshooting harder. Test a deliberate configuration on staging and preserve a way to revert it. Do not remove security or backup protection simply because it appears in a resource list.

For related background, read our WordPress caching plugin comparison and guide to testing a website on mobile devices. Choose a cache configuration based on the hosting environment and site functions, then verify it. Installing every recommended plugin is not a performance strategy.

7. Monitor Core Web Vitals after deployment

After deploying a Core Web Vitals fix, repeat the same laboratory checks and manually test key journeys. Check navigation, search, forms, consent controls, and any purchase flow. Clear the relevant caches through the site’s normal controls where needed, and confirm that the intended assets are being served. Record what changed and when so later Core Web Vitals differences have a meaningful reference point.

Field reports reflect a rolling collection period and will not instantly become a clean before-and-after experiment. Watch the trend and check that enough data exists to interpret it. A page with little traffic may have no URL-level field result. That absence does not prove that the page is either fast or slow. Continue with laboratory diagnostics and, when appropriate, properly configured real-user monitoring.

Recheck after installing a new theme feature, advertising integration, form tool, or consent banner. Establish a short release checklist so performance does not depend on a single cleanup exercise. Core Web Vitals are most useful when they become part of normal quality assurance rather than an emergency response to a red dashboard.

How to interpret Core Web Vitals reports correctly

Keep the scope of each Core Web Vitals report visible. A URL-level result describes the available data for that page; an origin-level result summarizes a broader set of pages. Search Console can group URLs with similar experiences. Do not label a particular article fixed solely because another page or the entire origin looks better. Match the measurement scope to the question you are trying to answer.

Mobile and desktop Core Web Vitals reports can disagree because the experiences differ. A powerful computer on a stable connection may conceal issues that affect a lower-powered phone. Conversely, a slow synthetic test does not establish that every visitor has the same experience. Use repeated laboratory tests to investigate causes and field data to understand the observed experience across eligible visits.

The overall Lighthouse performance score is also different from passing Core Web Vitals. Keep the actual LCP, INP, and CLS values visible instead of using one score as a substitute. Passing a technical assessment does not guarantee a search position, a sale, or a specific amount of traffic. Content relevance, clarity, and the visitor’s task still matter.

A practical WordPress Core Web Vitals worksheet

Symptom First check Evidence to keep Functional check
Main image appears late LCP element and request timing Comparable waterfall and image dimensions Image remains clear at mobile widths
Menu opens slowly Interaction recording and long tasks Recorded steps and script attribution Keyboard and touch navigation still work
Article jumps during reading Layout shifts around images and embeds Affected component and reserved dimensions No content is hidden or obstructed
Only the first request is slow Cache behavior and initial response Warm and cold observations kept separately Private pages are excluded appropriately

Use one row per reproducible Core Web Vitals problem, not one row per plugin you want to install. Write down a hypothesis that can be tested: for example, “The hero is discovered late because it is injected by a script.” Then make the smallest change that tests it. If the evidence contradicts the hypothesis, keep the finding and investigate the next cause rather than stacking additional settings on top.

Frequently asked questions about Core Web Vitals

Does a good LCP mean all Core Web Vitals pass?

No. Loading, responsiveness, and stability describe different parts of the experience. A page may show its main content promptly but respond slowly to a filter or shift when an embed loads. Review each Core Web Vitals metric and its measurement scope. Use the threshold table as a checklist, then investigate whichever aspect is failing for the relevant audience.

Should I install the old Web Vitals Chrome extension?

No. Chrome ended support for that extension and incorporated its capabilities into the DevTools Performance panel. Use the maintained browser tooling rather than building a new workflow around the retired extension. See the Chrome team’s migration announcement for the background.

Can changing hosting fix every performance issue?

No. Hosting can influence server response and resource delivery, but layout shifts and heavy interaction handlers can remain after a migration. Identify the bottleneck first. Our small business hosting guide explains the broader selection process. Evaluate actual site needs instead of treating a more expensive plan as proof of better browser performance.

How should a small site work without enough field data?

For Core Web Vitals without field data, use repeatable laboratory tests, inspect real interactions, and check several representative templates. Record that field data is unavailable rather than reporting an invented pass. As the site gains eligible traffic, review the available field reports. You can also evaluate real-user monitoring with appropriate privacy controls, but its results must be clearly distinguished from the data shown by Google.

How Core Web Vitals evolve

Metric definitions can change as browser measurement develops. Google describes a lifecycle with experimental, pending, and stable stages. LCP, INP and CLS are the current stable metrics covered in this guide. When maintaining older articles or reports, check which metrics were measured and when: a historical FID result should not be relabeled as an INP result.

Core Web Vitals lifecycle: experimental, pending and stable measurement stages
Metric lifecycle diagram. Source: Google web.dev.

Official Core Web Vitals references and next steps

Consult Google’s Web Vitals overview for metric definitions. For diagnostic details, use the official guides to optimizing LCP, optimizing INP, and optimizing CLS. These references complement the practical workflow above; none is a promise that a particular configuration will work on every site.

Begin your Core Web Vitals review with one important template and one verified problem. Measure it, make a targeted change, and check both performance and functionality. Expand the fix to other affected pages only after the result is understood. That process produces a more defensible improvement than a long list of optimization switches with no record of what they changed.

Z
zasma171

Writes for Hostreta about the topics covered in this article.

Comments (0)

Your email address will not be published. Required fields are marked *

Ad
Affiliate links
Tools we recommend
Protect Your Website with Automated Daily Backups
$2.09
Get it
the easiest way to manage all of your social media accounts
$29
Get it
Starter Website Get online, properly
$249
Get it
google workspace Business Starter
$3.75
Get it
Nord Vpn Cybersecurity. Built for Everyday Use
$8.99
Get it
More hosting options · affiliate
AI SiteBuilder
View plans
AI Application Hosting
View plans
Shared Hosting
View plans
Reseller Hosting
View plans
Managed WordPress · Rocket.net
View plans
Unmanaged VPS Hosting
View plans
Managed VPS Hosting
View plans
Virtual Dedicated Servers
View plans

We may earn a commission on purchases made through these links, at no extra cost to you.

Ad
Ad

$ top hosting picks

affiliate
★★★★★

KAWEDMA Website Services

See optionsCheck current plans and terms
  • Explore website setup services
  • Choose a scope that fits your project
  • Confirm features with KAWEDMA
Explore KAWEDMA →
affiliate link · we may earn a commission
★★★★★

Managed WordPress Hosting

See plansCurrent terms on provider website
  • Managed hosting for WordPress
  • Powered by Rocket.net
  • Compare current plan specifications
View WordPress plans →
affiliate link · we may earn a commission
★★★★★

AI SiteBuilder

See plansCheck current offer and renewal terms
  • Explore AI-assisted website creation
  • Review included tools and features
  • Choose a plan for your project
Explore SiteBuilder →
affiliate link · we may earn a commission

Never miss a new article

Join thousands of developers and builders getting a weekly digest of the best tech articles.