GoogleChrome / GoogleChrome/lighthouse

Move charset audit from Best Practice to Performance insight

Open
#16,893 1 comment 0 reactions 0 assignees View on GitHub
14.0 breaking
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 20h
Merged PRs (30d)
19

Description

As discussed with @paulirish crrev.com/c/7577714 adds a Performance Insight for this audit for DevTools. Let's retire the Lighthouse audit to remove code duplication.

As part of that, and since Insights can only be used Performance audits, we'll need to move this audit from Best Practice to Performance category. There's good reasons for it to sit in either so think that is fine.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.