core(performance): hide most audits under passing conditions #16315
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.
Closes #16265
Several performance audits follow a pattern where they mark themselves as informative when there isn't a problem, instead of going into a true passing state (i.e. hidden in the "Passed audits" section). Although this pattern is necessary to keep audits like
largest-contentful-paint-element
visible, it's kinda overused which has led to some confusion as mentioned in #16265.This PR removes the "informative on pass" pattern from most audits. The following audits will still use the "informative on pass" pattern because they contain critical information for CWV:
largest-contentful-paint-element
layout-shifts
work-during-interaction
Might be worth keeping the "informative on pass" pattern for
third-party-summary
since 3P payloads could still be high even in a passing state, but that's debatable.