Page Speed Insights incorrectly reports insufficient data for the origin

185 views
Skip to first unread message

Kevin Farrugia

unread,
May 9, 2024, 4:30:43 AMMay 9
to Chrome UX Report (Discussions)
I ordinarily collect CrUX data using the CrUX API or the CrUX dashboard, both of which work well and report data for the origin https://sports.tipico.de.

However, when testing the URL using Page Speed Insights I receive the message "The Chrome User Experience Report does not have sufficient real-world speed data for this origin".

Thank you

Barry Pollard

unread,
May 9, 2024, 6:57:20 AMMay 9
to Kevin Farrugia, Chrome UX Report (Discussions)
Hi Kevin,

I see the following from the CrUX API:

Mobile home page: available
Desktop home page: unavailable

Mobile origin: unavailable
Desktop origin: available

And this is exactly what I see on PSI:

image.png

Now I'll admit it's slightly unusual to have URL-level data but not origin-level data, but this can happen in one of two cases:
  1. Data is borderline
  2. The root page redirects and it's difficult to tell if the origin should be indexed (we've had some problems with this recently for some origins).
It looks like a combo of both these issues for this. For the home page it seems to drift in and out of having enough data especially for desktop:

image.png

While for origin it looks like it dropped off recently in the last week (so after the CrUX dashboard was last updated last month):

image.png

Checking the no-index status I can see it redirects to https://sports.tipico.de/de and that seems to have caused the noindex flag to have been raised (despite neither the https://sports.tipico.de/ nor https://sports.tipico.de/de being no indexed). As I say, a few sites that redirect experience this and we've not been able to get to the bottom of it yet. Is this redirect new out of interest?


--
You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ux-repo...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/c9a5969e-e661-49e2-badd-3141281ccc6en%40chromium.org.
Message has been deleted
Message has been deleted

Kevin Farrugia

unread,
Jun 14, 2024, 7:46:16 AMJun 14
to Chrome UX Report (Discussions), Barry Pollard, Chrome UX Report (Discussions), Kevin Farrugia
Thank you Barry for the response.  

Yes you are correct, the CrUX API stopped reporting data for the origin since 01 May 2024, suggesting it is a reoccurence of the root page redirect. I was following a previously reported incident on this group that was also affecting this website, but it was resolved in the June 2023 release. Since then, I had origin-level data. It stopped working on 01 May 2024 and to date I still do not have origin-level data.

The page level data included in your link refers to the page before the redirect. That page is only available to users outside of Germany, so we do not expect it to have a lot of traffic. All German users (> 95% of traffic) should be redirected. The correct URL for page-level data for the home page would include be https://sports.tipico.de/de—which is available on CrUX API.
Message has been deleted

Kevin Farrugia

unread,
Jul 16, 2024, 12:39:52 AMJul 16
to Chrome UX Report (Discussions), Kevin Farrugia, Barry Pollard, Chrome UX Report (Discussions)
I saw in a separate thread that the issue was fixed for some sites but I still see the same issue for origin-level data on our site.

Kevin Farrugia

unread,
Jul 16, 2024, 12:39:52 AMJul 16
to Chrome UX Report (Discussions), Kevin Farrugia, Barry Pollard, Chrome UX Report (Discussions)
I saw in a separate thread that the issue was fixed for some sites but I still see the same issue for origin-level data on our site.

On Friday 14 June 2024 at 13:46:16 UTC+2 Kevin Farrugia wrote:

Kevin Farrugia

unread,
Aug 1, 2024, 3:38:39 AMAug 1
to Chrome UX Report (Discussions), Kevin Farrugia, Barry Pollard, Chrome UX Report (Discussions)
Since 2024/07/20 it is working once again and I have origin-level data. Thank you.

Coleena Smithwick

unread,
Aug 23, 2024, 12:28:07 PMAug 23
to Chrome UX Report (Discussions), Kevin Farrugia, Barry Pollard, Chrome UX Report (Discussions)
Been having same issue for quite some time and it still continues, how do I fix it?
Reply all
Reply to author
Forward
0 new messages