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.
What to check
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.
Worked example — illustrative, not a measured result
If a download transfers 25 megabytes in two seconds, its simple payload rate is 100 megabits per second: 25 × 8 ÷ 2. Protocol overhead and the test library’s aggregation can change the final reported rate. This calculation explains units; it is not a claim about your connection.
What to do next
Pause large background transfers and keep the device in its normal location. Record the connection type, VPN state and time, then repeat under comparable conditions. Test data counts against a metered plan. An unavailable value should stay unavailable; a failed request is not evidence of zero service speed. Read the methodology before comparing another test engine.