You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sentry reports the LCP value for a page load and the LCP element that contributed to the value. However, the LCP value for the pageload itself does not match with the end of the span of the LCP element in the waterfall
Expected Result
I would expect the LCP element span to finish at the same timeframe as the reported value of the LCP vital for the page load
Actual Result
The LCP element span finishes way before the time that Sentry reports as the LCP for the pageload
The text was updated successfully, but these errors were encountered:
serglom21
changed the title
LCP element span does not correlate with LCP vertical mark for trace in waterfall
LCP element span does not correlate with LCP vertical mark in waterfall
Aug 16, 2024
This might be related to some weird LCP/FCP/FP value normalization code we have in the SDK. I will investigate if we can remove this logic as it's massively screwing up web vital accuracy.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/remix
SDK Version
8.25.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
Customer Case
Sentry reports the LCP value for a page load and the LCP element that contributed to the value. However, the LCP value for the pageload itself does not match with the end of the span of the LCP element in the waterfall
Expected Result
I would expect the LCP element span to finish at the same timeframe as the reported value of the LCP vital for the page load
Actual Result
The LCP element span finishes way before the time that Sentry reports as the LCP for the pageload
The text was updated successfully, but these errors were encountered: