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
TraceElements: impactedNodes
is not iterable
#15870
Labels
Comments
adamraine
changed the title
pagespeed insights website error analyzing webpage
TraceElements: Mar 20, 2024
impactedNodes
is not iterable
I can reproduce this but not consistently. Looks like What's weird is that we handle the undefined/null case so in theory this isn't possible:
|
Artifacts from failing PSI run impacted-nodes.artifacts.json.gz |
We are experimented the same error in our website => https://pagespeed.web.dev/analysis/https-bigcrafters-com/5sactpqqk8?form_factor=mobile |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FAQ
URL
https://play-best-games.com/atomic-heart/
What happened?
Actually, in lighthouse it works:
However I wanted to report pagespeed.web.dev version, which errors on multiple checks
What did you expect?
I expect pagespeed.web.dev to show same results as browsers lighthouse feature or at least show the checks results properly, without error.
What have you tried?
I have really no idea, what should I try on my side to debug lighthouse behavior.
Please suggest.
How were you running Lighthouse?
web.dev
Lighthouse Version
i used the version that is used on pagespeed.web.dev
Chrome Version
122.0.6261.129
Node Version
OS
Windows 11
Relevant log output
The text was updated successfully, but these errors were encountered: