You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome provides an API to query their "CrUX" data (Chrome Rel user experience data). This data shows the CWV scores for real logged in Chrome users.
I'm currently using this API to diagnose some slow FID times on a client site. But, I've got to do everything by hand which is tricky when there are lots of URLs. It could be cool if you could optionally query the CrUX API for CWV scores for all of the URLs on your site. This could be another data point to include in spreadsheets and histograms.
One advantage of this data source is that it's real user data: it's not influenced by the machine hitting the API and represents real user experiences. It can also test for metrics like FID which can't be measured without a real user.
I'm not sure it it makes sense to integrate this into Lighthouse Parade. It may be a longshot. But the idea occurred to me so I thought I'd throw it out there and see what folks think.
The text was updated successfully, but these errors were encountered:
Chrome provides an API to query their "CrUX" data (Chrome Rel user experience data). This data shows the CWV scores for real logged in Chrome users.
I'm currently using this API to diagnose some slow FID times on a client site. But, I've got to do everything by hand which is tricky when there are lots of URLs. It could be cool if you could optionally query the CrUX API for CWV scores for all of the URLs on your site. This could be another data point to include in spreadsheets and histograms.
One advantage of this data source is that it's real user data: it's not influenced by the machine hitting the API and represents real user experiences. It can also test for metrics like FID which can't be measured without a real user.
I'm not sure it it makes sense to integrate this into Lighthouse Parade. It may be a longshot. But the idea occurred to me so I thought I'd throw it out there and see what folks think.
The text was updated successfully, but these errors were encountered: