Question on accessing TTFB and INP data after Looker Studio deprecation
Onitkar Sharma
Hi everyone,
I had a question regarding how TTFB and INP data are currently being calculated and accessed in the Chrome UX Report.
Previously, I relied on Looker Studio dashboards to view and analyze these metrics, but since their deprecation, I’m no longer able to retrieve this data the same way. I’m trying to understand:
How are TTFB and INP metrics being calculated in CrUX now?
What’s the recommended way to access or query this data going forward?
Are there any alternative dashboards, APIs, or tools that replicate what Looker Studio previously provided?
Any guidance or pointers to updated documentation would be really helpful.
Thanks in advance!
Chau Tran
Dear Onitkar,
TTFB and INP in the Chrome UX Report (CrUX) continue to be based on anonymized field data from real Chrome users who have opted in to syncing browsing history and have usage statistics reporting enabled. The main change is that the pre-built Looker Studio dashboards/templates are no longer the recommended access path.
1) How TTFB and INP are calculated in CrUX
- Aggregation window: CrUX publishes a rolling 28-day distribution of experiences for an origin (and, where available, URL-level data).
- Reported values: Metrics are exposed as distributions (histograms) plus summary statistics (commonly P75).
- INP: Interaction to Next Paint is computed from user interactions and represents the latency from input to the next paint, summarized at the page level. Core Web Vitals thresholds are typically: Good ≤ 200 ms, Needs improvement ≤ 500 ms, Poor > 500 ms.
- TTFB: Time to First Byte represents the latency from navigation request until the first byte of the response is received for the document request. Common thresholds used in CWV tooling are: Good ≤ 800 ms, Needs improvement ≤ 1,800 ms, Poor > 1,800 ms.
2) Recommended ways to access/query the data going forward
- CrUX API: Best for programmatic access for a given origin (and, where supported, URL). You can request INP and TTFB along with other metrics and retrieve histogram + percentile values.
Documentation: https://developer.chrome.com/docs/crux - CrUX BigQuery dataset: Best for analysis at scale, custom reporting, time series, segmentation (e.g., device form factor), and recreating dashboards. The public dataset exposes monthly tables and materialized views you can join/aggregate as needed.
Entry point: https://developer.chrome.com/docs/crux/bigquery
3) Alternatives to the deprecated Looker Studio dashboards
- Build your own Looker Studio report: You can replicate the previous dashboards by connecting Looker Studio to BigQuery (recommended for flexibility) or by using the CrUX API via a community/connector approach. This keeps the same visualization workflow while using the supported data sources.
- PageSpeed Insights (for quick checks): Provides CrUX-based field data (including INP and, where available, TTFB) for a URL/origin without building a dashboard.
https://pagespeed.web.dev/
If your previous Looker Studio report is now showing “No data,” it is typically due to the underlying CrUX data source/template being discontinued or schema/field changes (e.g., TTFB sometimes being represented under an “experimental” namespace depending on the surface). Repointing the report to BigQuery (CrUX dataset) is the most durable replacement.
Sincerely,
Chau Tran
 | Email sent via Mail Agent |
Barry Pollard
How are TTFB and INP metrics being calculated in CrUX now?
What’s the recommended way to access or query this data going forward?
Are there any alternative dashboards, APIs, or tools that replicate what Looker Studio previously provided?
--
You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ux-repo...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/437d56fe-5976-48ef-a113-7840e6733635n%40chromium.org.
Chau Tran
Dear Onitkar,
You are correct—TTFB and INP are not being calculated differently. The change is primarily in how you access and visualize CrUX data now that the hosted Looker Studio CrUX dashboards/templates were deprecated.
Recommended ways to access/query TTFB and INP going forward
- CrUX API (programmatic, per-origin / per-URL where available):
Use this when you want to fetch current 28-day aggregated distributions/percentiles for specific origins/URLs and integrate into your own tooling.
https://developer.chrome.com/docs/crux/api - CrUX BigQuery dataset (analysis at scale, custom dashboards):
Use this when you need historical/monthly tables, segmentation, and the ability to recreate dashboards reliably in Looker Studio by connecting directly to BigQuery.
https://developer.chrome.com/docs/crux/bigquery - CrUX Vis (dashboard-style UI with weekly data):
This is the closest first-party “dashboard” experience now, with a different cadence (weekly).
https://cruxvis.withgoogle.com/#/
Alternatives that replicate the previous Looker Studio dashboard experience
- Self-managed Looker Studio dashboard: You can still use Looker Studio, but you must manage the data source yourself (typically by using BigQuery in your own Google Cloud project and pointing Looker Studio at those tables). This is outlined in the deprecation post.
https://developer.chrome.com/blog/crux-dashboard-deprecation - Third-party tools: Some products surface CrUX monthly data (e.g., treo.sh).
About the “No data” cards shown in your screenshots
That behavior is consistent with using a Looker Studio report that is still tied to the deprecated CrUX dashboard/data source (or fields that no longer resolve). The durable fix is to migrate the report to a supported source (BigQuery-backed tables in your own project, or use CrUX Vis for visualization).
Sincerely,
Chau Tran