You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing this site I sometimes get a NO_FCP error, even though other runs have successfully complete. I'm not sure what is causing the trace to fail.
Here is a zip file with a full LH run that failed (LH HTML file, log, trace and devtoolslog).
I tried to look at the log and the trace file, but couldn't pinpoint what is happenning. I can confirm this is not specific to me as other testing tools that use Lighthouse also have this issue, such as GTmetrix
How were you running Lighthouse?
CLI
Lighthouse Version
9.3.1
Chrome Version
102
Node Version
16.13.0
OS
Linux
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
I think you are correct in that it is due to the animation, as removing that page animation and re running the test works fine. You can probably close this or mark as duplicated
FAQ
URL
https://www.carbon60.com/managed-cloud/disaster-recovery-and-backup
What happened?
When testing this site I sometimes get a NO_FCP error, even though other runs have successfully complete. I'm not sure what is causing the trace to fail.
Here is a zip file with a full LH run that failed (LH HTML file, log, trace and devtoolslog).
fail.assets.zip
What did you expect?
A succesful LH report.
Here is a sample successful run, done a few moments before the failed one above (LH HTML file, run log, trace and devtoolslog).
success.assets.zip
What have you tried?
I tried to look at the log and the trace file, but couldn't pinpoint what is happenning. I can confirm this is not specific to me as other testing tools that use Lighthouse also have this issue, such as GTmetrix
How were you running Lighthouse?
CLI
Lighthouse Version
9.3.1
Chrome Version
102
Node Version
16.13.0
OS
Linux
Relevant log output
No response
The text was updated successfully, but these errors were encountered: