Usually feels like
Seconds
It finishes while you are still looking at the screen.
It sits in seconds because the arrangement is made once and then reused, not because anything about it is quick.
The wait, in plain words
You paste the address, press enter, and the browser sits there with nothing to show. No progress bar that means anything, no partial page, just a tab that has committed to something. This is the stretch before the first byte, and it is the one people cut short most often.
A name on the ordinary web resolves to a machine, and your request goes to that machine. An onion address does not work that way. There is no machine to go to, because the service is hiding as deliberately as you are. Both sides have to agree on somewhere to meet, and neither side wants to say where it lives.
So this is not a lookup taking its time. It is a small piece of negotiation, and it has to finish before anything at all can be drawn. When it does finish, the first screen painting begins, and that is a different wait with a different feel.
Underneath, while nothing moves
Roughly, the shape is this. The service has told the network in advance about a handful of relays it is willing to be introduced through. Your client fetches that advertisement, picks one of those introduction points, and separately nominates a meeting point of its own choosing. It sends word, through the introduction point, of where to meet. The service builds a path to the meeting point. You build a path to the meeting point. The two halves join there.
Nothing in that description is a claim about timings. It is a claim about how many separate arrangements have to succeed before your request can even leave. Each hop is a relay somewhere in the world, chosen without regard to whether it is anywhere near you, and each arrangement is a round trip in its own right.
- The advertisement
- A description the service publishes so clients can find a way to be introduced. Fetching it is a request in itself, made before your own request exists.
- The introduction point
- A relay the service is willing to hear from. It carries the request for a meeting and nothing else.
- The meeting point
- A relay you nominate. Neither side learns where the other lives, because both only ever speak to this middle.
- The joined path
- Once the halves meet, the path stays up and later requests ride it. That is why the second page usually feels quicker than the first.
That last row is the part worth keeping. The expensive work is the setting up, not the using. If opening the address feels slow and then everything after it feels ordinary, nothing went wrong. You paid at the entrance.
When the arrangement fails instead of finishing, the client does not announce it. It quietly tries again along different relays, and the wait rolls forward into building another circuit.
Behaving, and not behaving
The two look identical for the first stretch. What separates them is what the tab does next, not what it is doing now.
A first contact that is working
The tab stays blank and the address bar keeps the address you typed. Nothing is redrawn, nothing errors, and the browser offers no message of its own.
Then something appears at once rather than gradually: a header, a form, a plain page. Arrival is sudden because the negotiation was the slow part and the page itself is small.
A first contact that has already lost
The blank stretch runs past the point where it feels like the machine has forgotten the request, and then the browser puts up its own error page rather than anything from the market.
A second attempt behaves the same way and stops at the same stage. Repeatable failure in the same place is a signal. A single slow load is not.
The distinction is repeatability. One long blank stretch tells you almost nothing, because a badly chosen relay is ordinary and invisible. The same stretch, ending the same way, twice, tells you the arrangement is not completing rather than merely taking its time.
It is also worth being clear about what the browser error page means. It is written by the browser, not by the market. It knows the arrangement did not complete. It does not know whether the service is down, and it will mislead you if you read it as though it does.
Safe to do meanwhile
There is very little to do here and that is rather the point. The one thing worth doing is the thing that should have happened before you pressed enter.
- Read the address string againThe cheapest check on this site, and the only one that runs entirely in your head.
- Keep the two addresses where you can see themBoth are printed plainly. Nothing here contacts either of them.
- Leave the tab alonePressing enter again throws away the arrangement in progress and asks for a fresh one.
- Open nothing else in the same windowOther tabs pull on the same client and make the blank stretch longer for no gain.
- Wait past the point where it feels wrongThat feeling arrives well before the mechanism has run out of options.
What makes it longer
Everything that lengthens this wait does so by adding another arrangement that has to succeed, not by slowing down one that already has.
- A relay somewhere in the path that is slow, overloaded or on the far side of the world. Selection does not consider where you are.
- A first visit rather than a return visit, because nothing is set up yet and nothing can be reused.
- Pressing enter again partway through, which abandons the half built arrangement and starts another.
- The service being under load, so its side of the meeting is slow to build even though yours is ready.
- A client that has just started and has not yet finished its own housekeeping with the network.
- Anything else in the session pulling on the same connection, including a page left loading in another tab.
What this card is not. This is not a check on whether the market is up, because nothing on this page contacts anything.
Questions people ask about this wait
Why is the second visit quicker than the first?
Because the path built during the first visit is still there and gets reused. The expensive part is the arrangement, and it does not have to be made again while it holds.
Does a long blank tab mean the address is wrong?
Not on its own. A wrong address tends to fail the same way every time, at the same stage. A slow one varies. Repeatability is the thing to watch.