-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
docs: add v8.0 Performance FAQ #12597
Conversation
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.
📜 ❓ 🎯
to TBT changes in the long tail and the windowing of CLS, and both metrics' | ||
higher weights. | ||
|
||
### What are the exact score weighting changes? |
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.
aw, the github table formatting is kind of a bummer. Maybe throw some italics on the v6 weights column to deemphasize? Should we separate the phase weights somehow (separate table? put the metric names in the middle with different weights on each end?) to make it more readable?
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.
attempted something. added some italics on all the phases. i can also try splitting the table out.
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.
attempted something. added some italics on all the phases. i can also try splitting the table out.
ah, looks great split like that. Sorry to send you down this rabbit hole. Github really just needs to add one or two more table styling options
the best incentives to improve overall page experience for users. | ||
|
||
LCP, CLS, and TBT are [very good | ||
metrics](https://chromium.googlesource.com/chromium/src/+/lkgr/docs/speed/good_toplevel_metrics.md) |
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.
LCP, CLS, and TBT are very good
metrics
|
||
### What's the story with TTI? | ||
|
||
TTI serves a useful role as it's the largest metric value reported (often >10 |
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.
TTI serves a useful role as it's the largest metric value reported (often >10 | |
TTI serves a useful role as it's the longest metric value reported (often >10 |
maybe?
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.
feels weird as longest. but also weird as largest. ohwell
and that's why they are the three highest-weighted metrics in the performance | ||
score. | ||
|
||
### How should I think about the Lighthouse performance score in relation to Core Web Vitals? |
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.
bump on my offer :)
Co-authored-by: Brendan Kenny <bckenny@gmail.com>
Co-authored-by: Patrick Hulce <patrick.hulce@gmail.com>
add standalone faq md, and linking it into the v8.0 changelog notes
faq is currently previewable here: https://github.com/GoogleChrome/lighthouse/blob/v8changelog-faq/docs/v8-perf-faq.md
to merge into #12596 (which merges into #12593)