performance-testing

Name: performance-testing
Availability: InStock
Author: jota-batuta

Establish performance baselines and budgets for APIs and web applications.

Updated Feb 20, 2026

Search Tags:#benchmarking #budgeting #frontend-backend #load-testing #performance-testing #ci-cd #core-web-vitals

Ready to run

npx skills add https://github.com/jota-batuta/batuta-dots --skill performance-testing-jota-batuta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: performance-testing
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/performance-testing
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill performance-testing-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performance validation for APIs and web applications. It ensures you measure, baseline, and plan optimizations before changing code, preventing regressions and budget overruns.

Core Features & Use Cases

Baseline establishment: measure real-world performance (p50, p95, p99) for frontend and backend endpoints.
Core Web Vitals and budgets: set targets for LCP, FID/INP, CLS, TTFB and enforce budgets in CI/CD.
CI/CD integration and tooling: support k6, Artillery, Lighthouse workflows for automated regression checks and performance budgets in pipelines.
Use Case: Validate a new feature rollout by comparing current performance against the established baseline and triggering alerts if budgets are exceeded.

Quick Start

Run a baseline load test in your CI to establish performance targets for your API and iterate on improvements.

Frequently Asked Questions about performance-testing

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

FAQPage Schema

How do I establish a performance baseline for my API and web application?▼

Performance testing baselines measure real-world frontend and backend metrics like p50, p95, and p99 percentiles. This provides baseline protocols and budgeting rules to compare against before changing code, preventing regressions.

How do I enforce Core Web Vitals budgets in my CI/CD pipeline?▼

Core Web Vitals budgets enforce targets for LCP, FID/INP, CLS, and TTFB within CI/CD pipelines. This provides example configurations using k6, Artillery, and Lighthouse workflows to trigger automated regression checks and alerts for budget overruns.

What's the best way to identify frontend and backend performance bottlenecks?▼

Identifying performance bottlenecks requires measuring real-world metrics across frontend and backend endpoints. This applies testing end-to-end, establishing baselines and budgeting rules to pinpoint where API or web application latency originates.

Can I validate a new feature rollout against an existing performance baseline?▼

Validating a new feature rollout requires comparing current performance against an established baseline. This applies baseline protocols to measure frontend and backend endpoints, triggering alerts if Core Web Vitals or API budgets are exceeded.

Do I need specific load-testing tools to apply performance testing to my application?▼

Performance testing supports integration with k6, Artillery, and Lighthouse workflows. No specific dependencies are required to start; it provides baseline protocols, budgeting rules, and example configurations to implement automated regression checks.

Why measure p50, p95, and p99 percentiles before optimizing application code?▼

Measuring p50, p95, and p99 percentiles establishes a performance baseline to validate API and web application behavior. This prevents regressions and budget overruns by ensuring you measure and plan optimizations before changing code.