Latency

Two clocks that should roughly agree.

What this check is

This check times the same conversation two ways: how long the browser takes to fetch from the server's edge, measured inside the page, and how long the network handshake itself took, measured by the server. For a browser sitting where it claims to sit, the two numbers live in the same neighbourhood.

What Tells reads

The median browser-to-edge fetch time measured in the page
Cloudflare's TCP (and QUIC, when present) round-trip times for the connection

How to read your result

Warning: The browser's measured latency is far higher than the handshake's: something (a remote browser, a relay, an extra hop) is between the page and the connection it arrived on.
Pass: The two clocks roughly agree.

Why it matters

Latency disagreement is a soft signal with a hard cause. A browser driven remotely, streamed from a data centre, or tunnelled through relays cannot make its in-page timing match the handshake timing of the connection it presents, because the extra distance is real. On its own it proves little; next to a datacenter finding it corroborates the story.

Where this matters most

Across the platforms Blowhorn works with, rated in the platform guide (H = matters a lot, M = contributes, L = no public evidence; tags mark vendor-stated, reported, or inferred evidence):

X (M): non-human rates and timing regularity are named enforcement triggers [Vendor]
Reddit (M): predictable request timing is a named detection mechanism [Reported]

Everywhere else in the set this one rates Low.

In your report

Find it in the checks table on the tool page, with the detail in the Resource timing section. The same findings appear in the report JSON under verdict.reasons, and the agent guide explains how to read them programmatically.