internet speed test

Internet Speed Test Guide: Check Download, Upload, Ping and Jitter

Learn how to run an accurate internet speed test, read download, upload, ping, and jitter results, and decide what to fix next.

For anyone trying to understand whether their connection is fast enough or simply unstable, the fastest path is to stop guessing and measure the connection in a repeatable way. A single result is useful, but a pattern across device, room, time of day, and connection type is far more powerful.

Bandrift focuses on the numbers that explain real internet experience: download speed, upload speed, ping, and jitter. Use the Bandrift speed test before and after each change so you can see whether the fix actually helped.

Start With the Right Baseline

The first step is a clean speed test baseline. Run the test from the same device and the same location, then repeat it after one controlled change. This keeps you from mistaking normal variation for progress.

Run two or three tests and compare the middle result.
Record the time, room, device, and whether you used Wi-Fi, Ethernet, VPN, or a mesh node.
Pause streaming, cloud sync, game downloads, and system updates while collecting a baseline.
When possible, run one Ethernet test near the router to separate ISP performance from Wi-Fi behavior.

Common Signs to Watch

Most home network problems leave clues. If you can name the symptom precisely, you can choose the next test instead of changing random settings.

download results that change from test to test
good Mbps but laggy calls or games
confusing upload, ping, or jitter numbers
different results on phone, laptop, Wi-Fi, and Ethernet

Write these symptoms next to your test numbers. For example, "upload dropped during backup" or "Wi-Fi was weak in the bedroom" is much more useful than simply writing "slow."

What the Speed Test Numbers Mean

Download speed affects streaming, browsing, app updates, and large downloads. Upload speed affects video calls, cloud backup, file sharing, livestreaming, and security cameras. Ping is the delay before a response comes back, while jitter is how much that delay changes from moment to moment.

A connection can show high download speed and still feel bad if upload is saturated or jitter is unstable. That is why gaming, video calls, and work-from-home issues often need latency and upload troubleshooting, not only a bigger download plan.

Fixes That Usually Help First

Apply fixes in order, testing after each one. The goal is not to change everything at once; it is to find the smallest change that improves the result.

test the same device in the same place for fair comparisons
pause streaming, cloud backup, game downloads, and VPNs before baseline tests
run one Ethernet test near the router if possible
record download, upload, ping, jitter, device, room, and time of day

If Wi-Fi is the weak point, router placement and band choice are usually higher-impact than changing your internet plan. If Ethernet is also poor across several time windows, then modem, router, line, plan, or ISP-side congestion becomes more likely.

Build a Simple Three-Day Test Log

A three-day log is enough to reveal many patterns. Test once during a quiet time, once during the household's busiest time, and once late at night. Keep the device and location consistent for each comparison.

Your log should include download Mbps, upload Mbps, ping, jitter, device, connection type, room, and what else was happening on the network. Add notes when someone starts a cloud backup, joins a meeting, streams 4K video, downloads a game, or turns on a VPN.

After a few sessions, look for repeatable signals. Wi-Fi-only weakness points to placement, interference, channel choice, or device limitations. Time-of-day drops point to household congestion or ISP congestion. Upload-related latency spikes point to upstream saturation or weak queue management.

When to Change Settings and When to Call the ISP

Change local settings when results improve on Ethernet, worsen in specific rooms, or vary strongly by device. That usually means the home network is the first place to fix. Start with router placement, firmware, cables, overloaded devices, and Wi-Fi band selection.

Contact your ISP when wired tests are consistently poor, every device drops together, or the same issue appears at predictable times even after local traffic is controlled. Send the test log, the wired-vs-Wi-Fi comparison, and the steps you already tried. Clear evidence helps support skip generic scripts and check the line or local node.

Before You Finish Troubleshooting

Do one final controlled retest before deciding the problem is solved. Use the same device, same room, and same connection type you used for the first baseline. If the result improves, keep the change and continue monitoring during your busiest normal usage window. If the result does not improve, undo the change unless it was clearly needed for security or stability. This keeps the troubleshooting path clean, makes future comparisons easier, and gives you better evidence if you need help from router support or your internet provider.

Related Bandrift Guides

FAQ

How do I run an accurate internet speed test?

Use the same device and location, pause heavy traffic, run two or three tests, and compare the middle result instead of only the fastest number.

What does an internet speed test measure?

It estimates available download speed, upload speed, latency, and jitter between your device and a test endpoint at that moment.

Why does my speed test change every time?

Results change because Wi-Fi signal, device load, household traffic, ISP congestion, and server routes all vary during the day.

Next step: run a fresh Bandrift speed test, save the numbers, make one change, and test again from the same device.