Reminder that this changed rolled out in Chrome 133.
If you’re seeing worse LCP times and load your LCP images from another domain (and didn’t have the TAO header set) then that could be why.
Read the full thread for details.
If you’re seeing worse LCP times and load your LCP images from another domain (and didn’t have the TAO header set) then that could be why.
Read the full thread for details.
Reposted from
Barry Pollard
We’re therefore intending to change this to allow the proper LCP time to be exposed (though coarsened a little to be accurate to within a few milliseconds rather than the exact time).
This will mean you can get the (approximate) LCP time even without setting the TAO HTTP header! 🎉
This will mean you can get the (approximate) LCP time even without setting the TAO HTTP header! 🎉
Comments
https://developer.mozilla.org/en-US/docs/Web/API/LargestContentfulPaint/renderTime#browser_compatibility
And https://web.dev:
https://web.dev/articles/lcp#load-render-time
And the LCP reported by Chrome 133 is the correct one (within a few ms)! This is not a regression, but an increase in accuracy.