-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Move perf metrics into performance section #1876
Comments
Do we have a public note about why we're extending TTI's budget to < 10s? (just for historical context as folks look at how/why metric budgets have evolved). |
@addyosmani there's two separate "audits" here A) A boolean audit saying "is the TTI faster than 10s?". This is to mirror this item in the baseline checklist: B) sharing the value and scoring of TTI, along with the other key perf metrics. The scoring over here is separate and we can handle completely independently from the PWA requirement. FYI: With our current scoring curve (which honestly hasn't been validated), a 9900ms TTI gets a score of 11%. That seems a tad low, but I'm also okay with Lighthouse perf section having much higher standards for perf than the hard boolean requirements of PWA-ness. |
This is already done in the categories landing of config v2. OK to close @paulirish or was there more to it (UI perhaps?) than just moving them out? |
yah sgtm. |
once Add TTI < 10s audit for PWA #1840 is done, we can move perf metrics to their real home, out of the PWA section.
The text was updated successfully, but these errors were encountered: