Post

Barry Pollard
@tunetheweb.com

So the CrUX Dashboard uses the CrUX BigQuery data set. This has some differences to the CrUX API which powers CrUX Vis: - Only updated monthly (and only on 2nd Tuesday so up to 13 days behind even then) - Origin only - Slower to query - Missing some data (e.g. LCP subparts that we launched recently)

Barry Pollard
@tunetheweb.com

Querying that from Looker Studio is also suffering from some reliability issues and isn't really meant for the scale it's being used for. Hence why we build CrUX Vis based on the CrUX History API which doesn't suffer from those issues even at scale.

0 reposts1 like

Barry Pollard
@tunetheweb.com

Those reliability issues also partially explain why we haven't added more data (like LCP subparts) to the Dashboard. It would just exacerbate the problem! So we do want to deprecate the CrUX Connector powering the Looker Studio dashboard And CrUX Vis is our attempt at a replacement for that.

Barry Pollard
@tunetheweb.com

You could still query the CrUX BigQuery dataset yourself if you really wanna keep the dashboard, but it won't be free like the CrUX Connector unfortunately. The data it needs is cheap to query and should be within the 1TB BigQuery free monthly limit for most users, but the CrUX Connector was free 😔

Barry Pollard
@tunetheweb.com

Alternatively, the CrUX History APIs are free and you can build your own dashboards as you see fit. There are also LOTS of great CrUX tools out there — many with a free offering to view history such as Treo, Calibre...etc. So that's another option.