The Chrome Speed Metrics team aims to quantify users' experience of the web to provide Chrome engineers and web developers the metrics, insights, and incentives they need to improve it. We aim to:
Chrome needs a small, consistent set of high quality user experience metrics. Chrome Speed Metrics is responsible for authoring reference implementations of these metrics implemented using Trace Based Metrics v2 (TBMv2) in tracing/metrics. These reference implementations will often require adding C++ instrumentation. Some metrics work will also be driven by more focused metrics teams, such as the work on Frame Throughput. Chrome Speed Metrics also owns UMA/UKM metrics, and speed metrics related Web Perf APIs.
The wider set of folks involved in defining these metrics will include:
Chrome Speed Metrics is responsible for ensuring that our core metrics are exposed everywhere. This includes collaborating with devtools, lighthouse, etc. to make sure our metrics are easy to expose, and are exposed effectively.
Metrics aren’t useful if no one looks at them. Chrome Speed Metrics performs detailed analysis on our key metrics and breakdown metrics, providing actionable reports on how Chrome performs in the lab and in the wild. These reports are used to guide regular decision making processes as part of Chrome’s planning cycle, as well as to inspire Chrome engineers with concrete ideas for how to improve Chrome’s UX.
The Chrome Speed Metrics team will gradually gain ownership of tracing/metrics, and will be responsible for the long term code health of this directory. We’re also ramping up ownership in the Web Perf API space.
We realize it's important to keep developers on the loop regarding important changes to our metric definitions. For this reason, we have created a metrics changelog which will be updated over time.