Web vitals missing on Crux API since update ?

116 views
Skip to first unread message

Quentin Mathieu

unread,
Apr 11, 2025, 12:26:27 PMApr 11
to Chrome UX Report (Discussions)
Hello,
I've noticed that some websites are not returning all cwv metrics through cruxAPI even if other metrics have data and that the website has high traffic (around 10k chrome users per day)

this is an example that returns all metrics but LCP
 {
    "origin":"https://kr.louisvuitton.com",
    "formFactor": "PHONE"

}

From time to time i even get straight up a 404.

I was thinking that it could be due to low traffic on chrome users but after checking i can see that other subdomains with lower traffic on chrome dont' have the issue.

Any idea on why this is happening ?


Kind regards

Quentin

Lal Chandran

unread,
Apr 12, 2025, 10:43:14 AMApr 12
to Chrome UX Report (Discussions), Quentin Mathieu
We have the same problem. We have close to 20k users and it says 99.9% users are from desktop. This simply cannot be true. 

❄ Johannes Henkel

unread,
Apr 12, 2025, 12:02:26 PMApr 12
to Lal Chandran, Chrome UX Report (Discussions), Quentin Mathieu
Hi!

Thanks to both of you for letting us know.

I have looked into the origin mentioned in Quentin's post (https://kr.louisvuitton.com). My understanding is that this particular origin is affected by not quite hitting our requirements for "sufficiently popular" (https://developer.chrome.com/docs/crux/methodology#popularity-eligibility).

Unfortunately this can play out in a somewhat confusing manner: Because LCP has slightly fewer recorded measurements than FCP, we may not be able to include it when we do include FCP.
But then also, when we're right at the edge of the popularity requirement and need to drop the data for a form factor, we require that the overall data (=all form factors) has at least 80% of the traffic in it (https://developer.chrome.com/docs/crux/methodology#filtering).
So this can have the effect of dropping (for example) phone-specific data when the desktop data can't be included but has more than 20% (e.g. imagine it's 70% phone and 30% desktop and desktop can't be included). But in that case ... the overall data would be available.

For the specific example origin "https://kr.louisvuitton.com": Whereas ~yesterday, when we were serving 2024-04-09, we were missing LCP for form factor 'phone' for the first issue, ~today, we're serving 2024-04-10 and so we're returning 404 for phone for the second issue (probably, I haven't checked this 100%) - but if you make a request without form factor { "origin":"https://kr.louisvuitton.com" } you actually get overall data today (including LCP).

Hope this helps a bit. If you do see things that don't make sense, please point them out and examples are definitely useful and appreciated.

Good wishes,
Johannes.



--
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 [email protected].
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/1c7e21db-e938-417b-9fdf-17879cc068can%40chromium.org.

Quentin Mathieu

unread,
Apr 12, 2025, 12:43:07 PMApr 12
to ❄ Johannes Henkel, Lal Chandran, Chrome UX Report (Discussions)

Hello Johannes,

Thanks for your reply. That makes sense. What was unexpected to me was that kr.louisvuitton.com was having the issue but not other subdomains that have less overall traffic. But from my understanding I also have to check the form factors repartition in order to know if the requirements are fulfilled.


I'll investigate,


Have a good day

Quentin 

❄ Johannes Henkel

unread,
Apr 12, 2025, 1:08:30 PMApr 12
to Quentin Mathieu, Lal Chandran, Chrome UX Report (Discussions)
Also, maybe to keep in mind is https://developer.chrome.com/docs/crux/methodology#user-eligibility - the "eligible traffic" is not necessarily the same fraction across form factors and countries.
I think this is a limitation of this dataset - so if you have your own RUM it's probably a better way to compare such country specific sites, or ratios between form factors.
Good wishes!

❄ Johannes Henkel

unread,
Apr 12, 2025, 1:48:21 PMApr 12
to Lal Chandran, Chrome UX Report (Discussions), Quentin Mathieu
Thank you!

I do think this origin is also affected by the popularity thresholds, and this is also true for the form factors.

Quickest way to see it is in the CrUX History API, or via CrUX VIs, e.g. this link shows the CWV history:
and clicking between "Desktop" and "Phone" in the controls area one can see that there were stretches when these form factors had individual reporting.

And, there is a "Form Factors" metric, it's in this view at the bottom (can be expanded):
There is some data at times, but because frequently there wasn't enough traffic to include the detailed data points, there's no fractions or it ends up being 0% and 100% which is distortion that comes from our aforementioned filtering (up to 20% can be dropped).

Btw - another way to do a quick check on "popularity" according to CrUX is rank magnitude (https://developer.chrome.com/blog/crux-rank-magnitude). In this case, the rank magnitude is 50M (smaller means more popular). This was my query:

SELECT
origin,
experimental.popularity.rank
FROM
`chrome-ux-report`.all.202503
WHERE
origin = 'https://igrant.io'

So, I'd say this is a limitation with CrUX / what we can publish, not with your site.
You could measure things with your own Real User Monitoring (RUM).

Good wishes,
Johannes.

On Sat, Apr 12, 2025 at 2:43 AM Lal Chandran <[email protected]> wrote:
I'm not sure my earlier post reply worked, so I'm reposting it again.


We are confident that we have enough mobile users. We initially observed this 2 years or so ago and did a lot of optimisation. It improved our desktop situation, but not our mobile one. 

Lal Chandran

unread,
Apr 15, 2025, 7:43:55 PMApr 15
to Chrome UX Report (Discussions), ❄ Johannes Henkel, Chrome UX Report (Discussions), Quentin Mathieu, Lal Chandran
@Johannes: I appreciate your quick reply.
Could you investigate a bit? We noticed it first a year ago and did a lot of improvements, and we can see it changing the desktop numbers. However, mobile stayed unchanged. We are reasonably sure we have a good enough number of users. 

On Saturday, 12 April 2025 at 11:02:26 UTC+2 ❄ Johannes Henkel wrote:

Barry Pollard

unread,
Apr 15, 2025, 7:51:11 PMApr 15
to Lal Chandran, Chrome UX Report (Discussions), ❄ Johannes Henkel, Quentin Mathieu
It looks like you're in the top 50,000,000 sites visited by Chrome users, which is the final bucket of sites (we actually only list the top 17 million sites or so in CrUX). So sites in that bucket are liable to drop in and out of the CrUX dataset unfortunately — which looks to be the case for your site over last few months.

P.S. I've deleted your other message. Posters who are not members of this group have to have their messages reviewed before they are allowed through to the group due to spam.

Reply all
Reply to author
Forward
0 new messages