HOW TO USE
Run a focused test
- 1Use Lite mode to keep data usage low.
- 2Keep this page visible while latency and throughput are measured.
- 3Compare raw results with the four scenario explanations.
Contact & Suggest NETWORK QUALITY
Measure download, upload, latency, jitter and responsiveness under load.
Temporary test dataThe test transfers random data to and from our same-origin test node. No files or results are stored, and packet loss is not inferred from Fetch failures.
HOW TO USE
WHAT RESULTS MEAN
PRIVACY & LIMITATIONS
The server streams random bytes and discards uploads. Infrastructure providers necessarily process connection metadata such as IP addresses to deliver and protect the service, but AnHot does not save individual test results. Ordinary browser Fetch cannot reliably expose true lower-level packet loss.
UNDERSTAND YOUR CONNECTION
A stable 25 Mbps can support everyday browsing and one HD stream. Larger households, 4K video and big downloads benefit from more capacity.
Upload matters for video calls, cloud backups and sending large files. Consistent performance is often more useful than one brief peak.
Latency is the round-trip delay to this test server. Lower values usually make calls, games and interactive pages feel more immediate.
Jitter describes how much latency changes between samples. A steady connection can feel better than a faster one with large timing swings.
It shows whether the connection stays responsive while busy. A large increase can explain lag during downloads, calls or cloud sync.
This result includes your Wi-Fi or wired link, device, browser, route and server. Test near the router and over Ethernet to isolate Wi-Fi limits.
NETWORK FAQ
Lite mode keeps usage low—up to about 10 MB download and a few MB upload; the actual transfer can be lower.
Every latency value is measured between this browser and the AnHot edge test server—not a game server or the entire internet.
It indicates how responsive the connection remained while download or upload traffic was active, which can matter for calls, browsing and games.
No. Browser Fetch uses reliable transports that can hide lower-level retransmissions, so this test does not publish a misleading packet-loss number.
No. The server streams, counts and discards temporary random bytes without writing them to storage.
Wi‑Fi conditions, competing traffic, browser load, routing and the selected edge node can all change between runs.