GoogleChrome / GoogleChrome/lighthouse
a
- Dominant language
- JavaScript
- Stars
- 30.8k
- Forks
- 9.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 20
Description
### FAQ
- [x] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [x] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [x] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#faq).
### URL
https://glitch.com/, http://jsbin.com/
### What happened?
aaa
### What did you expect?
aaaa
### What have you tried?
aaa
### How were you running Lighthouse?
Chrome DevTools
### Lighthouse Version
1
### Chrome Version
_No response_
### Node Version
_No response_
### OS
_No response_
### Relevant log output
```sh
```
Contributor guide
Research direction
Start by reproducing the report against https://glitch.com/ and http://jsbin.com/ in Chrome DevTools with Lighthouse version 1. Compare the observed “aaa” result with the expected “aaaa” result and capture the missing Chrome, Node, and OS versions plus logs. Done means the behavior is reproducible and the affected audit or expected outcome is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100