skills.rest
aporto-tech
aporto-techOFFICIAL
Explore all skills by this author →
GitHub

gstack-benchmark

Detect web application performance regressions by comparing page load times, Core Web Vitals, and resource sizes.

Updated Jun 4, 2026
Search Tags:#performance#web vitals#bundle size#lighthouse#benchmark#page speed#load time
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill gstack-benchmark-aporto-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-benchmark
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/benchmark
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill gstack-benchmark-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_automation, and includes scripts (resource) components.

What problem does it solve?

This Skill identifies performance issues in web applications, ensuring that changes do not negatively impact user experience. It compares performance metrics before and after changes and tracks trends over time.

Core Features & Use Cases

  • Performance Regression Detection: Compares page load times, Core Web Vitals, and resource sizes between different versions.
  • Baseline Comparison: Establishes baselines for performance metrics and compares them with current performance data.
  • Trend Analysis: Tracks performance trends over time to identify gradual degradations.
  • Use Case: When preparing a pull request or deploying a new version of a web application, use this Skill to ensure that changes have not introduced performance issues.

Quick Start

Run the benchmark skill on the URL 'https://example.com' to check its performance.

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 deploying a new version?▼

To detect web performance regressions, compare page load times, Core Web Vitals, and resource sizes before and after changes using benchmark tracking to identify any degradations.

What is performance baseline comparison and when do I need it?▼

Performance baseline comparison establishes a reference for page load times and Core Web Vitals, and you need it when preparing a pull request to ensure changes have not introduced performance issues.

Do I need browser automation to measure Core Web Vitals and resource sizes?▼

Yes, you need browser automation capabilities to measure Core Web Vitals and resource sizes, as the benchmark process requires automating the browser to collect accurate performance data from the target URL.

How do I track Core Web Vitals and page load time trends over time?▼

You track Core Web Vitals and page load time trends by running benchmark comparisons on your web application URL, which records performance metrics over time to identify gradual degradations.

What's the best way to check if my bundle size changes impact page speed?▼

The best way to check if bundle size changes impact page speed is by comparing resource sizes and page load times between different application versions to pinpoint performance degradations.

Related Skills

Explore More Software Engineering Skills→
ClyptAIClyptAI

benchmark

Measure real-browser performance by collecting navigation and resource metrics for target URLs.

Official
Advanced
SoSoBurnerSoSoBurner

benchmark

Measure page load times, Core Web Vitals, and resource sizes in CI/CD pipelines.

Community
Advanced
OysteinAmundsenOysteinAmundsen
48

bundle-check

Validate @toolbox-web/grid index.js bundle size against raw and gzipped limits.

Community
Intermediate
DexploarerDexploarer
6

lighthouse-ci-integrator

Automate Lighthouse CI audits and enforce performance budgets in CI/CD pipelines.

Community
Intermediate