Skip to content

tests: refresh sample artifacts#15962

Merged
adamraine merged 9 commits intomainfrom
refresh-sample-artifacts
Apr 19, 2024
Merged

tests: refresh sample artifacts#15962
adamraine merged 9 commits intomainfrom
refresh-sample-artifacts

Conversation

@adamraine
Copy link
Copy Markdown
Contributor

@adamraine adamraine commented Apr 17, 2024

Wouldn't recommend opening any of the artifact/sample JSON diffs :)

This was a simple yarn update:sample-artifacts followed by yarn update:flow-sample-json -a

Old 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/

@adamraine adamraine requested a review from a team as a code owner April 17, 2024 21:56
@adamraine adamraine requested review from connorjclark and removed request for a team April 17, 2024 21:56
score: 0,
metricSavings: {'FCP': 15},
metricSavings: {'FCP': 2000},
...defaultAuditRef,
Copy link
Copy Markdown
Collaborator

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?

Copy link
Copy Markdown
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants