[CrUX Announce] The 202006 dataset is live

['Rick Viscomi' via chrome-ux-report-announce]

Hi CrUX users,

This is your monthly announcement that the latest dataset has been published to BigQuery. The 202006 (June 2020) dataset is now available and it covers 7,501,835 origins, a 5.6% increase over last month's record-setting dataset size!

Here's a look at origins' Core Web Vitals performance in June 2020:
Note the correction to last month's assessment.

• 47.84% of origins had good LCP
• 86.74% of origins had good FID
• 57.45% of origins had good CLS
• 25.34% of origins had good LCP, FID, and CLS

What's new in this dataset:

• User experiences served from Google's AMP cache are now attributed to the publisher's origin in CrUX. Effects will vary depending on the amount of AMP cache traffic relative to the rest of the website, but most origins see less than a 5 percentage point change in Core Web Vitals performance, with most effects being positive.

There are two community resources to highlight this month:

• Mastering CrUX on BigQuery by Rick Viscomi (me), a video walkthrough of advanced CrUX use cases
• core-web-vitals.now.sh by Alex Loaiza, a web UI for querying and visualizing the CrUX API

If you have any questions about CrUX, feel free to reach out to us on any of these channels:

• chrome-ux-report on Google Groups
• @ChromeUXReport on Twitter
• questions tagged with chrome-ux-report on StackOverflow
• GoogleChrome/ChromeUXReport on GitHub
  

Cheers,

Rick

[Mohit Maini]

Hi Rick

This CrUx report update for every month is useful for knowing how a particular Origin is performing for Core Web Vitals.

However, we always refer to Field Data to know about individual page performance. And in Search Console as well data is aggregated by Field.

So how is this Origin Report contributing to Field Data and does it affect field data in any way?

[Rick Viscomi]

Hi Mohit,

If I understand the question correctly, you're asking how representative the data aggregated by origin is of real-user performance, as opposed to the URL-level aggregations available in PSI, Search Console, and the CrUX API. The answer is that they're both equally valid ways of aggregating user experience data, and they tell different stories about the experience.

URL-level data will help you identify whether a page has UX issues. Origin-level data will tell you whether experiences as a whole on your website are good. Some pages are more popular than others, so origin-level aggregations are an effective way of factoring in those popularity differences.

Hope that answers your question!

Rick