Loop 002
The sub-50 ms page-load loop
A speed loop for local sites where the target is strict enough to force measurement discipline.
Ready-to-use prompt
Copy 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.Verify / stop
Every target page meets the 50 ms threshold.
The same benchmark, route list, environment, warm-up behavior, and measurement metric show every page under the agreed page-load threshold.
Use this when
Use this when a site has a known set of pages, a local or production-like benchmark, and a strict latency target that can be measured the same way after every change.
How to run it
- Define the exact page-load metric, target routes, hardware, runtime mode, warm-up behavior, and number of benchmark runs.
- Record a baseline for every route before making optimization changes.
- Make one meaningful optimization, then rerun the complete benchmark under the same conditions.
- Keep the change only when the target metric improves without creating a regression on another route.
- Repeat until every target page is under 50 ms or the next improvement needs a clearer benchmark or approval.
Why it works
Performance work becomes trustworthy when the benchmark stays fixed. Measuring every route after each change catches local wins that quietly slow down another page.
Implementation note
Name the metric before starting. Server response time, browser timing, and full visual readiness are different targets and should not be compared as if they were the same number.