benchmark

Measure browser performance metrics like TTFB, FCP, and LCP via the browse daemon.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/256javy/safia --skill benchmark-256javy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/256javy/safia/tree/main/.claude/skills/gstack/benchmark
Command: npx skills add https://github.com/256javy/safia --skill benchmark-256javy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Web performance often drifts unnoticed until user experience degrades. This skill provides automated measurement, baseline capture, and regression detection for page load timings and resource sizing.

Core Features & Use Cases

  • Baseline and compare core metrics (TTFB, FCP, LCP, DOM timings) across pages and deployments.
  • Surface regressions and trends with actionable insights, including resource and bundle-size analysis.
  • Integrate into PR workflows to flag performance regressions before merge.

Quick Start

Run /benchmark <url> to perform a full performance audit against the target page.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I measure web performance metrics like LCP and TTFB for my deployments?

You can measure web performance metrics like LCP and TTFB by running an audit against a target URL using the browse daemon to collect core timings and resource sizing data, which establishes a performance baseline for your deployments.

Can I detect browser performance regressions in my PR workflows?

Yes, you can detect browser performance regressions in PR workflows by integrating this benchmarking process to flag page load timing drifts and bundle-size increases before merging code changes, preventing unnoticed web vital degradation.

What is the best way to establish a baseline for page load timings and resource sizing?

The best way to establish a baseline for page load timings is to collect DOM timings, TTFB, FCP, and LCP across multiple pages and deployments, capturing and reporting results using structured JSON and Markdown outputs for trend analysis.

How do I compare core web vitals across multiple pages and deployments?

You can compare core web vitals across multiple pages by running benchmark audits against target URLs to capture baseline metrics, then analyzing the generated JSON and Markdown outputs to surface regressions and actionable trends.

Does web performance benchmarking work without additional dependencies?

Yes, web performance benchmarking works without additional dependencies. The skill operates independently using the browse daemon to measure TTFB, FCP, LCP, and related metrics, requiring no external packages to execute end-to-end audits and report results.