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
On individual events of page loads for Remix, I am seeing that the measurement for FCP is higher than LCP in some cases
It seems that a similar issue was reported on previous versions of the SDK but that was closed since it seems that v7 fixed it. But we are seeing the same discrepancy in v8
Expected Result
I would expect FCP to always be lower than LCP
Actual Result
FCP is higher than LCP in some cases
The text was updated successfully, but these errors were encountered:
So this is still a bit concerning as I haven't yet found a reason as to why it would happen consistently. Some notes:
Based on my understanding of LCP, it should never be lower than FCP. It might be equal to - whenever there LCP element happend in the same paint as FCP - but never lower.
We do have some LCP value "normalization" logic, which I'm gonna experiment with removing but the same logic also applies to F(C)P. So theoretically, this code path should mess up both values equally but not reduce one more than the other one 😅. But maybe I'm missing something and removing this logic solves it too.
There are cases when LCP is reported lower by the SDK than by web vitals. Specifically, this is expected when a new LCP element is rendered after the pageload span finishes. The fix for this is Send Standalone LCP spans #13063
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
On individual events of page loads for Remix, I am seeing that the measurement for FCP is higher than LCP in some cases
It seems that a similar issue was reported on previous versions of the SDK but that was closed since it seems that v7 fixed it. But we are seeing the same discrepancy in v8
Expected Result
I would expect FCP to always be lower than LCP
Actual Result
FCP is higher than LCP in some cases
The text was updated successfully, but these errors were encountered: