Core Web Vitals field data on Wix: understanding CrUX and real-user metrics

Lab data from PageSpeed Insights and Lighthouse tells you what could happen in an ideal test scenario. Field data from the Chrome User Experience Report (CrUX) tells you what is actually happening for real users visiting your Wix site. Understanding the difference — and prioritising field data — is essential for making Core Web Vitals improvements that move your GSC rankings.

Lab Data vs Field Data: The Critical Difference

Lab data is collected in a controlled, simulated environment using specific device profiles and network conditions. It is consistent and reproducible, but does not reflect the actual devices, connections and behaviours of your real visitors. Field data is aggregated from real Chrome browser sessions. Google uses field data (CrUX) to determine Core Web Vitals status for ranking purposes, not lab scores.

How the Chrome UX Report Collects Wix Site Data

• CrUX data is collected anonymously from Chrome users who have opted into usage reporting
• Data is aggregated at the origin level (your domain) and URL level
• A minimum volume of page visits is required before CrUX data appears for a URL
• Data is updated monthly in the GSC Core Web Vitals report
• New Wix sites or low-traffic pages may not have enough CrUX data to appear

Reading the Core Web Vitals Report in GSC

Interpreting your Wix Core Web Vitals data in Search Console

• Navigate to Experience > Core Web Vitals in your GSC property
• Select Mobile and Desktop reports separately — they have different thresholds and scores
• Review the Good, Needs Improvement and Poor URL counts for LCP, INP and CLS
• Click on "Poor URLs" to see which specific Wix pages fail the most
• Use the URL Inspection tool on failing pages to request a CrUX re-evaluation after fixes
• Allow 28 days after making fixes before expecting GSC scores to update

Why Lighthouse and GSC CWV Scores Often Disagree

A Wix page can score 90+ on PageSpeed Insights (lab) but show Poor status in GSC (field). This happens because: lab tests simulate one device on one network, while real users span a range of devices; lab data is sampled instantly, while CrUX is a 28-day rolling average; and certain Wix app interactions (like opening a booking widget) only happen with real user interaction, not during automated tests.

How to Read Your Core Web Vitals Field Data in Google Search Console

How to use GSC field data to identify and prioritise Core Web Vitals fixes on your Wix site

• Log in to Google Search Console and select your Wix site property.
• Click Experience > Core Web Vitals in the left sidebar to open the CWV report.
• Select the Mobile tab first — mobile field data is more important for ranking because Google uses mobile-first indexing.
• Review the summary showing the count of Good, Needs Improvement, and Poor URLs for each metric (LCP, INP, CLS).
• Click the Poor URLs count for your worst-performing metric to see a list of the specific Wix pages failing that metric in field data.
• Click on a specific page in the Poor URLs list to open its URL detail, which shows the metric values and threshold status.
• Open PageSpeed Insights and enter the URL of a failing page to get both lab diagnostics and field data context in one report.
• In the PageSpeed Insights results, scroll to the Opportunities and Diagnostics sections for specific recommendations on what is causing the field data failure.
• After implementing a fix (such as removing a heavy third-party script or optimising images), allow 28 days for the CrUX field data to update in GSC before expecting the score to improve.
• Switch to the Desktop tab in GSC Core Web Vitals and repeat the review — desktop and mobile scores often differ significantly on Wix sites due to different JavaScript execution environments.