benchmark

You can detect performance regressions by establishing historical baselines and comparing PR builds against them. This process applies to page load timings, Core Web Vitals, and resource sizes to catch slowdowns early across URLs and branches.

Automating Core Web Vitals trend analysis involves collecting timing data like TTFB, FCP, and LCP, then comparing current results against saved historical baselines. This approach surfaces hotspots and generates recommendations for performance improvements over time.

To set up a performance baseline comparison, run a performance audit on a target URL to collect timing data. The system saves these baselines locally, allowing you to compare current branch results against historical data to identify regressions or warnings.

Yes, you can track DOM timings and resource sizes across multiple URLs without dependencies. The system requires a browse daemon to collect timing data and saves all baseline reports locally, ensuring comprehensive metrics collection without external modules.

A browse daemon is required to actively collect timing data like TTFB, FCP, and LCP from targeted URLs. This background process enables the system to establish baselines, compare PR builds, and generate actionable regression and warning outputs.

When tracking performance trends over time using local baselines, you are limited by the local storage of reports in your project directory. This approach focuses on PR and branch comparisons rather than continuous production monitoring.