The sub-50 ms page-load loop

A performance optimization workflow for coding agents that uses one repeatable benchmark and stops only when every target page meets the threshold.

Use 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.

The loop

Continue optimizing the code for speed. After each significant change, measure page-load performance across every page under the same repeatable test conditions. Continue until every page loads in under 50 ms.

Steps

• 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.

Verification

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.