Repository navigation
Replace the Loading Speed report with CrUX #178
Description
Activity
Strong +1. It's far too easy to draw wrong conclusions based on current synthetic tests running on oversubscribed VMs.
Strong +1. It's far too easy to draw wrong conclusions based on current synthetic tests running on oversubscribed VMs.
FWIW, WPT uses
n1-standard-2, which should be fine according to the Lighthouse recommended machine specs. It'd be concerning if it were using n1-standard-1. (And of course a beefier machine may improve variability, but we currently haven't collected data to quantify the degree.)
https://httparchive.org/reports/loading-speed
This report is based on HTTP Archive's synthetic monitoring of the following performance metrics:
It's not our intent to draw conclusions about real users' experiences based on synthetic metrics like these. In order to avoid this pitfall, we should replace the metrics in the report with the RUM-based metrics from CrUX.
To implement this, we should overwrite the existing
loading-speedreport with the metrics in the chrome-ux-report.