Idle latency
How long a request takes when the connection is mostly quiet. Lower is generally better for interactive use.
A fast download number can still hide delay and instability. Use the four connection vitals to decide which test or troubleshooting step actually fits the symptom.
How long a request takes when the connection is mostly quiet. Lower is generally better for interactive use.
How much delay appears while the connection is busy. A line can have excellent idle latency and still become sluggish under load.
How much latency varies between samples. Real-time audio and games prefer consistent timing, not only a good average.
How much data the line can move. It matters for large transfers and high-bitrate streaming, but it does not replace responsiveness.
When a bottleneck queue fills, packets can wait behind bulk traffic. The connection may still transfer data quickly while clicks, voice packets and game inputs wait in the same queue. That is the core experience the loaded-latency test is designed to expose.
If idle latency is good but upload-loaded latency rises sharply, upload queueing is the likely pattern. If both directions rise, queue management may be weak in both directions. If idle latency is already high before load, distance, routing, VPN, wireless or access technology may matter more than bufferbloat.
This page explains the signals; these tools perform the measurements.
Measure idle, download-loaded and upload-loaded latency plus jitter and throughput.
Understand why a connection can stay fast while becoming unresponsive.
Use a controlled wired retest to isolate the local wireless path.
Use only after the measurements point to queueing under load.