How VelocityVerify Measures Your Internet
Most internet speed tests are simpler than they look. They download a file, measure the time, and call it done. We go further — because download speed alone is not a reliable proxy for whether your connection will handle real-world use.
I. What We Measure (and Why Each Metric Matters)
Multi-stream parallel TCP download to saturate the pipe using adaptive stream counts (4–12+) rather than a fixed number, producing accurate results on both slow DSL and multi-gigabit fibre.
Same approach as download, reversed. Upload is frequently the bottleneck for video conferencing and remote work, and ISP plans are often highly asymmetric.
Round-trip time to our edge server with no other traffic in flight. Measured as the median of multiple samples, not a single probe.
Standard deviation of latency over multiple probes. High jitter is often more disruptive than high average latency in video calls and gaming.
Latency measured while the link is saturated. This reveals whether router queue management causes lag spikes under load.
- Download speed (Mbps): Multi-stream parallel TCP download to saturate the pipe. We use adaptive stream counts (4–12+) rather than a fixed number, which produces accurate results on both slow DSL and multi-gigabit fibre.
- Upload speed (Mbps): Same approach as download, reversed. Upload is frequently the bottleneck for video conferencing and remote work, and ISP plans are often highly asymmetric.
- Unloaded latency (ping, ms): Round-trip time to our edge server with no other traffic in flight. Measured as the median of multiple samples, not a single probe.
- Jitter (ms): Standard deviation of latency over multiple probes. High jitter is often more disruptive than high average latency in video calls and gaming.
- Bufferbloat grade (A–F): Latency measured while the link is saturated. This is the metric that reveals whether your router's queue management is causing lag spikes under load. See our deep-dive article on the measurement algorithm.
II. Server Infrastructure & Routing
The current test endpoints run on Cloudflare Pages Functions. Cloudflare is a CDN and edge-services provider; this site does not claim a separately operated network of neutral test datacenters. Measurements depend on the route to that endpoint as well as your device, local network and current congestion.
Requests use the site's published API routes, with edge delivery handled by Cloudflare. The application does not provide a separately managed rotating node pool or record a selected physical server region in its optional results database.
III. Measurement Limits
The test uses HTTPS download, upload and latency endpoints. The current API applies payload limits, rate limits and numeric input bounds. These controls do not prove that an ISP cannot detect test traffic, that endpoints rotate, or that a submitted speed matches the physical capacity of a particular connection.
Use repeated tests under consistent conditions. Browser timing, device load, local Wi-Fi, route selection and congestion can all affect measurements.
IV. Hardware-Related Content
Hardware comparisons should distinguish vendor specifications, cited research and direct measurements. A product mentioned in a guide is not, by itself, evidence that every device has been physically tested in a dedicated lab. Check the individual article for its sources, test conditions and limitations.
V. Data & Privacy
Database storage is optional and is disabled unless the required environment bindings are configured. When enabled, the results endpoint accepts speed, latency, jitter, timestamp, and ISP fields. It does not write the visitor's IP address to the results record.
For full data handling details, see our Privacy Policy.
Our Team
- Younes Kirat — Publisher and Site Maintainer
Our Editorial Policy covers how we handle corrections, affiliate disclosures, and editorial independence.