Skip to content
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

FCP higher than LCP on individual page loads #13407

Open
3 tasks done
serglom21 opened this issue Aug 16, 2024 · 2 comments
Open
3 tasks done

FCP higher than LCP on individual page loads #13407

serglom21 opened this issue Aug 16, 2024 · 2 comments
Labels
Feature: web-vitals Package: remix Issues related to the Sentry Remix SDK

Comments

@serglom21
Copy link

serglom21 commented Aug 16, 2024

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

Image

@Lms24
Copy link
Member

Lms24 commented Aug 19, 2024

backlogging to triage after hackweek

@Lms24
Copy link
Member

Lms24 commented Aug 28, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: web-vitals Package: remix Issues related to the Sentry Remix SDK
Projects
Status: Waiting for: Product Owner
Development

No branches or pull requests

3 participants