What is LCP by Chrome version
LCP by Chrome version shows the Largest Contentful Paint (LCP) segmented by the version of Google Chrome the user was running when visiting your site. This lens helps you spot regressions or performance differences introduced by new (or old) Chrome versions.
You’ll only see Chrome versions that actually sent traffic to your website during the selected time range. The data includes both mobile and desktop Chrome traffic.
Why this matters: Browser updates can include changes to rendering behavior, JavaScript engine performance, and how Core Web Vitals are calculated — all of which directly impact LCP.
LCP is the most popular vital from the Core Web Vitals and represents the loading time of the largest element on the page.
Healthy LCP by Chrome version sample
Should you worry
In a healthy view, all commonly used Chrome versions are green. Slight variance across versions is expected - but if users on the latest version have a consistently slower LCP, it may point to a browser-specific issue or a site feature that doesn’t play well with recent changes.
Older versions may occasionally show poorer LCP due to outdated rendering engines or unsupported performance features - but as long as their traffic share is low, they’re less urgent.
Unhealthy LCP by Chrome version sample
If the latest Chrome version shows degraded LCP, that’s something to investigate right away. It could be due to:
A new rendering behavior introduced by Chrome (e.g. a paint timing change).
Compatibility issues with recent JavaScript APIs or CSS features.
A slow third-party script that affects how fast the largest element renders in this version only.
Accidental regressions in your frontend that were not tested on the updated browser.
On the flip side, if very old Chrome versions are showing poor LCP and still represent significant traffic, you might be relying on newer performance APIs those users don’t support — which means you’ll need fallbacks.
Resolving unhealthy LCP by Chrome version
Go-to action plan to resolve an unhealthy LCP by Chrome version:
Ask Uxi to analyze your LCP by Chrome version values and suggest improvements.
Use Filters to isolate the affected version and look at page-level patterns.
Simulate LCP of the suspected lens to see if fixing it will resolve the slow LCP by Chrome version. If yes, this is where the resolution focus should be.
Use an automated LCP optimization tool like Navigation AI to improve your LCP by Chrome version values.
Once you’ve improved LCP, set an alert to be the first to know if it starts worsening again.
Try it yourself
Discover how your website performs with real user data.