How a speed test works
A browser test measures a particular network path at a particular time. Understanding the units and destinations makes the result useful without treating it as a universal score.
→Averages use accepted visitor tests for the selected country, provider and mode. Small samples may not represent all customers. Missing measurements remain blank.
A browser test measures a particular network path at a particular time. Understanding the units and destinations makes the result useful without treating it as a universal score.
InternetSpeedGeo uses Cloudflare requests in three approximately ten-second windows: latency, download, then upload. Throughput comes from transferred data and elapsed time. Latency and jitter come from the library’s summaries. The separate Ping page instead times HTTP requests to this website. Neither is equivalent to a game server’s ICMP latency.
A browser test measures a particular network path at a particular time. Understanding the units and destinations makes the result useful without treating it as a universal score.
→A controlled wired comparison helps isolate the part of the connection that is slow. Change one condition at a time so an improvement has an interpretable cause.
→Different results can both be real. A result depends on endpoint, route, browser, traffic and measurement method; the largest number is not automatically the most accurate.
→A fast download can coexist with lag. Delays and their variation affect conversations and games, and need a different investigation from raw throughput.
→A plan’s advertised speed is not the same as the speed of every download. Device links, overhead, content servers and shared use all affect the experience.
→