-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
LCP element span does not correlate with LCP vertical mark in waterfall #13408
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
Comments
Backlogging to triage after hackweek |
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. |
@serglom21 do you have an update if after updating to a more recent SDK version the problem still persists? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
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: