Get every page under 50 ms
Benchmark each page with one repeatable measure and keep optimizing until every target loads under the threshold.
Use this when
Use this when a product has a defined set of routes, a stable performance harness, and a 50 ms target that maps to a specific metric and environment.
How it runs
- Define the exact metric, routes, test environment, warm-up behavior, and number of benchmark runs.
- Capture a baseline for every target page before making changes.
- Make one significant optimization, rerun the same benchmark, and inspect regressions across all routes.
- Continue until every page meets the threshold under the original test conditions.
Done when
✓ Every page loads in under 50 ms. Use the same benchmark and confirm there are no regressions.
Why it works
The fixed harness prevents performance work from turning into anecdotal tuning. Measuring every route after each change catches local wins that quietly slow down another page.
Implementation note
Page load can mean server response, render completion, or a browser timing metric. Name the metric and hardware explicitly so the 50 ms target is reproducible and meaningful.
More performance loops
Benchmark regression watch
Run the benchmark suite every 30 minutes during active development and raise a flag the moment any benchmark slips more than 5 percent from baseline.
Bundle size budget
Shrink the production JavaScript bundle under a hard budget by attacking the largest modules with code-splitting, lighter imports, and dead-weight removal.
AutoLoop — metric-driven optimization loops
Agent-agnostic hill-climbing loops inspired by Karpathy's autoresearch: define a metric, let the agent propose a change, measure, keep it only if the number improved, and repeat.