The 202209 dataset is live

[Barry Pollard]

Hi CrUX users,

This is your monthly announcement that the latest dataset has been published to BigQuery.

The 202209 (September 2022) dataset is now available and it covers 17,715,277 origins, an increase of 5.7% over last month. Here’s a look at origins' Core Web Vitals performance this month:

• 54.5% of origins had good LCP

• 94.8% of origins had good FID

• 72.4% of origins had good CLS

• 41.4% of origins had good LCP, FID, and CLS

The CrUX API now includes a collectionPeriod object with firstDate and endDate fields representing the beginning and end dates of the aggregation window. An example is provided below:

    "collectionPeriod": {

      "firstDate": {

        "year": 2022,

        "month": 10,

        "day": 9

      },

      "lastDate": {

        "year": 2022,

        "month": 9,

        "day": 12

      }

    }

This allows better understanding of the data and whether it's been updated yet for that day or is returning the same data as yesterday.

Note that the CrUX API is approximately two days behind today's date since it waits for completed data for the day, and there is some processing time involved before it is available in the API.

The new collectionPeriod object has been added to our documentation at https://developer.chrome.com/docs/crux/api/.

Other recent CrUX-related updates:

• A team of researchers at Stanford University and Cloudflare published Evaluating the Accuracy of Popular Website Lists, which noted that CrUX data is significantly more accurate than other data sources.

• The web-vitals library released v3 which includes the new INP metric and built-in attribution to help identify elements causing issues with your metrics.

• Barry Pollard wrote Why is CrUX data different from my RUM data? recently to understand why you may see differences in these datasets.

• Jeremy Wagner wrote a guide on Optimizing Long Tasks, which can help you improve your FID and INP metrics.

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/CrUX on GitHub

Cheers,

Barry