benchmark

To detect web performance regressions, measure current page timing, request counts, and transfer sizes, then compare them against a saved baseline. This process flags timing spikes, bundle growth, and request explosions introduced by recent frontend changes.

A performance baseline requires page timing metrics, JavaScript evaluation data, resource timing analysis, request counts, bundle size, and transfer sizes. Recording these metrics before a change lands enables accurate regression comparison and slow-resource identification.

Verify performance budgets by navigating affected routes with browse-daemon, evaluating JavaScript performance, and comparing resource timing and transfer sizes against stored baseline metrics. This confirms whether homepage, dashboard, or other pages still meet performance targets.

Yes, review historical benchmark trends to identify the slowest resources and verify common performance budgets. Trend reviews analyze stored baseline metrics for timing, bundle size, and request count variations to spot gradual web vitals degradation over time.

Yes, performance benchmarking requires browse-daemon navigation to evaluate JavaScript performance and analyze resource timing. This daemon enables automated page-speed audits and baseline metric storage for accurate regression detection across branches.