Feature request: add TTFB to CRuX API

[Aaron Peters]

Hi,

The CRuX API is *great* and so much nicer (faster!) to use compared to the PSI API.

I'd love to see the API expose more metrics and be more on par with what is available in BigQuery: TTFB, DCL and OL.

Of all the missing metrics, I believe TTFB is the most important: 

• high TTFB always hurts the user experience: until those first bytes arrive, the browser can't give the user anything useful (e.g. show the <title> in the tab)
• high TTFB directly impacts LCP: it's bad for one of the three Core Web Vitals
• high TTFB is typically caused by high network latency and/or high server response times: devs know "it's not just the front-end" and should know what next steps to take

Please add TTFB to the CRuX API and keep up the good work!

Aaron

[Rick Viscomi]

Hi Aaron,

Thanks for submitting this feature request! It's very helpful to hear your reasoning for why you'd like to see TTFB in the API response. I'll forward this to the API team and let you know when I have any updates.

And if anyone else is interested in this feature, please feel free to reply with "+1" or let us know how this feature would be useful to you.

Rick

[Louis Dubruel]

+1 for TTFB !!

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/e794f523-3cea-4454-b5e6-98db96fec2d7o%40chromium.org.

[Matthew Hobbs]

+1 for TTFB. I personally use the CrUX data to find information about government services from other departments. This is information not readily available due to the complexities of government. TTFB would allow me to identify if a performance issue is backend or frontend related, and thus allow for much more productive conversations.

[Anthony RICAUD]

+1 as well for TTFB.

Internally, we've started tracking the difference between LCP and FCP to get a feel for a regression/improvement in the HTML/assets side of things. Tracking the difference between LCP and TTFB would be a better metric to track.

[Padma Chintamaneni]

+1

 

Padma Chintamaneni

Lead Performance Analyst

 

Cell: +91 9703039276   Email: padma_chi...@epam.com

Hyderabad, India (GMT+6)   epam.com

--

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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/fb3bb524-2944-43ca-a08c-eef7da21d39bn%40chromium.org.

[Ryan Siddle]

+1 for all of the previous comments.

 

On a slight side note, for those who have the ability to ingest data into their RUM dashboards and data warehouses, check out the web-vitals.js[0] open source project that provides, CLS, FCP, FID, LCP, TTFB. The data comes in real-time from your users, so it would be a case of rolling the data up to make it meaningful. It also helps to capture daily URL data that isn’t available via the API. In particular, we have found that analysing at page type level rather than individual URLs provides more robust data. Consider pulling in the geographic region (geo-IP lookup) to provide a country-level segmentation too.

 

[0] https://github.com/GoogleChrome/web-vitals

 

Best regards,

 

Ryan

 

Ryan Siddle / Digital Director
ryan....@merj.com

Merj
+44 (0) 2033 222 660 / Ext: #101
9th Floor, 1 Ropemaker Street, London, EC2Y 9HT
merj.com

 

 

 

From: chrome-u...@chromium.org <chrome-u...@chromium.org> on behalf of Anthony RICAUD <rik...@gmail.com>
Date: Thursday, 28 January 2021 at 10:30
To: Chrome UX Report (Discussions) <chrome-u...@chromium.org>
Cc: Matthew Hobbs <matthe...@digital.cabinet-office.gov.uk>, Rick Viscomi <rvis...@google.com>
Subject: [CrUX Discuss] Re: Feature request: add TTFB to CRuX API

--

[Ludovic Lefebvre]

+1 it will be so usefull to have the server metric for client side.

Best, 

Ludovic

[Greg Wolf]

+1 for TTFB

[Joseph Scott]

Adding my +1 to including TTFB in the CRuX trailing 28 day API.

Reasoning behind this is that out of the three core web vital metrics the one we have the most work to do to get into the green is LCP.  Having metrics that come before LCP are helpful in narrowing down where to focus our work.  Since LCP can't be any faster than TTFB, it would be really helpful to know what CRuX is seeing there.

[Martin Michálek]

+1 for TTFB

[Rick Viscomi]

Hi everyone,

I'm happy to update that as of today TTFB is being served from the CrUX API. See today's announcement for more info.

Thanks for all of your feedback!

Rick

[Aaron Peters]

Yeah Rick, this is great, txs!

[Karolina]

I'm also very excited about TTFB being accessible now, great work everyone involved! We added it to our Core Web Vitals (and other notable metrics 😉) checker too.

[Anthony RICAUD]

Thanks for adding this metric! I'm also very happy to see INP landing in BigQuery and the API at basically the same time. This is terrific.