Core Web Vitals field data on Wix: understanding CrUX and real-user metrics
Module 6: Technical SEO, Structured Data & Rich Snippets for Wix | Lesson 89 of 683 | 26 min read
By Michael Andrews, Wix SEO Expert UK
Lab data from PageSpeed Insights tells you what could happen. Field data from the Chrome UX Report tells you what is actually happening for real users. This lesson explains the difference, how to read CrUX data for your Wix site, and why your GSC Core Web Vitals report may show different results from Lighthouse.
What you will learn in this Wix SEO lesson
- The difference between lab data and field data for Core Web Vitals
- How the Chrome UX Report collects real-user data from Wix visitors
- Reading the Core Web Vitals report in Google Search Console
- Why Lighthouse and GSC CWV scores often disagree
- Prioritising CWV fixes based on field data rather than lab tests
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.
Essential Tools for This Lesson
- SEO Fix in a Box: My Wix app. Free to install, it scans your site and shows what needs fixing, and the paid plan writes the fixes from your own Google searches
More lessons in Module 6: Technical SEO, Structured Data & Rich Snippets for Wix
- Wix site speed optimisation: a step-by-step Core Web Vitals guide
- Mobile SEO on Wix: common pitfalls and exactly how to fix them
- What is structured data? JSON-LD vs Microdata vs RDFa, which to use on Wix
- How to add JSON-LD schema markup to any Wix page using Custom Code
- Organisation and LocalBusiness schema: tell Google exactly who you are
- BreadcrumbList schema: how to implement breadcrumbs on Wix and get them in results
- FAQ schema on Wix: boost AI citations and semantic search clarity
- HowTo schema on Wix after Google retired how-to rich results
- Review and AggregateRating schema: star ratings in Google search results
- Article and BlogPosting schema: author, datePublished and E-E-A-T signals
- Product schema for Wix eCommerce: price, availability and rich product listings
- Event schema: show dates and event details directly in Google
- VideoObject schema: get your videos indexed and appearing in video rich results
- Testing and validating schema with Google's Rich Results Test and Schema.org validator
- Duplicate content, canonical tags and Wix pagination
- Wix JavaScript rendering: how Googlebot processes your Wix site differently
- Service, ProfessionalService and SameAs schema for Wix businesses
- 301 redirects, crawl errors, hreflang and robots.txt on Wix
- Using ChatGPT, Claude and AI tools to generate schema, redirects and structured data for Wix
- SpeakableSpecification schema for voice assistants on Wix
- noai and noimageai robots meta tags: controlling AI content usage on Wix
- NLWeb protocol: making your Wix site queryable by AI agents
- Model Context Protocol: your Wix site as an MCP server
- Wix AI-generated structured data for blog posts: automatic schema markup
- Wix robots meta tags deep dive: controlling exactly how Google indexes every page
- Scalable structured data: updating all pages of the same type in one action
Was this lesson useful?
It takes 1 minute to tell me. The course is free and I want to keep it that way, and your feedback shows me what is working and helps other people find it.
This lesson on Core Web Vitals field data on Wix: understanding CrUX and real-user metrics is part of Module 6: Technical SEO, Structured Data & Rich Snippets for Wix in The Most Comprehensive Complete Wix SEO Course in the World (2026 Edition). Created by Michael Andrews, a Wix Marketplace Legend Partner with 14 years of hands-on experience, 805 completed Wix SEO projects and 459 verified five-star reviews.