| Unit of measurement | Milliseconds (ms) for latency and ping; percentage (%) for packet loss |
| Good ping for general use | Under 100ms; under 50ms preferred |
| Acceptable packet loss threshold | Less than 1% for most applications |
| Common causes of high latency | Physical distance to server, network congestion, Wi-Fi interference, hardware limitations |
| Common causes of packet loss | Congested networks, faulty cables, weak Wi-Fi signal, ISP infrastructure issues |
| Related metric to know | Jitter — variability in packet arrival timing |
Why These Three Terms Matter
When your video call freezes, your game lags, or a web page loads sluggishly, troubleshooting guides almost always point to the same three culprits: latency, ping, and packet loss. Yet most explanations assume you already know what they mean. This glossary defines each term clearly, explains why it affects your everyday experience, and shows how the three concepts connect to one another.
These metrics go beyond simple download speed. You could have a fast connection — measured in Mbps or Gbps — and still suffer poor performance if any of these three are out of range. For a grounding in speed units themselves, see our plain-language breakdown of Mbps vs. Gbps.
| Unit of measurement | Milliseconds (ms) for latency and ping; percentage (%) for packet loss |
| Good ping for general use | Under 100ms; under 50ms preferred |
| Acceptable packet loss threshold | Less than 1% for most applications |
| Common causes of high latency | Physical distance to server, network congestion, Wi-Fi interference, hardware limitations |
| Common causes of packet loss | Congested networks, faulty cables, weak Wi-Fi signal, ISP infrastructure issues |
| Related metric to know | Jitter — variability in packet arrival timing |
Latency, Ping, and Packet Loss Defined
Each term describes a different dimension of how data travels across your network. Here is what each one actually means:
Latency
The time it takes for a single unit of data to travel from your device to a destination server (or vice versa). Measured in milliseconds (ms), lower latency means a more responsive connection. It is determined by physical distance, network routing, and the quality of the connection path.
Ping
The round-trip time for a small data packet sent from your device to a server and back again, also measured in milliseconds. Ping is effectively a practical measurement of latency in both directions combined. It is also the name of the command-line tool used to perform this test.
Packet Loss
The percentage of data packets sent over a network that fail to reach their destination. Even 1–2% packet loss can noticeably degrade voice calls and online gaming. It is typically caused by network congestion, faulty hardware, or a poor signal on a wireless connection.
Bandwidth
The maximum amount of data that can be transferred over a connection in a given time, usually expressed in Mbps or Gbps. Bandwidth is about capacity, not speed of delivery — a high-bandwidth connection can still have high latency.
Jitter
Variability in the delay between arriving data packets. When jitter is high, packets arrive unevenly, which causes choppy audio and stuttering video even if average latency looks acceptable.
Round-Trip Time (RTT)
The total time for a data packet to travel from the sender to the destination and back. RTT is the measurement that ping tests report, and it encompasses both directions of the communication.
It helps to think of your internet connection as a postal system. Latency is how long it takes a letter to arrive. Ping is the round-trip time for a letter and its reply. Packet loss is when some letters never arrive at all. All three problems can exist independently — or compound one another.
For context on the physical devices that shape these metrics at home, the guide to modems, routers, and gateways explains how each device in your home network fits into the picture.
How Each Metric Affects Real-World Use
Not every activity is equally sensitive to these metrics. Understanding which one matters most for what you do helps you prioritize troubleshooting.
20ms
Ping threshold considered ideal for competitive online gaming
Network performance guides widely cite sub-20ms ping as the target for real-time gaming, where fractions of a second affect gameplay.
150ms
One-way latency where voice call delay becomes noticeable
The ITU-T G.114 recommendation identifies 150ms one-way latency as the threshold above which conversational quality degrades for most users.
1–2%
Packet loss rate that begins to affect audio and video quality
Network engineering literature generally identifies packet loss above 1% as the point at which real-time applications such as VoIP and video calls show perceptible degradation.
- Video streaming: Moderately tolerant of latency, but sensitive to packet loss. A single missing data packet can cause buffering or visual artifacts.
- Video calls and VoIP: Very sensitive to both latency and packet loss. Even a 150ms delay becomes noticeable in conversation, and lost packets produce choppy audio.
- Online gaming: Extremely sensitive to latency and ping. High ping — often above 100ms — causes the delayed response commonly called "lag."
- General web browsing: Tolerant of moderate latency because browsers request and reassemble content in ways that mask small delays.
- File downloads: Almost unaffected by latency. Speed (bandwidth) is what matters here.
Consumer electronics specs — including those on routers and smart TVs — often reference latency in other contexts too. The consumer electronics terms glossary covers how the term appears across different device categories.
Wired vs. Wireless and These Metrics
Wi-Fi connections inherently add variability to latency, ping, and packet loss compared to a direct Ethernet cable connection. Radio interference, distance from the router, and competing devices on the same channel all introduce additional delay and potential data loss. If you're experiencing chronic issues with any of these metrics, testing with a wired connection is an important first diagnostic step before contacting your ISP or replacing equipment.
Practical Steps When Something Feels Off
If your connection feels sluggish or unreliable, a few straightforward checks can help identify whether latency, ping, or packet loss is the likely cause:
- Run a speed test with a ping reading. Most free network test tools report not just download and upload speeds but also your current ping in milliseconds. A ping under 50ms is generally considered good for most households; under 20ms is excellent for gaming.
- Run a continuous ping test. On Windows, open Command Prompt and type ping -t google.com; on macOS or Linux, use ping google.com. Watch for timeouts or wildly varying response times — both signal packet loss or instability.
- Check your router placement and connection type. Wi-Fi connections add latency compared to a wired Ethernet connection. If you're experiencing high ping, plugging directly into your router with a cable is a quick diagnostic step.
- Restart your modem and router. Many transient latency and packet loss issues resolve after a full power cycle of both devices.
- Contact your ISP. Persistent packet loss on a wired connection is often a signal of a problem outside your home — on the provider's infrastructure — and warrants a support call.
For broader guidance on the software side of network troubleshooting, our software terms glossary defines related concepts such as firmware and cache that often come up during router troubleshooting sessions.