Open
Bug 1890599
Opened 11 months ago
Updated 8 months ago
LCP end timestamp doesn't include composition time
Categories
(Core :: Performance Engineering, defect)
Core
Performance Engineering
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
References
(Blocks 1 open bug)
Details
From bug 1889717 we're collecting the timestamp that we report for LCP when we finish building the display list this doesn't match Chrome which is using the presentation time. This means our LCP times are artificially lower than Chrome's and makes it more difficult to compare.
|
Reporter | |
Comment 1•11 months ago
|
||
It seems like this is more controversial than I originally thought. See https://github.com/web-platform-tests/interop/issues/215 which links to https://www.catchpoint.com/blog/why-first-contentful-paint-doesnt-work-as-a-cross-browser-metric
|
||
Updated•9 months ago
|
Component: Performance → Performance Engineering
|
||
Comment 2•8 months ago
|
||
The severity field is not set for this bug.
:fdoty, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(fdoty)
|
||
Comment 3•8 months ago
|
||
Marking as S3 as we haven't discussed the impact or a path forward
Severity: -- → S3
Flags: needinfo?(fdoty)
You need to log in
before you can comment on or make changes to this bug.
Description
•