Connection quality test
A speed number does not tell you why calls stutter and games lag. This test measures the things that do — packet loss, jitter, latency, and how much your latency rises when the line is busy (bufferbloat) — and grades them A to F with the fix for each.
Round trip to our Frankfurt server and to the nearest Cloudflare edge, idle.
How much consecutive round trips vary. Under 10 ms is excellent, under 30 ms fine.
Estimated from 20 HTTPS samples; any request unanswered within 3 s counts as lost.
How much latency rises while the line is busy, graded A to F.
A short 5 MB download and upload to Frankfurt — a rough figure, not a speed test.
Can your browser reach our IPv6-only host?
| Use | Verdict | Why |
|---|---|---|
| Video calls | Waiting | Run the test to see a verdict. |
| Online gaming | Waiting | Run the test to see a verdict. |
| Streaming | Waiting | Run the test to see a verdict. |
HTTPS measurements from your browser; loss and throughput are estimates. Latency to Frankfurt depends on distance — the nearest-edge figure shows what your own access network adds. Full speed test · IPv6 test
Your results
Press Start. The test measures idle latency with ten samples, then keeps measuring latency while downloading and then uploading for a few seconds each, and reports loss, jitter, idle and loaded latency, throughput in both directions and a bufferbloat grade. One run moves about 20 MB.
Packet loss
The share of probes that got no answer. Sustained loss above 1 % breaks real-time applications; loss that appears only under load points at bufferbloat or a saturated link; loss on Wi-Fi only points at interference or distance.
What packet loss is acceptable?
0 % on a healthy wired line; occasional single losses on Wi-Fi are normal. Anything above 1 % sustained is a fault worth chasing — cable, modem, Wi-Fi channel or the provider.
Jitter
The variation between consecutive latency samples. Voice and video codecs buffer to absorb it, so steady 40 ms with 2 ms jitter sounds better than 20 ms with 30 ms jitter.
What is a good jitter?
Under 10 ms is excellent, under 30 ms is fine for calls and games, above 50 ms causes audible and visible problems. Wi-Fi is the usual cause; a cable usually brings it near zero.
Latency to servers worldwide
Idle latency to our Frankfurt server is shown with the distance-based expectation, so you can see what your access technology adds. Measurements to servers on other continents are planned as we add test locations; until then the ping test gives the same single-server figure.
Bufferbloat (latency under load)
When your upload or download is saturated, packets queue in the modem or router; oversized queues add hundreds of milliseconds to everything else — the reason a call breaks up when someone starts a backup. We measure latency idle and under load and grade the increase: A under 30 ms, B under 60, C under 100, D under 200, F above. C or worse is fixable and the fix is usually dramatic.
How to fix lag and packet loss
Cable before Wi-Fi; then the router.
Wi-Fi vs cable
Run the test wired and on Wi-Fi. If loss and jitter disappear on the cable, the fix is Wi-Fi: 5 GHz band, a less crowded channel, a closer access point or a mesh unit. If they stay, the problem is the line or the modem.
Router SQM / QoS settings
Enable SQM (smart queue management: cake or fq_codel) on routers that have it (OpenWrt, many prosumer models) and set the bandwidth slightly below your measured speeds; this keeps queues short and typically turns an F into an A. Routers without SQM often have a QoS or gaming mode that helps less. Then re-run the test.
Frequently asked questions
What is a good jitter level?
Under 10 ms is excellent and under 30 ms is good for calls and gaming. Above 50 ms, audio and video start to break up.
What is jitter testing?
Measuring the variation in latency between consecutive packets, usually by sending a series of probes and comparing their round-trip times — what this test does with ten idle samples and continuous samples under load.
Is 7 ms jitter bad?
No. 7 ms jitter is well within the comfortable range for any application.
Is 35 ms jitter bad?
It is on the edge: calls still work but may glitch, and games may feel inconsistent. Most often it is Wi-Fi; test on a cable to confirm.
Why do I have packet loss?
Wi-Fi interference or weak signal, a damaged cable or connector, a failing modem, an overloaded link (bufferbloat), or congestion at the provider. The test's wired/wireless comparison and the loaded-latency result narrow it down.
What is bufferbloat?
Excessive queuing of packets in a modem or router when the link is full, which makes latency balloon during downloads and uploads. It is fixed by queue management (SQM) on the router, not by a faster plan.
Measured live from your browser against our own server in Frankfurt (probe-fra1) and the nearest Cloudflare edge; grades follow the Waveform/Cloudflare bufferbloat scale. Results are never stored.