Skip to content
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

Sporadic NO_FCP/NO_LCP errors #14094

Closed
2 tasks done
jorgeluislazo opened this issue Jun 6, 2022 · 2 comments
Closed
2 tasks done

Sporadic NO_FCP/NO_LCP errors #14094

jorgeluislazo opened this issue Jun 6, 2022 · 2 comments

Comments

@jorgeluislazo
Copy link

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

@adamraine
Copy link
Member

I have not reproed this yet, but it's possibly related to #10869 and #13253 since it looks like the page content is animated in somehow.

@jorgeluislazo
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants