benchmark

Detect web performance regressions by measuring page load metrics against saved baselines. This Skill captures end-to-end performance data like TTFB, FCP, and LCP, computing deltas to generate regression reports directly within your PR workflows.

A web-vitals baseline comparison requires page load metrics including TTFB, FCP, LCP, DOM Interactive, DOM Complete, and Full Load. It computes deltas against baseline files stored under .gstack/benchmark-reports/baselines to identify performance shifts.

Baseline capture and trend analysis work by collecting JavaScript performance probes during page loads and saving them as baseline files. It then compares subsequent builds and deployments against these files to track metric trends and detect regressions.

Yes, you need the browse daemon tooling and JavaScript performance probes to run a page performance audit. The tooling collects the required metrics and reads baseline files from the .gstack/benchmark-reports/baselines directory to generate comparison reports.

Yes, you can monitor production page load performance across deployments. It captures end-to-end metrics like LCP and FCP, compares them against established baselines, and provides trend analysis to protect user experience during continuous deployments.

The best way to compare page performance metrics for a specific URL is running a full audit against a saved baseline. This captures TTFB, FCP, and LCP metrics, computes deltas, and generates a regression report to highlight any performance degradation.