Guide
Why Is My Internet Slow?
A step-by-step way to diagnose a slow connection: which devices are affected, Wi-Fi vs. Ethernet, time of day, download vs. upload, VPNs, router placement, background traffic, and loaded latency.
Step 1: Is every device affected, or just one?
Before touching your router or calling your ISP, check whether the slowdown is isolated to a single phone, laptop, or streaming box, or whether every device on the network is affected at the same time. If only one device is slow while others stream and download normally, the problem is almost always that device or its Wi-Fi adapter — outdated drivers, a weak antenna, background apps hogging its own bandwidth, or a stale DNS cache — rather than your internet connection itself. If every device is slow at once, the cause is more likely your router, your Wi-Fi network as a whole, or your ISP connection, and the steps below will help narrow it down.
Step 2: Does Ethernet differ from Wi-Fi?
If you can, run the test on the same device over a wired Ethernet connection and then again over Wi-Fi. A small difference between the two is normal. A large gap — for example, 300 Mbps on Ethernet but 40 Mbps on Wi-Fi — points to a Wi-Fi problem, not your ISP plan. That usually means signal strength, interference from neighboring networks or household electronics, or router placement, rather than anything your provider needs to fix. If Ethernet and Wi-Fi are both slow, the bottleneck is more likely upstream of your router. See our Wi-Fi vs. Ethernet guide for more on when the two should and shouldn't match.
Step 3: Does the time of day matter?
Run the test at a few different times — for example, mid-morning and again during evening peak hours. If your speed is consistently good during the day but drops in the evening, that's a strong sign of congestion, either on your ISP's local network as many households in your area come online at once, or from your own household's peak usage as more devices join calls, streams, and downloads simultaneously. This pattern is common and doesn't necessarily mean anything is broken, but it's useful to know when planning bandwidth-heavy activities.
Step 4: Is it download or upload that's slow?
Look at your result separately for download and upload rather than treating them as one number. The two have different causes: slow download can point to congestion, plan limits, or Wi-Fi issues, while slow upload — especially on connections that are otherwise fast — often reflects an asymmetric plan where upload was never provisioned to match download. This matters most for video calls, cloud backups, and live streaming, which lean on upload much more than everyday browsing does. See What Is a Good Internet Speed? for typical download and upload targets by activity.
Step 5: Are you using a VPN?
A VPN routes your traffic through an extra server and encrypts it, which adds latency and can cap your effective throughput well below what your connection is otherwise capable of. If you're not relying on the VPN for privacy or work reasons at that moment, try disabling it and testing again to see how much of the slowdown it accounts for. If the difference is large, that's expected behavior for a VPN and not a fault with your ISP connection — you can weigh the trade-off between the VPN's protection and the speed cost.
Step 6: Router placement and age
If Step 2 pointed to Wi-Fi specifically, router placement and hardware age are the most common causes. Walls, floors, metal appliances, and distance from the router all weaken a Wi-Fi signal, and a router tucked in a closet or behind a TV will perform noticeably worse than one in an open, central location. Older routers also matter: aging hardware and out-of-date firmware can struggle with modern traffic loads and lack newer Wi-Fi standards. A few practical fixes: move the router to a central, elevated, open spot away from other electronics; keep its firmware updated; and if it's several years old, consider whether a replacement or mesh system would help — especially in a larger home.
Step 7: Background traffic on your network
Even a fast connection can feel slow if something else on the network is consuming most of it. Large downloads, cloud photo or file syncs, automatic app and OS updates, and other devices mid-stream or mid-download all compete for the same bandwidth. Before assuming there's a deeper problem, check what else is running — on your own device and on other devices sharing the connection. A useful, more precise way to spot this is to check loaded latency specifically: if ping under load is much higher than idle ping, something is actively saturating your connection. See Ping, Jitter & Loaded Latency Explained for how to read that signal.
Step 8: Loaded latency and bufferbloat as a unifying signal
If none of the steps above turned up an obvious cause, look at loaded latency in your test result. It measures ping while your connection is actively downloading and uploading, rather than sitting idle. A big gap between idle and loaded latency — sometimes called bufferbloat — points to how your router manages traffic queues, not to a lack of raw speed. This is why a connection can show a high headline Mbps number yet still feel laggy during calls or games whenever something else is using the network. If you see a large gap, look for a Quality of Service (QoS) or Smart Queue Management (SQM) setting in your router's admin panel and enable it — this is one of the most effective fixes for a connection that has fine raw speed but poor responsiveness under load.
Put it together
Most slow-internet complaints trace back to one of these eight signals rather than a single mysterious cause. Run the speed test now and walk through each step against your result: which devices are affected, how Wi-Fi compares to Ethernet, whether the time of day lines up, whether download or upload is the weak point, whether a VPN is active, how your router is placed, what else is on the network, and what the gap between idle and loaded latency looks like. Together they cover the large majority of everyday slowdowns. For more background on what the numbers in your result actually mean, see our methodology.