Data source

Data from Google Chrome Developers, delivered clean.

1 dataset pulled from Google Chrome Developers's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.

  • 1 dataset
  • 1 industry
  • Real rows on request

What Datadory delivers from Google Chrome Developers

1
Interactive Home Entertainment Worldwide real-user measurement with per-coun… · Monthly history back to 2017

Chrome UX Report (CrUX)

Pick a catch, see the rows.

Name any Google Chrome Developers dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.

Get a sample

API, files, or your warehouse. Daily, weekly, or hourly.

Straight answers about Google Chrome Developers data

What does Datadory deliver from Google Chrome Developers?

One Interactive Home Entertainment dataset, the Chrome UX Report, shipped as six named deliverables: the Core Web Vitals spine with histogram bins plus p75 per origin or page, device-class cuts, monthly history back to 2017, overlapping weekly periods of roughly ten months, a rolling 28-day view, and supporting context metrics such as navigation types and round-trip-time bands.

How far back does the history go?

Monthly partitions reach back to 2017 - nearly a decade of page-experience record. Between that archive and the present sit overlapping weekly periods spanning roughly ten months and a rolling 28-day window carrying the current state. Scheduled captures extend any depth forward at whatever cadence your study needs.

Why are some origins missing from the data?

Eligibility is earned with traffic. Only publicly discoverable origins busy enough to aggregate statistically appear, so quiet or newly launched sites are absent because there is too little traffic to measure, not because anything is broken. The rule is what makes presence citable: every included origin passed the bar.

Can competitor origins be benchmarked head to head?

Yes, and it is the sharpest use of the source. Every origin sits on identical traffic-weighted scales, so your storefront's p75 LCP can be placed beside a rival's per device class on the same observation window. No normalization project stands between you and the comparison, because the measurement frame is already common.