How to diagnose a slow internet connection (free tools)

Your internet feels slow. But is it actually slow — or does it just feel that way? Is the problem your connection, your router, your ISP, or the website you're visiting? Most people restart the router, shrug, and move on. But with the right approach and a few free tools, you can pinpoint exactly what's wrong in under 10 minutes.

This guide walks you through a systematic diagnosis — from measuring actual speed to tracing the exact hop where your connection is losing time.

---

Step 1: Measure your actual speed

Before anything else, get a baseline. Your ISP promises a certain speed — let's see if they're delivering it.

Use the internet speed test on netvizor.app to measure your current download speed, upload speed, and ping. Run the test at least three times — once right now, once during peak hours (evenings), and once at an off-peak time (early morning).

What to look for:

• Download speed significantly below what your plan promises → ISP issue or line degradation
• Upload speed much lower than download → asymmetric connection (normal for most home plans) or upstream congestion
• Speed varies wildly between tests → congestion or unstable connection

Before the test:

• Connect via Ethernet, not WiFi — this isolates the connection itself from wireless variables
• Close all other apps, pause downloads, stop streaming on other devices
• If possible, test from multiple devices

If speed is consistently 50%+ below your plan speed during off-peak hours, that's a clear ISP issue worth contacting them about.

---

Step 2: Check your ping and jitter

Speed is only half the story. You can have 500 Mbps download and still feel lag if your ping is unstable. This is especially true for gaming, video calls, and real-time applications.

Run a ping test on netvizor.app to a nearby server and note:

Ping (latency): Time for a data packet to travel to a server and back.

• Under 20ms — excellent
• 20–50ms — good
• 50–100ms — acceptable
• Over 100ms — noticeably sluggish for interactive use

Jitter: Variation in ping between packets. A connection that goes 20ms → 80ms → 30ms → 150ms feels much worse than a stable 50ms. Jitter is the hidden cause of choppy video calls and stuttering games even when "speed is fine."

Run a continuous ping from your command line alongside the online test to see jitter in action:

# Windows
ping -t 8.8.8.8

# macOS / Linux
ping 8.8.8.8

Watch for "Request timed out" lines — that's packet loss. Even 1% packet loss causes noticeable problems.

---

Step 3: Run a traceroute to find the bottleneck

This is where diagnosis gets interesting. A traceroute shows every single stop your data makes on its journey from your computer to a destination — and how long each hop takes.

Run a traceroute on netvizor.app to a site you're having trouble with (Google, YouTube, or whatever is slow).

How to read the results:

Hop  Host                    Avg Latency
1    192.168.1.1             2ms       ← Your router
2    10.0.0.1                8ms       ← ISP local node
3    172.16.5.1              12ms      ← ISP backbone
4    142.250.180.1           14ms      ← Google
5    google.com              15ms      ← Destination

What the hops tell you:

Hop 1 is your router. If this is already 20ms+, the problem is inside your house — router overheating, bad Ethernet cable, or a device hogging bandwidth.

Hops 2-3 are your ISP. If latency jumps significantly here, the problem is between you and your ISP's infrastructure — congestion, degraded line, or a faulty node. This is worth reporting to your ISP with the traceroute as evidence.

Later hops are the internet backbone. High latency here is normal for geographically distant servers. A server in Singapore will always be 150ms+ from Europe — that's physics, not a problem.

*A hop that shows * * : This just means that router doesn't respond to traceroute probes — it doesn't mean traffic is lost there. Only worry if latency stays high after that hop.

---

Step 4: Check DNS resolution speed

This one surprises most people. Every time you visit a website, your device first asks a DNS server "what's the IP address for google.com?" If your DNS server is slow or overloaded, every single page load starts with a delay — even if your actual internet speed is fine.

Check your DNS with the DNS lookup tool on netvizor.app — if resolution takes over 100ms consistently, consider switching DNS servers.

You can also test DNS speed from the command line:

# Windows
nslookup google.com 1.1.1.1    # Test Cloudflare DNS
nslookup google.com 8.8.8.8    # Test Google DNS
nslookup google.com            # Test your current DNS

# macOS / Linux
dig google.com @1.1.1.1
dig google.com @8.8.8.8
dig google.com

Compare the response times. If your ISP's DNS is significantly slower than 1.1.1.1 or 8.8.8.8, switch your DNS:

How to change DNS on Windows: Settings → Network → Change adapter options → Properties → IPv4 → Use the following DNS server addresses → 1.1.1.1 / 8.8.8.8

How to change DNS on router (affects all devices): Login to your router admin panel (usually 192.168.1.1) → DHCP settings → Primary DNS → 1.1.1.1, Secondary DNS → 8.8.8.8

---

Step 5: Isolate WiFi vs the actual connection

WiFi and your internet connection are two completely different things. A problem with WiFi doesn't mean slow internet — and fast WiFi doesn't guarantee fast internet. You need to separate them.

The definitive test: Connect your computer directly to the router with an Ethernet cable and run the speed test again.

Result	Meaning
Speed improves dramatically on Ethernet	WiFi is the problem — interference, distance, router placement
Speed is the same (still slow) on Ethernet	The connection itself is slow — ISP issue or modem problem
Speed is fine but ping is unstable	WiFi jitter — switch to 5GHz or use Ethernet

Common WiFi problems that cause "slow internet":

2.4GHz congestion: Every router in your building probably uses channels 1, 6, or 11. Switch to 5GHz which has far less interference and much higher throughput — it just has shorter range.

Router placement: WiFi signal degrades dramatically through walls, floors, and large appliances. A router in a closet or behind a TV is a common cause of "random" slowness.

Too many devices: 20+ devices on a consumer router causes CPU strain. The router's processor can't handle all the NAT translations fast enough.

Old router: WiFi 4 (802.11n) routers are genuinely slow by modern standards. If your router is from before 2018, upgrading to WiFi 5 or WiFi 6 is often the single biggest speed improvement you can make.

---

Step 6: Check for bandwidth hogs on your network

Slow internet sometimes has nothing to do with your ISP or router — another device on your network is consuming all the bandwidth.

Common culprits:

• Windows Update downloading gigabytes in the background
• Cloud backup (Dropbox, OneDrive, Google Drive) syncing large files
• Torrent client running forgotten in the background
• Gaming console downloading a game update overnight... and still going
• Smart TV updating firmware
• Someone else on your network streaming 4K video

Check which devices are consuming bandwidth from your router admin panel: login to 192.168.1.1 → look for Bandwidth Monitor, Traffic Statistics, or Client List with usage data.

On Windows, you can check per-process network usage:

Task Manager → Performance tab → Open Resource Monitor → Network tab

On macOS:

Activity Monitor → Network tab → sort by "Sent Bytes" or "Rcvd Bytes"

---

Step 7: Test the connection to specific destinations

Sometimes internet feels slow only on certain sites or services — while everything else is fine. This suggests the problem is not your connection but rather that specific destination.

Use the ping test on netvizor.app to compare latency to different destinations:

• A nearby server (low ping = your connection is fine)
• The slow website (high ping = problem at destination or routing to it)

Then run a traceroute specifically to the slow destination to see where the delay builds up. If the problem appears in the last few hops before the destination — it's on their end, not yours.

---

Step 8: Check your IP and connection type

Sometimes the issue is more fundamental — you might be on a connection type that has structural limitations you weren't aware of.

Check your current IP and connection details with My IP on netvizor.app. This shows your ISP name and connection type — useful for confirming you're on the right plan and not accidentally on a throttled connection.

---

The complete diagnostic checklist

Work through this in order — stop when you find the culprit:

• Speed test (Ethernet, not WiFi) → is speed close to what your plan promises?
• Ping test → is latency stable? Any packet loss?
• Traceroute → where does latency spike?
• DNS test → is DNS resolution fast?
• WiFi isolation → does speed improve on Ethernet?
• Bandwidth hog check → is another device consuming all bandwidth?
• Destination-specific → is the problem only with certain sites?
• Router check → when did you last restart it? Is it overheating?
• Modem check → any error lights? When did you last restart it?

---

What to tell your ISP (with proof)

If you've worked through the checklist and the problem is clearly on your ISP's side, document it before calling:

1. Run speed tests at different times of day — screenshot the results
2. Run traceroute and identify the hop where latency spikes (usually hops 2-4)
3. Note the times when slowness occurs — consistent evening slowness is congestion, random slowness is instability
4. Document packet loss from continuous ping test

Armed with specific data — "my speed drops to 12 Mbps between 7-10pm, traceroute shows 200ms+ at hop 3 which is your node at [IP]" — you're far more likely to get a useful response than "my internet is slow."

---

Frequently asked questions

Why is my internet slow only in the evenings? Classic congestion. Your ISP's local node is overloaded by everyone in your area coming home and using internet simultaneously. This is an infrastructure problem on the ISP's side — document it with speed tests at different hours and report it.

Why does my speed test show 200 Mbps but YouTube still buffers? Speed test servers are often optimized and cached nearby — they don't represent real-world performance to specific destinations. Run a traceroute to YouTube's servers specifically to see what's happening on that route.

My ping is fine but video calls are choppy — why? Check jitter, not just average ping. A connection with 30ms average ping but ±50ms jitter will cause choppy audio and video. Run a continuous ping and watch how much the values vary.

Does restarting the router actually help? Yes, genuinely — but not for the reasons most people think. Routers accumulate stale routing tables, overflowing NAT tables, and memory leaks over time. A restart clears all of this. A monthly restart is good practice; daily restarts suggest a problem with the router itself.

---

Summary

Slow internet has a specific cause — it doesn't just "happen." Working through these steps systematically takes less than 10 minutes and gives you a clear answer: is it your WiFi, your router, your ISP, or the destination?

Start with the speed test on netvizor.app, add a ping test to check for jitter, and run a traceroute if the problem persists. These three tools together tell you almost everything you need to know — for free, in your browser, in under 5 minutes.