benchmark

Compare current web performance metrics against stored JSON baselines.

Updated Jun 22, 2026

Search Tags:#testing #performance #web vitals #optimization #benchmarking #regression

Ready to run

npx skills add https://github.com/betaTrident/manta --skill benchmark-betatrident

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/betaTrident/manta/tree/main/.agents/skills/benchmark
Command: npx skills add https://github.com/betaTrident/manta --skill benchmark-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the difficulty of maintaining performance standards by providing a standardized way to measure, track, and compare application speed and resource usage across development cycles.

Core Features & Use Cases

Performance Baselines: Capture and store snapshots of Core Web Vitals and API latency to establish a "known good" state.
Regression Detection: Automatically compare current metrics against saved baselines to identify performance degradation before deployment.
Use Case: Before merging a large feature branch, run a comparison to ensure that the new code does not negatively impact the Largest Contentful Paint (LCP) or increase the JS bundle size beyond defined thresholds.

Quick Start

Use the benchmark skill to compare the current application performance against the saved baseline.

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 before deploying new code?▼

Web performance regression detection works by comparing current Core Web Vitals and API latency against stored JSON baselines. This process identifies performance degradation early, ensuring new feature branches do not negatively impact application stability or breach SLA targets before merging.

What is the best way to establish a performance baseline for Core Web Vitals?▼

The best way to establish a performance baseline is to capture and store snapshots of Core Web Vitals, API latency, and build times as a JSON file within your repository. This creates a known good state to compare future development cycles against.

Can I measure API latency and build times to maintain strict SLA targets?▼

Yes, you can measure API latency and build times to maintain strict SLA targets. The benchmarking process requires browser-based performance auditing and build-time analysis to validate that application speed and resource usage meet your defined thresholds.

How do I check if a large feature branch increases JS bundle size beyond defined thresholds?▼

To check if a feature branch increases JS bundle size beyond thresholds, run a performance comparison against your saved baseline. Build-time analysis validates resource usage and flags metrics that exceed your defined limits before deployment.

When do I need to run browser-based performance auditing for web vitals optimization?▼

You need browser-based performance auditing for web vitals optimization when you want to measure and validate current application speed against stored baselines. This is crucial before merging large updates to prevent performance degradation and ensure stability.

Why does comparing current performance data against stored JSON baselines prevent deployment issues?▼

Comparing current performance data against stored JSON baselines prevents deployment issues by automatically detecting regressions. Identifying degraded Core Web Vitals or increased API latency before deployment ensures application stability and strict SLA compliance.