-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Lighthouse doesn't wait long enough for page to load (NO_LCP) #11180
Comments
Thanks for filing @eduardosada! I'm not able to reproduce this issue though :/ Any other steps or information you can give us that might help? |
I just tried web.dev/measure and sometimes it works and sometimes it doesn't. ¿could you please try again a couple of times? I think it could be a race condition. |
Ah thanks for the example report, in that case it looks like Lighthouse did not wait long enough for the page to completely finish. You can control this from the CLI with the |
Action items here:
|
Would adding a |
From the technical page load perspective yes but lighthouse treats FCP specially so we'll probably still want both for two main reasons.
|
@patrickhulce should we hold this until after fraggle rock? |
I wouldn't delay it just for fraggle rock. The |
Another aspect we'll want to consider when we pick this work back up is waiting for all images with a high priority (signal for above the fold) to finish loading for LCP as well. The test case for this is a page with a single very large image that takes more than our quiet timeouts to load. |
Steps to reproduce
lighthouse https://clientes-bancocaminos.grupocaminos.es
What is the current behavior?
On CLI I get:
largest-contentful-paint:warn Caught exception: NO_LCP
On DevTools I get:
Largest Contentful Paint Error!
Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_LCP)
What is the expected behavior?
I don't expect any errors.
Environment Information
The text was updated successfully, but these errors were encountered: