VoIP speed test
Most speed tests answer a question your phone system barely cares about. This one measures throughput, then measures the things that actually decide whether calls sound professional — and tells you how many simultaneous calls your connection can carry.
Can your internet handle business calls?
We check the things that actually decide call quality first, then measure speed. About 20 seconds, nothing installed.
Why we test quality before speed
The test measures jitter and packet loss first, while your line is quiet, and only then runs the transfers. That order is deliberate: measuring timing during a full-speed download would report congestion the test itself created, which tells you nothing about how a normal call behaves.
It also reflects what usually goes wrong. Voice needs about 0.09 Mbps per call, so on any modern business connection bandwidth is essentially never the constraint. When calls sound bad on a fast connection — which is the common case — the cause is timing, not capacity.
If the results look poor
- 1
Re-test on a cable
Wi-Fi causes more call-quality problems than everything else combined. If the numbers clean up on Ethernet, your internet is fine and the work is wireless — position, channels, or an access point too far from the desks that matter.
- 2
Test again with the network quiet
Backups, cloud sync, and video calls all distort timing. If a quiet network tests clean, you have a congestion problem rather than a quality one — and that is exactly what QoS solves.
- 3
Turn on QoS for voice
Your router can put voice packets ahead of everything else. For a connection with capacity but unstable timing, this is the highest-value change available, and it costs nothing.
- 4
Test at your busiest hour
A clean result at 9 p.m. proves little. Run it again when your office is fully working, because that is when your calls actually happen.
How this test works
Forty timed probes measure round-trip time, jitter and failed requests, then two transfers measure download and upload throughput. The first transfer pass is discarded because it carries connection setup. The quality score applies the ITU-T G.107 E-model — the same standard behind our published call measurements — to the measured timing.
Everything runs over HTTPS between your browser and our servers, so it measures the same path a call would take rather than a synthetic one. A WebRTC reflector measuring true media-path behavior packet by packet is in development.
Speed test questions
What internet speed do I need for VoIP?
Far less than almost anyone expects — about 0.09 Mbps per simultaneous call. Ten calls at once fit inside 1 Mbps. If you have any modern business connection, you have many times what voice requires, which is why a speed test alone tells you very little about whether your calls will sound good.
Why does this test measure jitter and packet loss too?
Because those are what actually decide call quality on a connection that already has enough capacity. Speed tells you how much data fits through the pipe; jitter and loss tell you whether it arrives on time and intact. A 500 Mbps connection with unstable timing produces worse calls than a 20 Mbps connection that is rock steady.
Why is upload speed the one that matters?
Because a call is symmetric — you send audio at the same rate you receive it — and upload is usually the smaller number, especially on cable and DSL. Your maximum simultaneous calls is set by whichever direction is slower, which in practice is nearly always upload.
Should I test on Wi-Fi or a cable?
Both, and compare. Test on Wi-Fi first because that is how most people actually work. If jitter or loss look bad, test again on a cable: if the numbers clean up, your internet service is fine and the problem is wireless — which is cheaper and faster to fix than changing provider.
My speed is great but calls still sound bad. Why?
That combination is common and it points away from bandwidth. The usual causes are Wi-Fi interference, a connection saturated at busy times by backups or video, or a router that treats voice like every other packet. Turning on QoS so voice gets priority is the highest-value fix, and it costs nothing.