Internet Speed Test

Results depend on the server you're testing against and current network conditions — some variance between sites is normal. This measures against our own servers, not a third-party network.

Like any speed test, it measures throughput to and from the server it targets — a good proxy for your real-world speed, not a guarantee identical to every destination.

Under 20-50ms is excellent for competitive gaming and real-time calls; under 100ms is fine for most everyday browsing, streaming, and video calls. Above 150ms, real-time activities start to feel noticeably laggy.

Jitter is how much your ping varies between measurements, not the ping value itself. A connection with 20ms ping and near-zero jitter feels smoother and more reliable than one that averages the same 20ms but swings between 5ms and 60ms — that inconsistency is what causes stuttering in calls and games, more than the raw ping number does.

Mbps (megabits per second) is the standard unit for internet speed — what this and every other speed test reports. MBps (megabytes per second) is 8 times smaller, since 8 bits make a byte. A 100 Mbps connection downloads at roughly 12.5 MBps, which is why a file's download progress bar can look slower than your "100 Mbps" plan implies.

Most home internet plans, especially cable and DSL, are asymmetric by design — built to deliver much more download bandwidth than upload, since most everyday use (browsing, streaming, downloads) is download-heavy. Fiber connections often have matched or closer download/upload speeds.

Wi-Fi adds distance, interference from other devices, and walls as variables that don't exist on a direct Ethernet cable — testing over Wi-Fi will almost always show somewhat lower speeds than the same connection tested wired, even though nothing about your internet plan changed.

It's a real, live measurement, not a simulation, so it accurately reflects the connection between your device and the server it tested against at that moment — but results can shift with network congestion, time of day, and which server is used, so treat any single run as a snapshot, not a fixed number.

Shared local infrastructure (like cable networks) can slow down during peak usage hours — early evening is a common slow period — when many nearby households are online at once, similar to rush-hour traffic on a shared road.

Running it two or three times, at different times of day, gives a more realistic picture than a single result, since any one run can be affected by momentary network conditions on either end.

Yes — anything else using bandwidth at the same time (background downloads, streaming, cloud backups) competes for the same connection and can pull your measured speed down.

Yes — a phone downloading updates, a TV streaming in another room, or a laptop backing up to the cloud all share the same connection, so a busy household network can lower what any single device measures, independent of your actual plan speed.

Yes — routing traffic through a VPN adds an extra hop and often encryption overhead, which typically reduces speed and increases ping compared to testing without one. If you want your raw connection speed, test with the VPN off.

Ping to a nearby server is typically well under 50ms on a decent broadband connection; satellite internet is the major exception, often running several hundred milliseconds due to the physical distance the signal has to travel.

It downloads 20MB and uploads 10MB of real data directly against our servers, timing exactly how long each transfer takes, and samples ping 8 times to calculate both the average and the jitter — a genuine live measurement, not a simulated estimate.

No — each test runs live and the result is shown only to you, in that moment. Nothing is saved to an account, a server, or your browser between visits.

Yes — it works in any mobile browser and tests whatever connection your device is actually using at the time, cellular data included.