How to Read Your Speed Test Results Correctly

You ran a speed test. Numbers showed up on your screen. Now what? Most people glance at the download figure, decide things look fast or slow, and close the tab. That approach misses most of what the test is telling you.

A speed test result is more like a health snapshot of your connection than a single grade. Each number measures something different. A connection that looks great on one metric can still make your video calls choppy or your games unplayable. This guide walks through every number on a typical speed test result. You'll learn what each one means in real life and how to use it to figure out if your internet is working the way it should.

The Five Numbers on a Typical Speed Test Result

Open any speed test and you'll see five metrics: download speed, upload speed, ping, jitter, and packet loss. Some tests show all five right away. Others bury jitter and packet loss in a details panel. No matter where they appear, all five matter.

Here's a quick overview before we go deeper on each one:

• Download speed - How fast data travels from the internet to your device. Measured in Mbps (megabits per second).
• Upload speed - How fast data travels from your device to the internet. Also in Mbps.
• Ping - The time it takes for a signal to make a round trip to a server and back. Measured in milliseconds (ms).
• Jitter - How much your ping varies from one measurement to the next. Also in milliseconds.
• Packet loss - The percentage of data packets that never arrive at their destination.

The rest of this guide covers each one in detail. It shows how to read different combinations of results and explains when you should retest before drawing conclusions.

Download Speed: What the Number Actually Means

Download speed is the metric most people focus on — and for good reason. It controls most of what people do online. Streaming video, loading web pages, pulling files from the cloud, downloading game updates — these are all download-heavy activities.

The number is in Mbps. One megabit is one million bits. There are eight bits in a byte, so a 100 Mbps connection can theoretically move about 12.5 megabytes per second. In practice you get a bit less due to protocol overhead, but that ballpark holds.

What counts as "good" depends on what you're doing and how many people are using the connection at once. A number that's fine for one person browsing can fall short for a household streaming multiple 4K videos.

These numbers are for the whole connection — not per device. If your plan gives you 100 Mbps and four people stream at once, each stream competes for a share of that 100 Mbps. A single 4K Netflix stream uses around 15–25 Mbps. Four of them can push 80–100 Mbps on their own. That leaves almost nothing for everything else.

Also worth noting: the FCC's definition of broadband moved to 100 Mbps download in 2024. Many providers still sell plans below that. They work fine for light use — but if your household has multiple active users, 25 Mbps isn't enough.

Upload Speed: Why It's Lower and When It Matters

If you're on a cable or DSL connection, your upload speed will almost certainly be a fraction of your download speed. This isn't a malfunction. It's by design.

Cable and DSL infrastructure was built when home internet use was one-directional. People downloaded web pages, music, and files. They didn't upload much at all. So providers gave far more bandwidth to the downstream direction. A cable plan advertised as 200 Mbps might give only 10–20 Mbps upload. That gap is baked into the technology.

Fiber is different. Because fiber uses light signals over dedicated lines, upload and download channels can be balanced. Many fiber plans give symmetric or near-symmetric speeds — 500 Mbps down and 500 Mbps up, for example.

For years, slow upload didn't matter much for most households. That changed when video calling became a daily thing and more people started working from home. Here's when upload speed becomes the bottleneck:

• Video calls - Every video call sends your camera feed upstream. Zoom HD calls use around 1.5–3 Mbps upload per person. If multiple people in the house are on calls at once, upload becomes the limit.
• Live streaming - Streaming to Twitch or YouTube in 1080p needs 4–6 Mbps upload sustained. 4K streaming pushes 15–25 Mbps upload.
• Cloud backups - Automated backups to iCloud, Google Drive, or Backblaze use upload in the background. On a slow upload connection, big backups can take hours and get in the way of other tasks.
• Uploading large files - Sending a 2 GB video file to a colleague can tie up a slow upload connection for a long time.
• Gaming - Online games use very little bandwidth in either direction. Most games need only 1–3 Mbps upload, so this is rarely the problem.

If your upload speed is consistently under 5 Mbps and you work from home or make frequent video calls, it's worth fixing. Either upgrade your plan or switch to a provider with better upload speeds.

Ping: What the Millisecond Number Actually Means

Ping is the metric most people understand the least. It's often the one that decides whether a connection feels responsive or sluggish.

The number is in milliseconds (ms). One millisecond is one thousandth of a second. The test sends a small signal to a nearby server and measures how long the round trip takes. That time is your ping — also called latency.

Why does it matter? Every interaction with an online service involves round trips. When you click a link, your browser sends a request and waits for the response. When your game character moves, your input travels to the game server and the result comes back. The faster those round trips complete, the more responsive everything feels. Think of ping like the delay in a phone call — even a half-second gap makes a conversation feel awkward.

For most browsing, a ping under 100ms is unnoticeable. For gaming and live video calls, the threshold is much tighter. Here's how different ping ranges translate to real-world experience:

One important note: the ping in a speed test is measured to a nearby test server — not to the actual services you use. Your ping to a game server in another country will be higher than what the speed test shows. A 15ms ping in a test might be 60–80ms in an actual game if the server is far away. That's normal. The speed test ping is a baseline indicator, not an exact figure for every service.

Ping on Wi-Fi is also consistently higher than on a wired Ethernet connection. If your speed test shows 40ms on Wi-Fi, you might get 8–15ms plugged directly into your router. Wireless signals add processing delays and occasional retransmissions that increase latency.

Jitter: The Number Most People Ignore

Jitter measures how consistent your ping is over time. It's the difference — in milliseconds — between your fastest and slowest ping measurements during the test.

Here's why it matters more than most people realize. A connection with a 40ms average ping and 2ms jitter is more reliable for video calls than one with a 20ms average ping and 30ms jitter. The second connection's ping varies so much that it creates gaps and bursts in the data flow. That's exactly what turns a video call into a pixelated mess.

Video and audio streaming apps work by buffering a small amount of data ahead of playback. That buffer absorbs minor variations in timing. But when jitter is high, packets arrive in clusters and then gaps. This drains or overwhelms the buffer and causes stuttering, freezing, or robotic audio.

Some practical jitter thresholds to know:

• Under 5ms - Excellent for everything including real-time voice and video. You won't notice any variability.
• 5-15ms - Generally fine for video calls and most online activities. Occasional minor issues are possible but rare.
• 15-30ms - Noticeable on real-time apps. Video calls may drop quality or stutter. Gaming can feel inconsistent.
• 30ms+ - Problematic. Video calls become unreliable, gaming feels laggy, and voice calls have audio artifacts.

High jitter is often a sign of a specific problem rather than general connection slowness. Common causes include a congested Wi-Fi channel, interference from nearby networks, an overloaded router, or a problem with the coaxial cable line coming into your home. If you have good ping but high jitter, switch from Wi-Fi to a wired connection and retest. That's the first diagnostic step.

Packet Loss: Why Even 1% Is a Red Flag

Packet loss is the percentage of data packets that leave your device but never reach their destination. Most speed tests show it as a percentage. On a healthy connection, packet loss should be 0% — or so close to 0% that it reads as zero.

One percent sounds trivial. It's not. Here's the problem: the internet's core protocols assume occasional packet loss and respond to it aggressively. When your computer detects dropped packets, it slows down transmission to give the network room to recover. This is called TCP congestion control. It causes big speed reductions even from small amounts of loss.

In practice, 1% packet loss can reduce a connection's effective throughput by 20–50% depending on the protocol and round-trip time. At 5% loss, some protocols essentially stop. Real-time apps like voice calls become unusable.

For gaming and voice calls, the impact is even more direct. Games and VoIP use UDP rather than TCP. UDP doesn't automatically retry dropped packets. A dropped UDP packet is simply gone. In a game, that means your character teleports or actions get missed. On a voice call, it means audio cuts out.

If your speed test shows any measurable packet loss — even 0.5% — it's worth investigating. Likely causes include:

• A loose or corroded coaxial cable at the wall, splitter, or where the line enters the house
• A failing network card in your router or modem
• Wi-Fi interference causing the wireless radio to drop packets before they reach your router
• ISP-side congestion or infrastructure problems in your area
• A failing cable or DSL modem (modems wear out over time and start logging uncorrectable errors)

A quick way to separate your local network from the ISP's network: test with a device plugged directly into your modem via Ethernet, bypassing the router and Wi-Fi entirely. If packet loss disappears, the problem is in your local network. If it persists, it's upstream.

What a Speed Test Result Screen Actually Shows

Before reading numbers, it helps to know where each number lives on a typical result display. The layout below shows the common arrangement you'll find on most major speed test services.

Notice in the example above that upload speed (22 Mbps) is much lower than download speed (247 Mbps). That's a classic cable connection result — nothing is wrong. It's just the natural gap built into cable technology. The ping of 18ms and jitter of 4ms show a fast, stable connection that's great for gaming and video calls.

How Download Speed Maps to Common Activities

The chart below shows the bandwidth each common activity needs. These are the sustained speeds required for a good experience — not peak bursts. Keep in mind these are per-stream or per-device figures. Multiply by the number of users doing the same thing at once.

The key takeaway: gaming isn't as bandwidth-hungry as most people think. It needs only around 5 Mbps. What gaming actually needs is low, stable ping and minimal jitter. Meanwhile, cloud backups and multi-device 4K streaming are the real bandwidth consumers in a typical household. If your connection feels slow during backups, that chart explains why.

The Gap Between Your Plan Speed and Your Test Result

This is one of the most common points of confusion. Your ISP sells you a plan described as "up to 300 Mbps." You run a speed test and get 210 Mbps. Are you being cheated?

Not necessarily. The phrase "up to" is doing a lot of work in that ad. ISPs sell shared bandwidth. The actual throughput you get at any moment depends on factors they don't fully control: network congestion at your local node, signal quality on the line to your house, the age of your modem and router, and the distance to the test server.

A rough guide to reading the gap:

• Within 20% of plan speed - Normal variation. No action needed. A 300 Mbps plan delivering 240–260 Mbps is performing as expected.
• 20-40% below plan speed - Worth investigating. Try retesting at different times of day. Test via Ethernet directly from the modem. If the gap stays, contact your ISP.
• More than 40% below plan speed - Likely a problem. Could be a failing modem, a bad cable line, network congestion in your area, or throttling. Document your test results and contact your ISP with data.

There are also real reasons you may never see your full advertised speed in a test. If you're testing over Wi-Fi, wireless overhead and interference will reduce measured throughput compared to a wired connection. If your device is several years old, its network card may not be able to sustain the speeds the line can deliver. If you're using a modem rented from your ISP, it may be an older DOCSIS 3.0 model that caps out below your plan's speed.

The best baseline test is always: device on Ethernet, connected directly to the modem (not the router), tested at off-peak hours (early morning on a weekday). That result is the closest you'll get to your actual line performance stripped of local variables.

Reading the Combination: What Different Result Patterns Mean

Individual numbers only tell part of the story. The combination of metrics — and which ones are good while others are bad — often points directly to the likely cause and the right fix.

When to Retest and How Many Tests to Take

A single speed test result isn't reliable data. Speeds change throughout the day. One test snapshot can be misleading in either direction — a brief burst might make things look better than they are. A short congestion event might make things look worse.

Before drawing conclusions about your connection, follow these guidelines:

Run at least three tests back to back. Average the results. If one result is way off from the others, that test likely caught a brief event. Discard it.

Test at different times of day. Run tests in the morning, afternoon, and evening on separate days. ISP congestion shows up most clearly during peak evening hours (roughly 7–10 PM on weekdays). If your evening speeds are consistently 30–50% lower than your morning speeds, that's a congestion pattern worth reporting to your ISP.

Test on different days of the week. Weekend evenings are often the worst for congestion since more people are home. If you want to see your connection's best performance, test on a Tuesday or Wednesday morning.

Test over Ethernet before concluding anything definitive. If you've only tested over Wi-Fi, you've tested your Wi-Fi setup as much as your internet connection. Plug into the router with an Ethernet cable before making any decisions about upgrading your plan or calling your ISP.

Use the same test server. Speed test results vary by server location. For consistent comparisons, lock onto the same server in each test. Most speed test services let you choose the server manually.

Check modem event logs if you have persistent issues. Most cable modems have a web admin interface (usually accessible at 192.168.100.1) that shows error logs. Uncorrectable error counts in those logs are a direct sign of line quality problems that no speed test captures.

Good, Acceptable, and Poor Thresholds at a Glance

When you have all five metrics from a speed test, this reference table lets you quickly grade each one without doing any math.

Print this table or bookmark this page. When you run a speed test, you can grade each metric and get a clear picture of what's working and what's not.

Putting It All Together

Reading a speed test well isn't about memorizing numbers. It's about understanding what each metric measures and which ones matter for your situation. A gamer needs low ping and minimal jitter more than raw download speed. A household of streamers needs high download speed more than upload. A remote worker on video calls needs both decent upload speed and low, stable jitter.

The most common mistake people make is treating download speed as the only number that matters. Then they're confused when calls are choppy or games are laggy despite a seemingly good speed test result. Fast download means your connection can move data quickly. Low ping, low jitter, and zero packet loss mean your connection can move data reliably. You need both for a connection that actually feels good to use.

When results look off, the troubleshooting approach is simple: isolate variables one at a time. Start with Ethernet versus Wi-Fi. Then modem-only versus router. Then different times of day. Each step narrows down whether the problem is in your home, your equipment, or your ISP's network. With a few data points and the context from this guide, most internet problems point to a clear cause and a clear fix.