Troubleshooting: How to Check Internet Speed and Connection Quality

Unstable internet isn't always about "low speed." Frozen Zoom calls, lag in online gaming, or pixelated security camera feeds are often caused by connection quality rather than bandwidth. Think of it this way: even if you have a wide pipe, you won't get enough water if the pipe is full of holes.

In this guide, we will walk through a basic diagnostic methodology: from simple speed tests to stability checks using the command line.

Part 1. Checking Bandwidth (Speed Test)

Speed measures how much data can pass through your connection per second.

Preparing for the Test

To get accurate numbers, eliminate internal factors:

1. Use a Wired Connection. If possible, plug directly into the router via Ethernet. Wi-Fi introduces variables like walls and interference.
2. Clear the Channel. Close torrents, system updates, and streaming services.
3. Turn off VPNs. A VPN always "throttles" your results because your data has to travel through an intermediate server.

Running the Test

Use industry-standard services: Speedtest.net or Fast.com.

What the numbers mean:

• Download: How fast you receive data (websites, movies).
• Upload: How fast you send data (your video in a call).
• Ping (Latency): The server's response time. The lower, the better.

The Verdict: If your wired speed is significantly lower than your ISP plan, the issue is likely on the provider's end. If only your Wi-Fi is slow, you need to optimize your local network.

Part 2. Diagnosing Connection Quality (PowerShell)

If your speed looks fine but the internet feels "choppy," you need to check stability. We will use PowerShell (Press Win + X and select Windows PowerShell).

Step 1. Checking the "Last Mile" (To the Router)

Let's see if your router or local cabling is the culprit. Find your router's address:

Type ipconfig and look for the Default Gateway (usually 192.168.1.1 or 192.168.0.1).

Run a connectivity check:

Test-Connection 192.168.1.1 -Count 50

How to interpret the results:

• Loss > 0%: This is "noise" inside your home. If you're on Wi-Fi, the channel is likely congested (switch to 5GHz/6GHz). If you're on a wire, check the physical connectors.
• High Ping (Normal is 1-3ms): If latency to your own router exceeds 20-50ms, your router's CPU is likely overloaded or the device is freezing.

Step 2. Checking the Outside World

If the connection to the router is clean, check the link to a major backbone server (like Google):

Test-Connection 8.8.8.8 -Count 50

• Packet loss to 8.8.8.8 while the link to the router is stable is a clear sign of an issue with your Internet Service Provider (ISP). It's time to call support.

Part 3. DNS and Performance Under Load (Bufferbloat)

Checking DNS (Why websites "hesitate")

If your ISP's DNS server is slow, your computer takes too long to find a website's IP address. Type:

nslookup google.com

If the response takes longer than a second, switch your DNS in the router settings to public servers:

• Google DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare: 1.1.1.1 and 1.0.0.1

Stress Testing (Bufferbloat)

Start a heavy 4K video and simultaneously run a continuous ping in PowerShell:

ping 8.8.8.8 -t

If your ping jumps from 20ms to 300+ms while the video is loading, you have Bufferbloat. Your router can't handle the packet queue efficiently.

A Note on Hardware

To solve queueing issues, Prosumer/SMB grade systems are very popular in the US:

• UniFi or TP-Link Omada: These allow you to fine-tune traffic priorities.
• Aruba Instant On: Offers enterprise-grade stability with a "set it and forget it" cloud setup.

These devices feature QoS (Quality of Service). This feature prioritizes critical traffic (calls and gaming) over heavy downloads. Budget routers often lack the processing power for this, making an upgrade the only real fix.

Troubleshooting Cheat Sheet

Summary

Internet troubleshooting is a process of elimination. If you see packet loss at the first step (to the router), complaining to your ISP won't help. Understanding these basics will save you time and money when dealing with technical support.