Install
openclaw skills install performance-benchmarkMeasure performance baselines, detect regressions, and compare stack alternatives before/after changes. Modes: page performance (Core Web Vitals), API latency, build speed, before/after comparison. Trigger phrases: benchmark, performance baseline, regression test, measure latency.
openclaw skills install performance-benchmarkMeasure performance impact of code changes and set baselines for your project.
Required: Bring your own benchmark tool (e.g. k6 for load testing, autocannon for API benchmarks, hyperfine for build speed).
benchmark baseline — captures current metricsbenchmark compare — measures impact against baseline⚠️ Safety Warning: Load tests should not be run against production systems without explicit authorization from your team. Test against staging or local environments only.
Measures on real browser:
- LCP (Largest Contentful Paint) — target < 2.5s
- CLS (Cumulative Layout Shift) — target < 0.1
- INP (Interaction to Next Paint) — target < 200ms
- TTFB (Time to First Byte) — target < 800ms
- Total page weight (target < 1MB)
- JS bundle (target < 200KB gzipped)
- Network requests count
Hit each endpoint 100 times:
- p50, p95, p99 latency
- Response size, status codes
- Load test: 10 concurrent requests
- Compare against SLA targets
Measures development feedback loop:
- Cold build time
- Hot reload time (HMR)
- Test suite duration
- TypeScript check time
- Lint time
- Docker build time
Reports saved to .benchmarks/ (git-tracked):
| Metric | Before | After | Delta | Verdict |
|---|---|---|---|---|
| LCP | 1.2s | 1.4s | +200ms | ⚠ WARN |
| Bundle | 180KB | 175KB | -5KB | ✓ BETTER |
references/integration.md — CI/CD setup, pairing with canary-watch and browser-qareferences/modes.md — detailed explanation of each measurement modeAdapted from everything-claude-code by @affaan-m (MIT)