A video call stutters, the picture freezes, and someone says the internet must be slow. Often it is not slow at all. You can run a speed test, see a healthy number, and still have a call that breaks up every few minutes. The problem is usually not how much data the connection can carry, but how reliably it carries it.
Understanding the difference turns a frustrating mystery into something you can actually check and, often, fix.
Four things that decide whether a call works
When people say "fast", they usually mean one of four different measurements:
- Bandwidth is how much data can move per second, measured in megabits per second (Mbps). It decides how quickly large files transfer and how many devices can share the connection.
- Latency is the round-trip time for data to reach the other end and come back, measured in milliseconds (ms). It decides how responsive the call feels and how much the software can correct for problems.
- Jitter is how much that latency varies from moment to moment. High jitter means packets arrive unevenly, which is what causes robotic audio and stuttering video.
- Packet loss is data that never arrives. Even a small percentage can make a call unusable, because voice and video would rather have every packet late than a few missing entirely.
A speed test tells you about the first one. Calls are usually broken by the other three.
Why a speed test misses it
A speed test measures throughput over a short window and reports an average. That average hides the details that matter for a call. A connection that is mostly fast, but briefly stalls every thirty seconds, can average out to an excellent number while making every call miserable.
It is also a single measurement at a single moment. The call might be happening later, on a different network, or while someone else in the house is uploading a large file. A number from one moment cannot describe a connection that changes.
Common causes, and what usually helps
In practice, a handful of causes explain most poor calls:
- Wi-Fi at the edge of its range. Distance and walls reduce signal, which raises latency and loss. Moving closer to the router, or using a wired connection, often fixes it outright.
- A busy or crowded channel. In a block of flats, many networks compete for the same radio space. Switching to a less crowded band can help.
- Something else using the connection. A large upload, a cloud backup or a game update can starve a call for the few seconds it needs. Pausing it often restores quality immediately.
- The connection itself, not the device. If every device on the network is affected at the same moments, the problem is upstream of your equipment.
- The other end. Sometimes your connection is fine and the far side is the one struggling. If only one person freezes, it is worth checking before assuming it is you.
How to actually see the problem
The useful question is not "how fast is my connection" but "is it steady right now". That needs a continuous view rather than a single test.
A browser-based monitor such as Conntivity measures round-trip time every second and shows it over time, so a brief spike or drop is visible instead of averaged away. Watching it while the call is struggling tells you within a minute whether the problem is latency, stability or an outright outage. That is often enough to decide between moving closer to the router, pausing another transfer, or contacting the provider.
For a deeper look at the path itself, native tools that show the route to a server are the right next step. MyEvent Labs builds netdx for exactly that kind of path analysis.
A short habit that saves a lot of frustration
Before an important call, give the connection a quiet minute. Close large uploads, sit near the router if you can, and glance at a live latency readout rather than trusting a single speed number. If the line is steady, the call probably will be too. If it is not, you have found the problem before anyone else notices it.