-
Notifications
You must be signed in to change notification settings - Fork 9.3k
Issues: GoogleChrome/lighthouse
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Audit proposal: Detect if React is development mode
good first issue
new_audit
P2
#9511
opened Aug 5, 2019 by
connorjclark
UX for errors caused by Lighthouse is unclear
needs-design
P2
report
#9968
opened Nov 13, 2019 by
connorjclark
Consider JS evaluation costs in efficiency audits
needs-design
needs-investigation
P2
simulation / lantern
#10089
opened Dec 11, 2019 by
connorjclark
visual representation of page weight by resource type
feature
needs-design
P2
report
#10356
opened Feb 19, 2020 by
connorjclark
audit proposal: http header best practices
new_audit
P3
trust and safety
#8659
opened Apr 27, 2019 by
connorjclark
For legacy-javascript advice, suggest excluding some polyfills for "modern" build
P2
#10945
opened Jun 11, 2020 by
connorjclark
Ensure running lighthouse with external emulation should work with full-page-screenshot
P3
#11122
opened Jul 17, 2020 by
connorjclark
Convert Critical request chains to use lantern LCP graph
P3
#11408
opened Sep 10, 2020 by
connorjclark
--only-audits incorrectly emits warning if audit is not in a category
bug
P3
#11531
opened Oct 7, 2020 by
connorjclark
Previous Next
ProTip!
Follow long discussions with comments:>50.