Usually feels like
Minutes
You stay at the keyboard and it finishes there.
A stalled transfer has no deadline the browser recognises, so it can hold a tab open long past the point where anything useful is going to arrive.
The wait, in plain words
A half arrived page is easy to recognise once you have seen one. Text with no layout. A table with a header row and nothing underneath it. A menu that is a bare list of links. The page looks like a document from before anybody thought about presentation.
Sometimes it is the other way round. The shell is fine, the middle of the page is blank, or the last section simply stops in the middle of a sentence and never resumes.
The browser will keep spinning on this for a long time. It has been handed part of an answer, and it has no way of knowing that the rest of the answer is never coming.
Underneath, while nothing moves
A page is not one delivery. The first response carries the markup. The browser reads it, finds references to stylesheets, scripts and images, and asks for each of those separately. On an ordinary connection those extra requests are almost free. Over a circuit they all travel the same long route and compete with each other for it.
If the path degrades after the first response, you keep whatever already arrived and lose the rest. That is the classic half page. The market answered, the answer began, and the road closed behind it.
There is a nastier variant. A transfer can be left open rather than closed. The far side sent some bytes and then neither finished the response nor dropped the connection, or a relay in the middle vanished without telling either end. The browser is waiting for a length it was promised. It will keep waiting well past the point where a person would have given up, because nothing has told it that the sender is gone.
A half page therefore says more about the network than about the market. The market answered. Something reached you. Whatever failed, failed after the shop had already done its work, and that is useful to know when deciding whether to rebuild the path or wait for the market to recover.
It also explains why the page looks the way it does rather than looking broken in some other fashion. Markup arrives first because it has to. Everything that makes a page look like a page is referenced from inside it and cannot even be asked for until the markup is read. So the failure mode of a route that dies part way through is always the same shape: the words survive and the presentation does not, because the words were in the delivery that got through.
Behaving, and not behaving
The difference worth drawing is between a page that is still going to finish and a page that is already over.
A transfer still in progress
Content is still appearing, even slowly. Images fill in, a blank section gains text, the layout snaps into place a piece at a time.
What the browser reports at the bottom of the window keeps changing, which means bytes are still arriving from somewhere.
A transfer that has stalled
Nothing has changed for a long stretch and the tab is still busy. That is a connection nobody closed rather than one that is still working.
Reloading gives you the same partial page breaking in the same place, which points at something reproducible rather than at bad luck.
A stalled transfer will not recover, and the fix for it is a new path rather than more patience. That is the card before this one. A slow transfer will recover, and interrupting it throws away everything that had already arrived.
One exception is worth holding on to. If the page you are half looking at is a search result or a long listing, the market may simply be slow to produce the contents, and the shell arriving first is exactly what that looks like. That is a different wait wearing the same clothes.
Safe to do meanwhile
The practical problem is rarely the page itself. It is whatever you had already typed into it.
- A form you had half filled in
- Select what you typed and copy it out of the browser before you touch reload. A reload discards it and nothing brings it back.
- A page that came from a button press
- Reloading may resubmit the thing you pressed. Navigate to the page fresh instead. See the order going through.
- A page you were only reading
- Nothing is at stake. Ask for a fresh path and request it again.
- Copy anything you typed before reloadingIt is the only part of a half page that cannot simply be fetched again.
- Give a slow transfer room before you kill itBytes still arriving are bytes you will not have to fetch a second time.
- Ask for a fresh path once it has truly stoppedA stalled connection does not repair itself, however long you watch it.
- Notice that the market answered at allStructure without contents is proof the shop was reachable a moment ago.
What makes it longer
What lengthens this is either the path or the amount of it you asked for at once.
- A congested relay somewhere in the middle, which punishes the many small requests more than the first large one.
- Several tabs pulling through the same path at the same time.
- A heavy page, where the markup is small and the things it references are not.
- Reloading at once, which throws away what arrived and starts the entire delivery again from nothing.
- A path that has already failed once, kept in service because rebuilding felt like effort.
What this card is not. This card is not a diagnosis of your browser settings and it does not describe what any market serves on any page.