Lighthouse-ci results differs from lighthouse itself
See original GitHub issueHi everyone, it seems that are some issue with lighthouse-ci results in comparison with lighthouse itself. When I ran lhci autorun
it gives me an error related to NO_FCP
, but if I use the same lighthouse that is installed through lhci (that one stored on node_modules
folder), it works properly:
If I ran using lhci autorun
it gives me the NO_FCP
error. I also tried to use the --no-sandbox
flag but got no luck.
Do you have any idea? Am I missing something? Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7
Top Results From Across the Web
Performance monitoring with Lighthouse CI - web.dev
Lighthouse CI is a suite of free tools that facilitate using Lighthouse for performance monitoring. A single Lighthouse report provides a ...
Read more >Why is my Lighthouse score different from PageSpeed Insights?
When running Lighthouse on your computer or on DebugBear the Performance score may be different from what you see on PageSpeed Insights.
Read more >You're probably using Lighthouse wrong | Vue Storefront
The Lighthouse score is calculated from a bunch of other metrics' scores. Each of them has its own weight - some of them...
Read more >Lighthouse meets GitHub Actions: How to use Lighthouse in CI
If a pull request impacts usability or performance, seeing those details in the context of our pull request is exactly where we'd like...
Read more >Lighthouse - DEV Community
Lighthouse Score for Pages behind Authentication with Selenium ... Continuous performance checks in Nuxt.js with Lighthouse CI and Github Actions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @patrickhulce it might be something related to my node version, I was using node 12, I switched to node 10 and it’s working:
I think that we can close this ticket, thank you for your help 😃 Regards.
Closing this ticket since the node 10 version fixed the issue.