Usually feels like
Seconds
It finishes while you are still looking at the screen.
Longer than fetching a page, because something has to be computed before an answer exists, and still far shorter than anything on the minutes band.
The wait, in plain words
Nothing on the screen acknowledges the press. The button may look pressed, and that is all. Behind that stillness the form is travelling, being read, and being answered.
This pause is longer than the one when you open a page, because the market is not handing you something it already has. It is checking a name, a passphrase, a challenge answer and possibly a code, and only then deciding what to send back.
It is also far shorter than anything on the minutes band, because the work involved is small and depends on nothing outside the market. Nothing is being confirmed by a wider network here, and nobody is reading anything by hand.
Underneath, while nothing moves
A form submission is one journey out and one journey back along a path that already exists. It is the same path that brought you the page, so this wait does not pay the arrangement cost again. What it adds is the market's own work in the middle.
That work is deliberately not instant. Passphrase checking on a system of this shape is designed to be slow to compute, because a check that is cheap for the market to run is cheap for anyone else to run over and over. The slowness is a feature, and you are paying a small share of it.
The answer comes back as a whole page rather than as a signal, so what lands is a fresh screen: either the one behind the door, or the sign in screen again with a message on it. A rejection travels exactly the same way an acceptance does.
The one thing that turns this pause into something much worse is a second press.
Behaving, and not behaving
The pause itself tells you very little. What it turns into tells you everything.
A submission being answered
The screen holds still, then replaces itself in one step. Whatever comes back arrives as a complete page rather than as a change to the one you were looking at.
Even a refusal is a healthy outcome here. It means the form arrived, was read, and produced a decision.
A submission that went nowhere
The screen holds still past the point where a page fetch would have finished, and then the browser puts up its own failure rather than the market putting up a message.
Nothing about that tells you whether the form was received. This is exactly the situation in which pressing again is worst, because you may be sending a second attempt against a first that already succeeded.
- A second attempt in flight
- Two submissions carrying the same challenge answer. A challenge is usually good once, so the second fails by construction.
- A failure counted
- It is recorded even though you meant it as a retry. Screens of this shape count attempts, not intentions.
- A cooldown
- Enough counted failures move you out of this band entirely. See a cooldown after failed tries.
- A session you cannot see
- The first attempt may have signed you in on a page you never received, leaving you pressing at a screen that has already let you through.
That last row is the reason to sit on your hands. The screen in front of you is not a record of what the market did. It is a record of what reached you.
If the reply really has failed to come back, the recovery is not another press on the same screen. It is opening the address again and seeing which screen you land on.
Safe to do meanwhile
Everything worth doing here is a form of waiting properly.
- Keep your hands off the buttonThe single most expensive action available on this screen.
- Let the browser finish before judgingA pause that feels wrong is still shorter than the wait it becomes if you interrupt it.
- Open the address fresh if it truly endsA new load shows whether you are already signed in without spending another attempt.
- Have a code ready if one is asked for nextThe screen after this one often wants a code with a life of its own.
- Read what a cooldown looks likeBetter known before you are in one than after.
What makes it longer
Part of this is the network and part of it is what the market has been asked to compute.
- A second submission racing the first, which usually costs an attempt and gains nothing at all.
- Deliberately slow passphrase checking, which is a design choice rather than a fault.
- A challenge that expired between the picture arriving and the button being pressed, turning the answer into a refusal and another round.
- A market under load, where submissions queue behind other submissions.
- A path that has degraded since the page arrived, so the journey out is slower than the one that brought you here.
- A second factor step waiting behind the first, which is a further round trip and not part of this one.
What this card is not. This card is not about being refused, only about the interval before you learn whether you were.
Questions people ask about this wait
Is it safe to press sign in again if nothing happens?
It is the worst move available. The first attempt may already have succeeded on a page that never reached you, and a second one usually fails on a used challenge while still counting as a failure.
Why is this pause longer than loading a page?
Because the market computes something before it can answer. Passphrase checking on a system of this shape is built to be slow on purpose, and the reply is only assembled once the checking is done.