benchmark

Automate performance regression detection by capturing baseline timing metrics across builds and comparing them against current page-level performance. Using a browse daemon with JS evaluation, you collect navigation timing, resource timing, and bundle sizes to identify when code changes slow things down.

Web vitals benchmarking requires capturing TTFB, FCP, LCP, and DOM metrics. Collecting these page-level timing metrics and resource profiles through automated JS evaluation provides the data needed to measure performance regressions and generate trend reports.

Yes, you can establish a performance baseline and compare it against current builds. The benchmarking process uses a browse daemon to collect web vitals and timing data, allowing you to track performance trends and detect regressions across the application lifecycle.

Track web performance trends by capturing baseline metrics and comparing them against subsequent builds. The benchmarking process collects navigation and resource timing data, storing detailed trend reports under .gstack/benchmark-reports for ongoing regression analysis.

No external dependencies or components are required. The benchmarking process relies on a built-in browse daemon and JS evaluation to collect performance metrics, generate timing reports, and detect regressions without needing additional setup.

Generate performance benchmark reports by running automated benchmarks on a URL to capture timing data. The system collects web vitals, navigation timing, and bundle sizes, saving detailed trend and regression reports into .gstack/benchmark-reports.