-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Why is FCP greater than LCP ? #2200
Comments
Hi @pschonmann check if the LCP element is the correct element. If so, you can report Chrome bugs direct in https://issues.chromium.org/issues . If it seems to be the wrong element for LCP, let me know. |
Im not sure if its only chromium thing. Im getting these weird results in Firefox and Edge -b option too. Anyway LCP seems to be identified okay.
|
Edge and Chrome use same codebase. You can report bugs for Firefox in https://bugzilla.mozilla.org. So the FCP and LCP is picked up from the browsers API:s, checkout https://w3c.github.io/paint-timing/#first-contentful-paint and https://w3c.github.io/largest-contentful-paint/#sec-largest-contentful-paint-interface, the values are not touched in Browsertime/sitespeed.io, they are picked up directly from the browser. |
Your question
FCP is greater than LCP, that doesnt make sense
The text was updated successfully, but these errors were encountered: