benchmark

Performance regressions are detected by collecting navigation and resource timing metrics, storing baselines per URL, and comparing current results against historical data to alert you across PRs and branches.

You can establish baselines for Core Web Vitals and resource sizes by running a full performance audit on a target URL, which captures page load metrics and stores them for comparison against future builds.

Yes, you can compare current builds to baselines by running a diff analysis on collected metrics, which surfaces regressions and provides actionable insights for performance optimization.

Tracking performance trends over time is achieved by continuously capturing timing metrics per URL and visualizing the historical data to identify hotspots in resource usage.

Collecting navigation and resource timing metrics requires the browse daemon to gather data from target URLs, enabling baseline capture and diff analysis without external dependencies.

Regression detection may fail to surface hotspots if historical baselines are not properly established per URL, preventing accurate trend visualization and diff analysis across PRs.