What problem does it solve? Teams need to verify that APIs, web pages, and mobile apps meet latency, throughput, and stability targets under realistic load, but configuring load generators, web vitals assertions, and threshold gates across different tools is fragmented and error-prone. ## Core Features & Use Cases - API Performance Testing: Run load, stress, spike, endurance, and smoke scenarios with K6, Gatling, or JMeter, with percentile thresholds (p95/p99), throughput, and error-rate gates exported to Allure. - Web e2e Performance Testing: Measure Core Web Vitals (FCP, LCP, CLS), page load time, and interaction latency natively in Playwright across cold-load, warm-cache, and slow-network scenarios. - Mobile Performance Reference: Delegates mobile device performance testing to the independent mobile-testing skill without duplication. - Use Case: Before a product launch, run a K6 load test ramping to 100 virtual users against the login API, then execute a Playwright cold-load test asserting LCP under 2.5 seconds, and review both timing reports in Allure. ## Quick Start Ask the AI to run an API load test with K6 against your staging API using the performance-testing skill and report the p95 response time and error rate.