Explore the guide library · Performance testing
Read delay, variation and missing packets separately before deciding what a router upgrade could fix.
A choppy call may happen on a connection with ample download capacity. Real-time communication depends on more than moving a large file quickly. Latency, jitter and packet loss describe different parts of the experience and should be recorded separately.
Understand the three clues
Latency concerns how long an exchange takes. Jitter concerns variation in timing. Packet loss concerns data that does not arrive as expected. Cloudflare includes these alongside throughput and loaded latency when assessing application-oriented internet quality.
Match measurements to the incident
Open the calling application’s supported diagnostic view while the problem is occurring. Note whether the issue affects your outgoing sound, incoming sound, video or screen sharing. A measurement taken after the meeting may miss the condition that caused the interruption.
Use a practical observation table
| Observation | Useful next comparison |
|---|---|
| Delay grows during an upload | Repeat with optional upload traffic paused |
| Timing varies only in one room | Compare the same device nearer the access point |
| Loss persists on wired and wireless paths | Inspect the shared path and service |
Avoid universal pass marks
Different applications calculate and tolerate metrics differently. Use the application’s own guidance and the observed symptom rather than treating one threshold from another tool as a diagnosis. A short sample can also miss intermittent bursts.
Retest the specific repair
After changing a justified setting or moving a device, repeat the same call conditions where practical. Preserve the same application and connection path so the comparison remains meaningful.
A new router may help when the local network is the limitation, but these metrics do not identify that location automatically. Pair them with a wired comparison, household traffic notes and timing. The goal is a stable conversation, not simply a green summary score from a test that used a different route and workload.
Sources and editorial notes
Sources checked 8–9 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.
- Cloudflare: application-oriented internet quality metrics
- Cloudflare: throughput, loaded latency and jitter definitions