When a page loads slowly

A page that is taking a long time looks the same whether the delay is in building a path, in finding the service, in the service answering, or in your own connection. There is no stage indicator, no diagnostic, and no message that distinguishes them.

That means any explanation you form while watching a slow page is a guess. Not a wrong guess necessarily, but a guess, and the confident version of it is the thing to be careful about.

1. Wait longer than feels reasonable before doing anything at all.
2. Try another address from the published set, since the three are genuinely different strings.
3. Check whether ordinary browsing is also affected, which is the one test that separates your side from everything else.
4. Stop and come back later. Time is the most effective tool on this list and the least used.
5. Do not start changing settings to make a slow page load. A page that requires a setting change is a different problem from a slow one.

It would be easy to write that a normal load takes a certain number of seconds. It would also be invented, because this site has never loaded any of these addresses and holds no timing data of any kind.

Published timings are worse than useless in this setting. A reader compares their experience to a number somebody made up, decides something is wrong or fine on that basis, and acts on it. Having no number at all leaves you with the correct impression, which is that you cannot tell.

The tiles here count symbols. They are not about slowness and do not pretend to be. They are the same string measurements as everywhere else on the board, present because a panel on this site shows what it can compute and there is nothing computable about a delay it never observed.

That awkwardness is deliberate. A dashboard that always finds a relevant number for every subject is a dashboard that is inventing some of them, and the alternative is a panel like this one where the tiles are honest and slightly beside the point.

There is a specific pattern worth recognising because it is self sustaining. A page is slow, you reload, the reload discards whatever progress existed and starts again, the new attempt is also slow, you reload again. Each cycle feels like an attempt to fix things and each one resets the clock.

From the inside it looks like an address that never works. From the outside it is a page that would have loaded several times over if left alone. There is no way to tell these apart while it is happening, which is why the advice is a rule rather than a judgement call: wait first, always, before doing anything.

The second half of the loop is worse. After several failed reloads people go looking for a different address, find one somewhere, and store it. A slow page has quietly turned into a change of source, and the change was made in the worst frame of mind for making it. The panel on where the address came from is about exactly that moment.

Is a slow load a sign of a problem with the market?

It is not a sign of anything specific. The same appearance comes from several unrelated causes and the screen does not separate them.

Should I keep reloading?

No. Reloading discards progress. Waiting and then trying a different address is the better sequence.