benchmark

Collect end-to-end web performance metrics from the browse daemon across pages.

Updated Mar 28, 2026

Search Tags:#performance #benchmark #baseline #web-vitals #lcp #trend-analysis #ttfb

Ready to run

npx skills add https://github.com/steadyfall/fspeek --skill benchmark-steadyfall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/steadyfall/fspeek/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/steadyfall/fspeek --skill benchmark-steadyfall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance regressions creep in as PRs accumulate; measuring, baselining, and tracking web performance is hard without automated tooling.

Core Features & Use Cases

Baseline and compare: capture baseline performance data and compare against current builds.
Page-level metrics: TTFB, FCP, LCP, DOM timings, and resource analysis.
Trend and alerting: track performance trends over time and surface regressions.

Quick Start

Run the benchmark against a URL to capture baseline data and compare it with the current run.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect web performance regressions in my PR workflows?▼

To detect web performance regressions, collect end-to-end metrics from the browse daemon across multiple pages and compare them against a stored baseline. This allows PR workflows to automatically surface any introduced regressions.

What web vitals and timing metrics are needed for baseline performance tracking?▼

Baseline performance tracking requires capturing page-level metrics including TTFB, FCP, LCP, DOM timings, and resource timing data. These web vitals are collected across specified pages to accurately identify performance regressions.

How does trend analysis for web performance baselines work?▼

Trend analysis works by capturing baseline performance data and comparing it against current builds over time. By storing these baselines in .gstack/benchmark-reports/baselines, you can track metrics and surface regressions as PRs accumulate.

Do I need gstack tooling to run benchmark commands for LCP and TTFB?▼

Yes, you need gstack tooling to run perf commands, export navigation and resource timing data, and store baselines. It is required to collect the end-to-end metrics needed to detect regressions.

Can I perform a quick performance check on specified pages?▼

Yes, you can run a benchmark against a URL to capture baseline data and compare it with the current run. This quick check on specified pages uses the browse daemon to collect end-to-end metrics.