Latency is the time information takes to travel through a network or complete a network exchange. It affects how quickly a request can receive a response, so menus, account operations and channel startup can feel slow even when enough data eventually arrives. Buffered video can tolerate a steady delay better than interactive conversation because it plays material already received. Latency should therefore be interpreted alongside sustained throughput, packet loss and the player's buffer, rather than treated as a single verdict on streaming quality.
Latency and Live delay
Encoding, packaging and the playback buffer add live delay beyond network latency.
How it works
A new request may require name resolution, connection establishment, security negotiation and a server response before useful media begins. Some stages need several exchanges. Longer round trips can lengthen that startup sequence even if the subsequent media transfer is fast. The exact sequence depends on reused connections, cached information and the application's delivery method.
Recognizing the symptom
A long wait before the first picture with smooth playback afterward differs from frequent pauses after playback begins. The former can involve setup and response delays; the latter can involve inconsistent delivery or insufficient usable capacity. Both symptoms deserve precise reporting. Saying only that the internet is slow discards the distinction that helps narrow the investigation.
Making a useful comparison
Compare startup time separately from continuous viewing. Repeat a channel change after the application has already established connections, then compare another permitted network if practical. Record whether all requests are slow or one endpoint is affected. A ping result can provide supporting context, but it does not measure account processing, media packaging or decoding delays.
An illustrative example
A distant endpoint takes several seconds to start a channel, then supplies enough media for uninterrupted viewing. Another endpoint starts sooner with the same picture bitrate. That difference may concern setup or response time; it does not establish that the first endpoint lacks enough sustained delivery capacity.
Practical actions
- Separate startup from playback symptoms
- Compare routes
- Record repeatable results