skills.rest
MFS-code
MFS-codeCOMMUNITY
Explore all skills by this author →
Website𝕏@miguelfsernaGitHub

benchmark

Measure page load performance and compare metrics against saved baselines.

8|2|Updated Mar 24, 2026
Search Tags:#bundle size#performance reporting#web performance#core web vitals#regression detection#frontend optimization#LCP FCP
One-click install
npx skills add https://github.com/MFS-code/gstack --skill benchmark-mfs-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/MFS-code/gstack/tree/main/benchmark
Command: npx skills add https://github.com/MFS-code/gstack --skill benchmark-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web performance can silently degrade over many pull requests, causing slower load times and worse Core Web Vitals without clear attribution. The benchmark skill measures real browser performance and compares it to a saved baseline to pinpoint regressions.

Core Features & Use Cases

  • Baseline capture and comparison: Save reference performance for a URL and later compare before/after metrics to identify deltas.
  • Comprehensive page auditing: Collect navigation timing, paint metrics (FCP/LCP), DOM timings, resource breakdown, and bundle size indicators.
  • Regression triage and reporting: Produce structured reports with warning/regression thresholds and list the slowest resources to guide optimization work.
  • Trend analysis over time: Visualize performance movement across multiple historical benchmarks to catch gradual degradation.

Quick Start

Run the benchmark for a URL you care about by telling the agent to benchmark https://example.com with a baseline comparison.

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 a pull request?▼

To detect web performance regressions, you capture a baseline of page load metrics for a URL before changes, then diff the current branch against the saved baseline using regression thresholds. This identifies Core Web Vitals deltas.

What metrics are collected when measuring Core Web Vitals and page load performance?▼

Measuring Core Web Vitals and page load performance involves collecting navigation timings, paint metrics like FCP and LCP, DOM timings, resource breakdown statistics, and bundle-size signals through in-page JavaScript execution.

Can I track historical page load performance trends over time?▼

Yes, you can track historical performance trends by persisting benchmark results into report files across multiple runs. This visualizes performance movement and catches gradual frontend degradation over time.

Do I need a browse daemon to audit frontend performance and bundle size?▼

Yes, auditing frontend performance and bundle size requires a browse daemon to navigate to the target page and execute in-page JavaScript. This extracts Performance entries and resource statistics for the report.

What is the best way to triage slow resources affecting LCP and FCP?▼

The best way to triage slow resources affecting LCP and FCP is to run a full page audit that produces structured reports. These reports list the slowest resources and flag warnings using regression thresholds.

Related Skills

Explore More Data & Analytics Skills→
nuurpronuurpro
1

canary

Detect post-deploy console errors, performance regressions, and page failures via the browse daemon.

Community
Intermediate
Intension-usIntension-us

benchmark

Measures frontend performance metrics from running pages via browse daemon and perf tooling.

Official
Advanced
bhianerdbhianerd
1

benchmark

Benchmark web page navigation timings and web vitals against a saved baseline.

Community
Advanced
bizzybaebizzybae

benchmark

Run browser-based benchmarks to compare web performance across pull requests.

Community
Advanced