GoogleChrome / GoogleChrome/lighthouse
Clear criteria of non-navigation mode's performance score
- Dominant language
- JavaScript
- Stars
- 30.8k
- Forks
- 9.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 20
Description
**Summary**
Hi, I'm wondering if there are any specific criteria for non-Navigation mode's performance score.
I wrote a Timespan script and ran it before and after the improvement.
What I've realized is the passed and the average script use different score criteria.
If you look at these images, you'll notice that passed one rated out of 13 and the average one rated out of 25.
I want to know why this difference occurs in the same script.


As far as I know, non-Navigation mode calculates its performance score based on the number of passed audits. [reference](https://github.com/GoogleChrome/lighthouse/issues/14290#issuecomment-1215061522)
Then why is this number changing? Is it using different sets of audits depending on its score range?
I want to know clear standards for this. It would be great if anyone shared this reason with me:)
Contributor guide
Research direction
Start by reviewing the non-Navigation mode scoring behavior described in this issue and the referenced discussion in issue #14290. Compare how the Timespan script produces the passed and average scores; done means explaining why the audit counts differ and documenting the applicable scoring criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100