Adds a web-exposed sampling profiler for measuring client JavaScript execution time.


Currently, it is difficult for web developers to understand how their applications perform in the wide variety of conditions encountered on real user devices. A native self-profiling API for JS code would also allow web developers to efficiently find hotspots in their JS code during page loads and user interactions, to assign CPU budgets to individual JS-implemented features on the page, to find unnecessary work being done on the client, and to find low-priority JS code executing in the background and wasting device power.




Editor's draft

Status in Chromium


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.


Search tags

profiler, profiling, js,

Last updated on 2021-04-12