Hi CrUX users,
This is your monthly announcement that the latest dataset has been published to BigQuery.
The 202311 (November 2023) dataset is now available and it covers 18,265,721 origins, a decrease of 0.6% over last month. Here’s a look at origins' Core Web Vitals performance this month:
59.8% of origins had good LCP
96.0% of origins had good FID
76.2% of origins had good CLS
47.4% of origins had good LCP, CLS and FID
79.2% of origins had good INP
43.9% of origins had good LCP, CLS and INP
More improvements across most of the metrics this month, though this time we’re not aware of any particular changes to attribute this to.
Our documentation moved infrastructure similar to the web.dev move in October. A huge benefit of this is that the CrUX documentation (and all other Chrome documentation) is available in 20 additional languages through machine translation, opening it up to many more people. Please raise an issue if you spot any problems with this site move.
We have a few community shout outs this month:
Henry Price for his post in the annual Web Performance Calendar on how to Monitor Performance Using Google Sheets and CrUX History API.
Undoubtedly there will be other interesting posts in the Web Performance Calendar over the month of December so keep an eye on that. Or, better yet, contribute your own post that you think the webperf community could benefit from. Shout out to Stoyan Stefanov for running it all these years.
Estela Franco for her talk on Challenging Assumptions About LCP Best Practices (with data!) from PerfNow which is now available to view online. It contains interesting insights from CrUX on LCP data, a sneak preview of some upcoming changes in CrUX. It also contains some perhaps surprising insights —did you know that downloading images is far from the biggest delay in LCP for images? So if you are not optimizing the parts then you're leaving web performance on the table!
Please find our documentation at https://developer.chrome.com/docs/crux.
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