-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add redirect time to TTFB breakdown #395
Comments
Decided to add as additional experimental breakdowns:
We will leave So adding up the 6 metrics will not equal the total and need to add either |
Good morning Barry, here is the version I use. It's more in line with the https://www.w3.org/TR/navigation-timing-2/#processing-model Feel free to use .... or not :-) attribution/onTTFB.js
and types/ttfb.js
|
Hey @tunetheweb + @philipwalton given that the first 4.0-beta has been cut, is it fair to guess that |
This would be a nice one to get in before v4 since it would be a breaking change if we change waitingTime. Will have a look this week and see if we can add to v4. |
Completed (as best as is possible) in #458 |
Redirects can cause considerable impact to LCP times. We should add this to TTFB attribution.
Note concerns have been raised that this is a cross-origin leak and so may be removed from Web APIs, but if that happens that will need to lead to discussions on the wider impact to Core Web Vitals (can you measure LCP accurately without this or do redirects have to move outside of LCP then?)
Also what to do with the current
waitingTime
measure which currently includes redirect time? Do leave as is to avoid making a breaking change? Or change in the next major release to subtract redirect time from this. Redirect time is also only part of what it measures and from the PerformanceNavigationTiming there's also unload time before it, and service worker and HTTP Cache time after it. So should they all be included and waitTime be full deprecated (but remain as is for now)?The text was updated successfully, but these errors were encountered: