skills.rest
tayiorbeii
tayiorbeiiCOMMUNITY
Explore all skills by this author →
GitHub

gstack-benchmark

Measure browser performance metrics and compare results against baselines.

Updated Aug 23, 2026
Search Tags:#performance#web vitals#bundle size#lighthouse#benchmark#regression detection#page speed
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit --skill gstack-benchmark-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-benchmark
Source: https://github.com/tayiorbeii/paperclip-factory-kit/tree/main/skills/gstack-benchmark
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit --skill gstack-benchmark-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents slowdowns from slipping into production by measuring real page performance and comparing it to a known baseline.

Core Features & Use Cases

  • Page load and web vitals measurement: Captures timing signals like TTFB, FCP, LCP, and load milestones plus resource behavior.
  • Bundle and network size inspection: Summarizes requests, transfer size, and script and CSS bundle sizes to pinpoint the cause of slowness.
  • Baseline capture and PR comparisons: Saves baseline runs and flags regressions using thresholds, plus optional trend reporting from historical data.
  • Use case: When a PR increases LCP or bundle size, run the skill to confirm which page and resource introduced the regression and prioritize fixes.

Quick Start

Run gstack-benchmark on your site by telling the agent: "Run /benchmark on https://example.com with baseline comparison and report any regressions."

Frequently Asked Questions about gstack-benchmark

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

FAQPage Schema
How do I detect web performance regressions before a release?▼

To detect web performance regressions, measure real page load metrics and compare them against a saved baseline. This process flags slowdowns introduced by new changes before they reach production.

What web vitals and timing signals are needed for baseline comparison?▼

Baseline comparison requires web vitals like LCP and FCP, plus TTFB and load milestones. Capturing these navigation and paint timings lets you accurately compare page performance before and after changes.

How can I inspect bundle size and network requests to pinpoint slow page loads?▼

Inspect bundle size and network requests by summarizing transfer sizes and script or CSS bundles. This pinpoints the specific resources causing slow page loads and regressions.

Can I run a single-pass page speed check on a specific URL?▼

You can run a single-pass page speed check on a specific URL to capture immediate performance metrics. This quick check evaluates navigation, paint, and resource timing without needing a saved baseline.

Does pull-request performance auditing work with explicit regression thresholds?▼

Pull-request performance auditing works by applying explicit regression thresholds to baseline comparisons. It flags any changes that exceed your defined limits for web vitals or bundle size.

Related Skills

Explore More Data & Analytics Skills→
legotec73legotec73

benchmark

Collect baseline and current page metrics to detect performance regressions.

Community
Advanced
bhianerdbhianerd
1

benchmark

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

Community
Advanced
yashs33244yashs33244
1

benchmark

Benchmark real page load metrics against stored baselines to detect regressions.

Community
Advanced
SergeiGolosSergeiGolos
1

performance-profiling

Audit web performance with Lighthouse and analyze bundle sizes.

Community
Intermediate