VoIP Readiness Test —
Is Your Network Ready?

Eight measurements run from your browser in roughly 30 seconds: round-trip latency to multiple endpoints, jitter (variance in latency samples), downstream bandwidth via the Cloudflare speed test, upstream bandwidth, NAT type via STUN candidate gathering, WebRTC browser support, the network type reported by your device, and a calculated MOS score using the ITU-T G.107 E-model. The result is a 0–100 readiness score with a category breakdown and specific action items.

Yes. The test runs entirely in your browser. We do not collect your email, store your IP, or send the results to any server. Refresh the page and the test is gone — you can run it as many times as you want.

A browser-based test cannot probe SIP-specific ports (5060/5061), verify QoS/DSCP marking survives across the WAN, or measure long-term stability. Most browser traffic also rides over HTTPS rather than UDP, which is what real VoIP uses. For a comprehensive evaluation we run a passive on-network capture that observes real UDP/SIP behavior over several days — the browser test is a useful first signal, not a definitive verdict.

Wi-Fi adds jitter and packet loss that wired Ethernet does not. If you score lower than expected on Wi-Fi, run the test again on a wired connection at the same site to isolate whether the issue is your Internet circuit or your local Wi-Fi.

On the ITU-T 1–5 scale, anything above 4.0 is good (toll quality), 3.5–4.0 is acceptable for business, 3.0–3.5 is degraded but workable, and below 3.0 means users will complain. The E-model calculation we use accounts for one-way delay and packet loss; jitter affects perceived quality but is captured in our overall readiness score rather than the raw MOS.

NAT failure usually means symmetric NAT, restrictive corporate firewall, or blocked outbound UDP. Cloud VoIP platforms work around these with a TURN relay or a Session Border Controller (SBC), but performance and call quality typically drop. If your test fails here, that is a strong signal to engage a UC consultant before committing to a cloud phone deployment.