Difference between Core Web Vitals & LHS metrics

Skip to first unread message

Meet Kumar Jain

Feb 27, 2024, 6:18:07 PMFeb 27
to Chrome UX Report (Discussions)
Hello TEAM, 

We have Core Web Vitals section and we have LHS metrics down below, where it does again talk about LCP, CLS, FCP etc but not FID. 

Which stats we need to concentrate on ? 28 days data by CRUX or the real time data under LHS metrics ? 



Barry Pollard

Feb 27, 2024, 6:33:08 PMFeb 27
to Meet Kumar Jain, Chrome UX Report (Discussions)
Always concentrate on field data (the top section) for how your site is actually experienced by your actual users.

Use the Lab data (Lighthouse data at the bottom) to drill down into that for more diagnostic details. But always check it matches up to the field data to see how representative the Lighthouse test is of your real user. There is likely less to gain from optimising LCP when Lighthouse tells you that is an issue, if your real users are not experiencing any LCP problems. Yes you can always improve, but you should look at other potential problem areas first.

Lab data describes how hypothetical users may experience your website. Field data describes how real users actually experienced your website. Field data is also known as Real User Monitoring (RUM), and is typically collected by monitoring real user experiences using JavaScript on the pages they load, and reporting various metrics to an analytics solution.


Always concentrate on field Core Web Vitals over Lighthouse metrics and scores. In particular, the Performance Score of Lighthouse is a broad measure of that lab test and often does not correlate with field Core Web Vitals.

Lighthouse is an amazingly useful tool to look at ways you can improve your site and repeatedly test changes quickly. But is a single, cold, page load, until very specific conditions (often slower than real users to emphasize performance problems), rather than a good measuring tool of how the site is actually used and experienced.

As Lighthouse does not by default do any interactions a users would do (open menus, click buttons, click links) it cannot measure FID nor INP. Total Blocking Time (TBT) is the best it can surface so show when the page is running a lot of blocking code and therefore likely to experience FID and INP issues.


You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ux-repo...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/aade1b2d-dc0a-40cf-a489-f5cab12aa6a2n%40chromium.org.
Reply all
Reply to author
0 new messages