Back to Blog
WiFi Solutions8 min read

Home Internet Slow Speeds? A Simple Troubleshooting Guide for Home Internet Issues

Z

Zak

24 May 2026

→ Get in Touch for Free


Few things are more frustrating than sitting down to stream, work, or game, and your internet crawls to a halt. Before you call your provider and spend 45 minutes on hold, there's a lot you can diagnose yourself. And more often than not, the problem has a straightforward cause.

This guide walks you through exactly what to check, step by step, with no technical knowledge required.


Person frustrated at laptop with slow internetPerson frustrated at laptop with slow internet


Step 1: Ask Yourself These Four Questions First

Before touching any settings or running any tests, slow down for a moment. The answers to these four questions will point you in the right direction faster than anything else.


Question 1: Which Application Is Having the Problem?

Is it Netflix? A video call on Teams or Zoom? A game? Your web browser? Or is it everything?

Write down exactly what you were doing when the problem happened. This matters because some applications are far more sensitive to network issues than others. A video call will stutter with even brief packet loss that a simple web browse wouldn't notice.


Question 2: Is It Just One Application or All of Them?

Open a couple of different apps or websites and see if they're all slow, or just the one you were using.

  • If it's just one app, the problem is more likely with that app, its servers, or your device's settings for it. Your internet connection itself may be fine.
  • If everything is slow, the problem is more likely at the network or router level, which is where the rest of this guide focuses.

Question 3: Is It Happening on All Your Devices?

Pick up your phone, tablet, or another laptop and try the same thing.

  • If only one device is affected, the issue is with that specific device. Could be a software problem, a bad network adapter, or the device being too far from the router.
  • If all devices are affected, the problem is almost certainly with your router or your broadband line itself.

This single check can save you hours of troubleshooting.


Question 4: Is It Worse at a Particular Time of Day?

Think back. Does it always happen in the evening? During school hours? Or is it completely random?

  • Evenings (roughly 6pm–10pm), this is known as peak congestion time. Your neighbourhood is sharing the same infrastructure, and when everyone comes home and starts streaming, speeds can drop. This is a problem your ISP needs to address.
  • Random or constant, could be a fault on your line, a failing router, or interference from nearby networks.
  • Always at the same time, check if something in your house is scheduled to run at that time. Automatic backups, system updates, and cloud sync services (like iCloud or Google Drive) can quietly eat your bandwidth in the background.

Step 2: Run a Continuous Ping Test to Check for Drops

Once you've answered those questions, the next thing to check is whether your connection is stable, or whether it's actually dropping in and out. A continuous ping sends a small message to a server every second and tells you how long it takes to get a reply. If the reply never comes back, your connection dropped.

We'll ping 8.8.8.8, a publicly available server run by Google that's designed to be always available and fast to respond. It's the perfect target for this test.


On Windows

  1. Press the Windows key on your keyboard (the one with the Windows logo, bottom left).
  2. Type cmd and press Enter. A black window called the Command Prompt will open.
  3. Type the following exactly and press Enter:
ping 8.8.8.8 -t

The -t at the end tells Windows to keep pinging forever, rather than stopping after four attempts.

You'll see lines appearing every second that look like this:

Reply from 8.8.8.8: bytes=32 time=12ms TTL=118
Reply from 8.8.8.8: bytes=32 time=11ms TTL=118
Reply from 8.8.8.8: bytes=32 time=13ms TTL=118

What to look for:

  • The time= value is the round-trip time in milliseconds (ms). Under 30ms is great for home broadband. Over 100ms consistently will cause noticeable slowness. Over 200ms will make video calls difficult.
  • If you see a line that says Request timed out, your connection dropped at that moment.
  • Leave it running for at least 5–10 minutes (longer is better, especially if your problem only happens at certain times). The more timeouts you see, the more unstable your connection is.

To stop the test, press Ctrl + C.


On Mac

  1. Click the magnifying glass icon in the top-right corner of your screen (this opens Spotlight Search).
  2. Type Terminal and press Enter. A white or dark window will open.
  3. Type the following exactly and press Enter:
ping 8.8.8.8

On Mac, the ping runs continuously by default, no extra flag needed.

You'll see the same kind of output as Windows:

64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=12.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=11.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=13.1 ms

What to look for:

  • Same as Windows, watch the time= values and look for any lines that don't appear or say Request timeout.
  • A gap in the sequence numbers (e.g., jumping from seq=4 to seq=7) means packets were lost during that time.
  • Run it for at least 5–10 minutes.

To stop the test, press Ctrl + C.


What to Do With the Results

  • No timeouts, low and steady ping, your connection is stable. The problem is likely something else (your device, a specific app, or your router's WiFi signal).
  • Occasional timeouts or spikes, your connection is intermittently dropping. This could be a line fault, a failing router, or interference.
  • Frequent timeouts or high ping, your connection has a serious issue that your ISP should be made aware of. Screenshot the results before you call them, it's hard evidence they can't dismiss.

Step 3: Why Online Speed Tests Are Not Reliable (And What to Do Instead)

At this point, many people jump to a speed test website like Speedtest.net or Fast.com. While these tools have their place, they have significant limitations that most people aren't aware of, and they can give you a false picture of what's actually happening on your network.


The Problem With Browser-Based Speed Tests

They only test one path. A browser speed test connects to a single server (usually the geographically closest one) and downloads a file as fast as it can. That tells you the speed to that one server, at that one moment, in that one browser tab. It doesn't tell you how your network performs for real-world traffic.

The browser itself is a bottleneck. Your web browser adds overhead, it has to manage tabs, extensions, JavaScript, and memory. That overhead means the browser can't push your connection to its full capacity, especially on faster connections (above 200Mbps). You might have a 500Mbps line that a browser test shows as 300Mbps, not because your internet is slow, but because the browser can't go faster.

They don't reveal packet loss or jitter. A speed test gives you a number in Mbps. It won't tell you that 2% of your packets are being dropped, which is enough to make video calls stutter and games unplayable. You need different tools for that.

The test server may be congested. If the speed test server itself is busy, your result drops, even if your actual connection is fine.


The More Reliable Way: iperf3

iperf3 is a free, open-source tool used by network engineers to measure true network performance. Unlike a browser test, it runs directly from your device without browser overhead, and it can measure throughput, jitter, and packet loss simultaneously.

You can download iperf3 here: https://iperf.fr/iperf-download.php

Downloads are available for Windows, Mac, Linux, and more. The page clearly lists the version for each operating system, download the one that matches yours.

Once installed, iperf3 runs from the same Command Prompt (Windows) or Terminal (Mac) that you used for the ping test. It connects to a public iperf3 server and measures your real throughput, not a browser-filtered approximation of it.

Note: Running iperf3 requires a little more setup than a browser test. If you're not comfortable with command-line tools, the ping test from Step 2 will already give you the most important piece of information, whether your connection is stable or dropping.


Need a Hand Sorting It Out?

If you've worked through the steps above and you're still not sure what's causing the problem, or if your ping results showed packet loss and you don't know what to do next, I'm happy to help.

I offer free 30-minute consultations for home internet issues. We'll look at what you're seeing, talk through the likely cause, and I'll tell you honestly whether it's something you can fix yourself, something your ISP needs to sort, or something that needs a hands-on look.

No jargon. No pressure. Just straightforward advice.

→ Get in Touch, It's Free

Leave a Comment

Need Expert Help with Network Automation?

Let's discuss how we can help transform your network infrastructure

Schedule a Consultation