Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
core: add time-to-first-byte and lcp-breakdown #14941
core: add time-to-first-byte and lcp-breakdown #14941
Changes from 35 commits
7ad95ad
f1e2815
aa7b9c3
05b1533
f0b8c99
1e71d31
89c772a
ae30f5c
befa77d
2665cb4
105b93f
94db20e
9390257
44fdd50
2f2e8db
2d6cf90
acfb79e
5328e61
a57c51f
fc47184
5ebd448
a1acfa1
e98110c
6656fff
8fec330
53d56df
f342e99
32407e8
77433d3
f80ad2e
d2b176e
30b3b61
46887f5
6ca196e
9dd7aab
2a58f89
556d85b
1def483
54059a2
225e437
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 254 in core/audits/prioritize-lcp-image.js
core/audits/prioritize-lcp-image.js#L254
Check warning on line 258 in core/audits/prioritize-lcp-image.js
core/audits/prioritize-lcp-image.js#L258
Check warning on line 30 in core/computed/lcp-image-record.js
core/computed/lcp-image-record.js#L29-L30
Check warning on line 68 in core/computed/lcp-image-record.js
core/computed/lcp-image-record.js#L46-L68
Check warning on line 25 in core/computed/metrics/lcp-breakdown.js
core/computed/metrics/lcp-breakdown.js#L24-L25
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might want to make loadStart/loadEnd
undefined
in these cases. The optimize-lcp article mentions making loadDelay/loadTime 0 (so setting these to ttfb), but that's technically only in the case where no resource outside the original HTML is needed for displaying the text. We don't track how fonts or dynamically added text were loaded, so we don't really know if there was another resource needed or not.FWIW that would follow the approach taken in UKM, where loadStart/loadEnd are null/not recorded when the LCP is text/video (with implicit possible future TODOs for if/when video LCP happens and if text LCP timing is ever worth looking at)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was somewhat worried that this would mess with the lantern metric comparisons. This might be reason enough to just leave it out of the lantern tests for this PR. I will keep the test data of course.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update, looks like lantern testing handles this just fine, I think I might still remove the lantern test stuff from this PR since we might want to regenerate the WPT again, and should probably use a real device.
Check warning on line 49 in core/computed/metrics/lcp-breakdown.js
core/computed/metrics/lcp-breakdown.js#L34-L49