Performance is a product feature, not a cleanup task

People experience latency as uncertainty. A slow interaction does not only cost time; it makes the product feel less stable and the company behind it less capable.

Treat budgets as product constraints. Give every meaningful workflow a target, observe it in the field, and make regressions visible alongside feature work.

Not all milliseconds are equal. Start with the interaction closest to user intent, then remove work, stream useful state, or move computation to a better boundary.