The page arrived halfway and then stopped

Mars market mirrors

marshjhtog245vzjzcicnmv2ci6yljibvdm4pngq5kmkfvcutppboxad.onion

marsiujka6lrsaqpnxiwvknthhzsrlmq77mnl2fi62guc4lwxif65syd.onion

marsmtbwtxkohhpu34m4jkwcntian7n257wsex5tbkmsjdjrsz6me3yd.onion

Printed as supplied, in no order. Nothing here is watched or timed, so an address that opens is not proof of anything. More about the set

Some of the page is there. The rest is not. A button does nothing, or a section is blank, or the layout has collapsed into something that looks broken.

This is the state that costs people the most money on this site, not because it is severe but because of what it makes people do next.

Responsible: The network. A connection that carried part of a response and then stalled.
Usually blamed on: The market, for a broken page, or the browser, for being unreliable.
What follows: Partial loads are ambiguous by nature. What follows is a waiting rule, because acting on a partial page is what turns this into an expensive case.

Why pages arrive in pieces

A page is not one thing. It is a document plus everything the document asks for, fetched over the same connection through the same relays. Any one of those fetches can stall while the others succeed.

On the ordinary web this is rare enough to be surprising. Over Tor it is routine, because the path is long and every hop is a place where a transfer can lose momentum. A page missing a piece is not evidence of anything on the far end.

The dangerous version

The dangerous version is a page that half loads after you did something. Submitted an order. Sent a payment. Confirmed a form. The response never fully arrived, so you have no idea whether the action landed.

This is where people repeat the action, and repetition is described in full under acting twice. The network created the ambiguity. The duplicate was created by the reader. Both statements are true and only the second one is recoverable.

What to do with a partial page

Do not click anything on it. A half rendered page may be missing the piece that would have told you the state.
Reload it properly rather than interacting with what is there.
If reloading is slow, request a new circuit once and try again.
If the action involved money, go and find the record before doing anything else at all.

The last one is the whole page in a line. Find the record. Not a confirmation message, which is the thing that went missing, but the underlying record that exists independently of any page.

What follows from getting it right

You treat a partial page as a display problem rather than as information. A page that failed to arrive has told you nothing about your account, your order or your money, and reading meaning into a blank section is how people talk themselves into a second transfer.

The quieter benefit is that you stop blaming the market interface for something that is a property of long routes. That matters mostly because it keeps your judgement of the market attached to things the market actually did.

Why turning scripts back on does not help

A common response to a broken looking page is to lower the browser security level, on the theory that something was blocked and that is why the page is incomplete. Occasionally that is the reason. Usually it is not, and the cost is permanent while the benefit is one page load.

Check the difference before changing anything. A page blocked by your settings fails the same way every time, immediately, and looks the same on every attempt. A page interrupted by the network fails differently each time and often works on the next try.

If it is genuinely the settings, that is a decision to make deliberately, knowing what is being given up. It is not a thing to do reflexively at eleven at night because a section was blank.