adamraine
commented
2 years ago This is working as intended. The page loads too slowly to finish within our time limit. Do you see the following warning at the top of your Lighthouse report?
Closed DavidFekiac closed 2 years ago
adamraine
commented
2 years ago This is working as intended. The page loads too slowly to finish within our time limit. Do you see the following warning at the top of your Lighthouse report?
DavidFekiac
commented
2 years ago Yes I ve seen it. However i dont think that it takes 45 seconds for page to load even under throttled conditions. I also changed the limit using --max-wait-for-load flag and set it to 5 minutes even. The navigation still timed out. We have an autoplay video for desktop version so i could understand that the network activity would confuse the tests, but mobile version is free of this and yet it still does not load within the time limit.
adamraine
commented
2 years ago Lighthouse waits for network quiet before finishing. This means the page must have 0 pending critical requests and no more than 2 pending requests. Critical requests are any request with Hight or VeryHigh priority.
https://www.google-analytics.com/collect is a critical request that doesn't finish within the time limit, so Lighthouse times out.
yogeshgadge
commented
2 years ago This is happening even without the "There were issues..."
Env macOS 12.5.1 node 16 lighthouse 9.6.7
lighthouse https://google.com --only-categories=performance,pwa --view --preset=desktop
results into
LH:status Navigating to https://google.com/ +0ms
LH:waitFor:warn Timed out waiting for page load. Checking if page is hung... +45s
LH:waitFor:warn Page appears to be hung, killing JavaScript... +1s
Unhandled Rejection. Reason: LHError: PROTOCOL_TIMEOUT
LH:ChromeLauncher Killing Chrome instance 12028 +18sReport is never produced.
I see a Finders window and some PWA application added (which is my jira). I see that it installed the same application multiple times.
joelhsmith
commented
10 months ago I had a lot of sites failing (only in Docker hosted in OKD). They had images near and above 1MB. I got my script running by using the flags for blocking images.
--blocked-url-patterns='*.png' --blocked-url-patterns='*.jpg'
It makes some of the tests less accurate anymore, but it ran. It is worth trying to see if large images were causing the timeout.
FAQ
URL
https://www.centrum.sk
What happened?
Hi everyone,
when i try to run lighthouse to test our company site it takes a really long time and produces low score. The score may be deserved but the time to take the test bothered me so i installed a lighthouse npm package and ran the test through that. While the results were mostly the same I noticed this in the logs:
LH:status Loading page & waiting for onload +0ms LH:status Navigating to https://www.centrum.sk/ +0ms LH:waitFor:warn Timed out waiting for page load. Checking if page is hung... +45s LH:status Gathering in-page: ServiceWorker +6ms LH:status Gathering devtoolsLog & network records +1msSeems that the loading of the page has sort of a timeout but the tests continue afterwards as if nothing has happened.
What did you expect?
No timeout when running the test.
What have you tried?
I did look at current and past issues hoping that someone ran into the same problem, but I didnt find anything that would explain why this is happening or how to fix it.
How were you running Lighthouse?
node, PageSpeed Insights, Chrome DevTools, web.dev
Lighthouse Version
9.6.2
Chrome Version
Version 100.0.4896.127 (Official Build) (arm64)
Node Version
v16.13.1
OS
Windows and Mac
Relevant log output