What actually makes a music bot feel fast

Ask someone why they prefer one music bot to another and you will rarely get a feature. You will get "it just works" or "the other one is slow". Both are about timing, and neither is something people measure.

The first note is the whole impression

The gap between asking for a song and hearing it is the moment the product is judged. Everything after that is assumed to work.

That gap is mostly not playback. It is resolving what you asked for: working out that a link is a track rather than a playlist, finding the audio, and getting ready to stream. Making the streaming faster does very little; making the resolution faster does almost everything.

A gap is worse than a wait

Silence in the middle of a song is far more damaging than a slightly slower start. A pause reads as broken, and one interruption undoes a long stretch of everything working.

Which is why audio is kept away from everything that might block it. Whatever else the bot is doing — answering commands, writing to storage, handling another server entirely — it must not be able to interrupt what is already playing. That constraint drove more of the design than any feature did.

Predictable beats fast

A bot that always starts in two seconds feels better than one that usually takes half a second and occasionally takes eight. People adapt to a consistent delay within minutes and never adapt to an unpredictable one.

Users do not experience averages. They experience the worst thing that happened to them recently.