Superior Performance

Improve the user or system outcome that is actually constrained, not the code that merely looks expensive. Preserve correctness, security, accessibility, and maintainability while grounding every optimization in comparable evidence.

Define the performance contract

Before optimizing, establish:

• the affected user journey, operation, workload, or resource;
• the metric and target, including percentile or distribution where relevant;
• current baseline, regression window, and measurement source;
• environment, hardware, network, data shape, concurrency, and cache state;
• correctness and quality constraints that may not be traded away;
• whether the goal is latency, throughput, responsiveness, capacity, efficiency, or cost.

Do not convert an unverified impression such as “slow” into a universal target. If no explicit budget exists, derive a provisional comparison from product expectations and repository evidence, and label it as provisional.

Measure before changing