What puts a wait in the shortest band
Length is the symptom in this band, not the definition. What the cards below share is a shape. A request goes out over a path through the network that has already been assembled, something at the far end answers it, and the browser paints what came back. There is no queue in front of the request. No second person has to notice anything. No outside network has to reach agreement with itself before an answer can exist.
That shape carries its own ceiling. The cost is the time the relays need to carry the message out and the reply back, plus whatever small work the service does in between. Relay hops add up, and over a poor path they add up more than most people expect, but the number of hops does not change while you sit there watching. The wait is bounded by something that was already fixed at the moment you pressed the key.
One consequence of that bound is worth stating on its own. Nothing in this band gets faster because you want it to, and nothing in it gets slower because you looked away. The variation you notice from one attempt to the next is variation in the route, not in the service. A route that happens to run through congested relays is slow for everything you do over it, including things that were quick a moment earlier, which is why a sudden run of sluggish pages usually says more about the path than about the far end.
It is also why failures in this band tend to be loud rather than quiet. When the exchange genuinely cannot complete, something breaks the silence: a browser error, a timeout page, a layout that arrived without the pieces that were meant to fill it. A wait of this size that is broken usually says so. A wait of this size that is merely slow says nothing at all, and that is where the trouble in this band begins.
- One path, already built
- Nothing here assembles a new route through the network. If a fresh route has to be built before anything can be asked, the wait has left this band and belongs with building another circuit.
- One answer, already existing
- A single response completes the wait. The thing you asked for is not being manufactured while you watch, and it is not sitting behind other people in a line.
- Nobody else in the loop
- No human has to read anything and no outside network has to confirm anything before the screen is allowed to change.
Reading a short silence as a failure
The mistake that defines this band is acting on a pause that has not yet earned the name. The screen sits still. Nothing on it says anything is wrong. The reflex is to reload, or to press the button a second time, or to open the same thing in another tab, or to go looking for a different address.
Each of those has a cost that is easy to miss in the moment. A reload discards the response that was already on its way and asks for the whole thing again from the beginning, so a wait you were nearly through with starts over. Pressing a submit button twice can send a second copy of what you submitted rather than replacing the first. Opening the same service in a second tab makes both tabs compete for the same path through the network, which makes both of them slower than the one would have been. Going looking for a different address is the worst of the four, because it means handling a long string at exactly the moment you have the least patience for checking it.
The rule that fits here follows from the mechanism. A wait sits in this band because of how it is built, so it has earned the whole of the band before you treat it as broken. If it runs past that with no error of any kind, the useful question is not which key to press. It is what changed. Whether the path is simply poor, whether you are sitting on the gate screen without having recognised it, or whether the address you reached was never the one you meant to reach. Reading the address string again costs less than any of the four reflexes and rules out the worst of the possibilities.
The waits filed here
Each card names one thing you might be watching, says what is happening out of sight while it looks like nothing is, and says what would make it take longer than the band suggests. They are short waits, so the cards spend most of their space underneath the screen rather than on it. That is where the interesting part is.
Seconds · Wait 01
The first contact costs more than any later one.
Waiting for the client and the service to arrange a meeting point and the first bytes to come back
Seconds · Wait 02
Arrival is not the same as the request landing.
Waiting for the page to arrive as bytes and the browser to have enough of it to draw
Seconds · Wait 03
A small image that travels on its own.
Waiting for a small image to be generated for your visit and sent separately from the page it sits in
Seconds · Wait 04
One trip out, one trip back, and a decision in between.
Waiting for the form to reach the service and a decision about it to come back
Seconds · Wait 05
A wait you should choose to take.
Waiting for the current code to run out so the next one can be used from the start of its life
Seconds · Wait 06
The trip costs more than the matching does.
Waiting for a query to reach the catalogue and a page of results to make the trip back
Seconds · Wait 07
The only wait here worth making longer.
Waiting for nothing on the network, only for your own eyes to finish comparing the string
Telling this band from the one above it
No band is shorter than this one, so there is only one border to police, the one with waits measured in minutes. The test is never how long the screen has been still. It is whether anything has to be built, queued or agreed before the answer you want is capable of existing.
| If this is true of your situation | Where the wait belongs |
|---|---|
| The route through the network is already open and carrying traffic. | Here, in the shortest band. |
| A route has to be assembled before anything can be asked at all. | The minutes band, because assembling one is work in its own right. |
| The service is holding everyone at a door before it will serve any of them. | The minutes band. A door is a queue, and queues do not answer on arrival. |
| Something outside the market has to agree before a number on your screen changes. | The minutes band at the earliest, and often an evening. |
One border case is worth naming outright. The pause after you press sign in feels as though it belongs a band higher, because a login feels heavier than a search feels. It does not belong higher, because the work is still a single exchange and the answer still already exists. What can push it upward is a cooldown, and a cooldown is a separate wait with a mechanism of its own and a card of its own.