HTTP-429 on Lighthouse reports when running via WebPageTest · Issue #6002 · GoogleChrome/lighthouse · GitHub

Some of out tests are breaking because of following error. This test was run via a private instance of WebPageTest. Unfortunately, I do not have access to the agent machine so I cannot find lighthouse version but since the WPT agent is i

Lighthouse cannot get a Performance score ~30% of the time · Issue #9107 · GoogleChrome/lighthouse · GitHub

PageSpeed Insights HTTP/2 Issue · Issue #12228 · GoogleChrome/lighthouse · GitHub

Performance and pwa not reporting. Also results in others are not correct. · Issue #5463 · GoogleChrome/lighthouse · GitHub

Getting Avoid multiple page redirects for Desktop report but mobile works just fine · Issue #13425 · GoogleChrome/lighthouse · GitHub

Not able to generate the lighthouse audit report · Issue #13236 · GoogleChrome/lighthouse · GitHub

Using Google Lighthouse to improve app performance

GitHub - GoogleChrome/lighthouse-ci: Automate running Lighthouse for every commit, viewing the changes, and preventing regressions

Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_LCP) · Issue #11003 · GoogleChrome/lighthouse · GitHub

LHCI continuously failing with PROTOCOL_TIMEOUT error · Issue #428 · GoogleChrome/lighthouse-ci · GitHub

Running lighthouse (Chrome Audit) switches into mobile emulation automatically · Issue #3186 · GoogleChrome/lighthouse · GitHub

Not able to generate the lighthouse audit report · Issue #13236 · GoogleChrome/lighthouse · GitHub