-
Notifications
You must be signed in to change notification settings - Fork 9.6k
tests: refresh sample artifacts #15962
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
Conversation
| score: 0, | ||
| metricSavings: {'FCP': 15}, | ||
| metricSavings: {'FCP': 2000}, | ||
| ...defaultAuditRef, |
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.
why are these changes so large?
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.
With the new artifacts, 15ms is a negligible change to FCP which results in a 0 for it's overall impact. Using larger numbers ensures that the savings at least register a pulse on our overall impact calculations.
Wouldn't recommend opening any of the artifact/sample JSON diffs :)
This was a simple
yarn update:sample-artifactsfollowed byyarn update:flow-sample-json -aOld report: https://lighthouse-googlechrome.vercel.app/sample-reports/english/
Report on this branch: https://lighthouse-2b4j6cvtp-googlechrome.vercel.app/sample-reports/english/
Old flow report: https://lighthouse-googlechrome.vercel.app/sample-reports/flow-report/
Flow report on this branch: https://lighthouse-2b4j6cvtp-googlechrome.vercel.app/sample-reports/flow-report/