Your API Isn't Slow. Your Response Strategy Is.
There's a class of bug that never shows up in your performance benchmarks but destroys user trust every single time: the frozen UI on a long-running request.
You've seen it. A user clicks a button. The spinner appears. Ten seconds pass. Fifteen. The page looks completely dead. Has it crashed? Is it working? Should they refresh? By the time the response arrives, the damage is already done — they've lost confidence in your app.
The instinct is to optimize the underlying operation. Faster queries, better caching, smarter algorithms. That's not wrong, but it's also not the whole picture. Sometimes the operation genuinely takes time, and the real fix isn't making it faster — it's changing what the user experiences while they wait.
The Response Model We've All Accepted Without Questioning
