Free tools Windows power users keep installed
One-click scans. No signup required.
Core Web Vitals are LCP, INP, and CLS: measures of loading, responsiveness, and visual stability. To improve them, start with real-user field data, separate mobile from desktop, identify the failing metric, reproduce its likely cause with lab tools, make a targeted change, and verify the result in field data. A lab score can help you debug, but it is not a substitute for how visitors experience your site.
What are the Core Web Vitals in 2026?
Google’s current Core Web Vitals are three stable metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Each describes a different part of the experience, so a single overall score can hide the problem visitors actually encounter. The current definitions and thresholds are documented in Google’s Web Vitals overview.
As an Amazon Associate I earn from qualifying purchases.
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP | Loading: when the main content has likely loaded | ≤ 2.5 seconds | > 2.5 and ≤ 4 seconds | > 4 seconds |
| INP | Responsiveness across user interactions | ≤ 200 milliseconds | > 200 and ≤ 500 milliseconds | > 500 milliseconds |
| CLS | Unexpected movement of visible content | ≤ 0.1 | > 0.1 and ≤ 0.25 | > 0.25 |
Judge each metric at the 75th percentile (p75), separately for mobile and desktop. At p75, at least three quarters of visits are at or better than the reported value. The same recommended thresholds apply to both device classes; Google explains its threshold methodology.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallINP is the current stable responsiveness metric; First Input Delay (FID) is not the current Core Web Vital. INP considers click, tap, and keyboard interactions throughout the visit rather than only the first input. Google’s INP guide explains how it succeeds FID.
#1 Best Overall
How should you measure site performance?
Begin with field data, then use lab tools to investigate. Field data reflects real visits; a lab run is a controlled, repeatable test that helps reproduce and inspect potential causes. Google’s measurement guide describes the distinction.
- Check field status. Use PageSpeed Insights or Search Console’s Core Web Vitals report when your site has data in Chrome User Experience Report (CrUX). Read results by metric and device class. Aggregated results flag areas to investigate; they are not a trace of one visitor’s session.
- Reproduce with a lab tool. Inspect a local trace in Chrome DevTools’ Performance panel, use Lighthouse for repeatable audits, or use WebPageTest to run tests under selected device and network conditions. These help isolate issues and assess changes before release.
- Compare like with like. Align device, network, viewport, content variant, and cache conditions as closely as practical. A lab test can differ from field data because of redirects, connection latency, caching, screen-dependent content, cookie banners, or personalization.
- Instrument production if aggregates are too coarse. The
web-vitalsJavaScript library can send LCP, INP, and CLS measurements to an analytics endpoint. Site-owned real-user monitoring (RUM) can add pageview-level detail for diagnosis and regression response. - Change one likely cause and measure again. Use traces and field evidence to connect a proposed fix to the failing experience. Verify before and after under relevant conditions rather than assuming an optimization helped.
Ordinary Lighthouse runs do not measure INP directly because the metric depends on user input. Lighthouse reports Total Blocking Time (TBT), which can help reveal main-thread blocking in a lab but is only a proxy, not a field INP score. Lab CLS may also miss shifts that happen after load or after an interaction.
Rank #2
Which measurement approach should you use?
| Approach | Best use | Main limitation |
|---|---|---|
| CrUX in PageSpeed Insights or Search Console | Aggregate field status for eligible pages or origins | No detailed per-pageview trace; coverage depends on CrUX eligibility and available data |
Site-owned RUM, including web-vitals instrumentation |
Production diagnosis, segmentation, and regression monitoring | Requires implementation and an analytics destination; readings may differ from CrUX |
| Chrome DevTools Performance panel | Local trace inspection and responsive debugging | Your device, network, and interactions may not represent the user population |
| Lighthouse or Lighthouse CI | Repeatable lab audits and pre-release regression checks | Standard lab runs do not directly measure INP; TBT is a proxy |
| WebPageTest | Synthetic comparisons under selected conditions | It remains a lab test and cannot replace field data |
These tools answer different questions rather than competing to provide one definitive score. See Google’s Web Vitals overview, its measurement guide, the Lighthouse documentation, and the DevTools Performance panel documentation.
How do you fix poor LCP?
LCP identifies when the main content has likely loaded. First find the LCP element, then trace how its content or resource is discovered and delivered. It may be an image, text block, or a banner or personalized element; the right fix depends on which one is actually largest for the affected visits.
- Check whether the LCP resource is discoverable early in the HTML and whether it is prioritized appropriately.
- Trace time to first byte for the document and for the LCP resource. If waiting for either response dominates, investigate the delivery path; a content delivery network can help where origin distance or response time is the bottleneck.
- Compare the lab page with the affected field experience: redirects, cache state, viewport, cookie banners, personalization, and device or network conditions can change which content becomes the LCP element or how quickly it arrives.
Google’s Core Web Vitals optimization guide emphasizes making the LCP resource discoverable from HTML, prioritizing it, and improving document and resource time to first byte. Do not add caching or preload changes without evidence that they address the measured bottleneck.
How do you fix poor INP?
INP reflects the path from an interaction to the next paint, including input delay, event-handler work, and the time until the browser can render feedback. Look for the slow interaction and the main-thread work that delays it, rather than assuming every interaction or every page has the same cause. The INP guide notes that Chrome usage data shows 90% of a user’s time on a page is spent after it loads; that figure is Chrome usage data reported in a guide published in 2022 and updated in 2025, not a new 2026 study.
Break up work that blocks input
Split long tasks and yield to the main thread so the browser can process input and render sooner. A long task is work exceeding 50 milliseconds, a diagnostic threshold in Google’s optimization guidance—not a Core Web Vital pass/fail cutoff.
Reduce unnecessary JavaScript
Use DevTools Coverage to identify unused code, split bundles where appropriate, and review tag-manager code. Less unnecessary work can reduce competition for the main thread.
Avoid oversized rendering updates
Keep DOM size manageable, avoid forced layout and layout thrashing, and limit large rendering updates. For longer asynchronous operations, show prompt visual acknowledgment that the interaction registered; without it, a delayed response may lead a visitor to click again.
Best Value
These priorities—yielding between long tasks, removing unnecessary JavaScript, and avoiding large rendering updates—are outlined in Google’s optimization guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do you find and prevent layout shifts?
CLS measures unexpected movement of visible content. Investigate what appeared, resized, or moved after the surrounding page had already been laid out. Make room for content before it arrives, and avoid animations or transitions that change layout.
- Give content that loads into the page explicit dimensions so the browser can reserve space.
- Avoid inserting content above existing content in a way that pushes it down unexpectedly.
- Prefer animation approaches that do not use layout-inducing CSS properties.
- Check the full page lifecycle, not only the initial load: shifts can occur later or after interaction, so combine field monitoring with lab checks.
Google’s optimization guide covers explicit sizing, back/forward cache eligibility, and avoiding layout-inducing animations. The measurement guide explains why lab tests may not capture shifts across the full lifecycle.
Why does PageSpeed Insights disagree with Lighthouse?
PageSpeed Insights can show CrUX field data alongside a Lighthouse lab audit. Those numbers describe different evidence: CrUX aggregates eligible real visits, while Lighthouse runs a controlled test with specific conditions. Differences are expected, not proof that either measurement is wrong.
Field visits vary in network latency, redirects, cache state, viewport, banners, and personalized content. A standard Lighthouse run also cannot measure INP without interaction, so it reports TBT as a lab diagnostic. Compare the same metric, device class, and time context where possible, and use the lab trace to investigate rather than to overrule field performance.
Google describes the relationship between field and lab data in its measurement guide and explains the Core Web Vitals in its overview.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
