Problem with PageSpeed Insights, question marks and "Required traces gatherer did not run" error

[wladislaw-tepes]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

https://m.101hotels.com/main/cities/moskva

What happened?

I'm having issue with PageSpeed Insights, when I run an audit I get question marks instead of scores, and under each metric there is an error "Required traces gatherer did not run". Here's a screenshot https://i.imgur.com/c7InCEk.png

The problem appears around 12:00 GMT and disappears around 21:00. Last week the issue seemed to be gone all week (no question marks and errors, the audit went fine, scores were there), but on friday it started again. When I run tests of the page via Search Console all is fine, the page loads fine and ready for indexing. I also created an almost blank page without JS and CSS with only two words, and the error remained.

This problem is present on my mobile subdomain (m.101hotels.com), but no errors for other subdomain and desktop version.

What did you expect?

Successful audit with scores to appear after test

What have you tried?

Looked throuth logs with Chrome-Lighthouse UA, all visits were with 200 code.

I also created a blank page with document only and text "Hello, world" without js and css, the problem remained

How were you running Lighthouse?

PageSpeed Insights

Lighthouse Version

10.1.0

Chrome Version

No response

Node Version

No response

OS

Windows, Mac

Relevant log output

No response

[adamraine]

I can't reproduce this. If you see this again, can you click "Copy link" in the upper right and share the link to the report here?

[wladislaw-tepes]

I can't reproduce this. If you see this again, can you click "Copy link" in the upper right and share the link to the report here?

Sure, I have some from before. Here's one from today https://pagespeed.web.dev/analysis/https-m-101hotels-com-main-cities-moskva/wcylo28yol?form_factor=mobile, and one from last week https://pagespeed.web.dev/analysis/https-m-101hotels-com-main-cities-moskva/kau6x13y2c?form_factor=mobile

[adamraine]

Looks like Chrome is sending a net::ERR_TIMED_OUT error for the main document request on the page. It could be an issue with your server or the Chrome we are using but it's hard to say without a consistent repro.

That being said, this error detail is included in a Lighthouse warning that PSI doesn't display so perhaps we should find a way to surface it in the UI.

[khambadkone]

Hi, we're having a similar issue on our website. Can this be happening due to any rate limiting that occurs on the server ? What is the name of the bot that Pagespeed uses to analyse a webpage ?