Why Is My Internet Slow?

"Slow" usually means one of four different things

When someone says their internet is slow, they could be describing any of several distinct problems, and the fix for one does nothing for another. The first useful step is working out which kind of slow you actually have.

Low speed

Download or upload throughput below what you expect — pages take a long time to load, or large files take a long time to transfer.

High idle latency

A slow response time even when the connection is otherwise quiet, which shows up as sluggish page loads or delayed reactions in games, independent of how much data is moving.

Instability

Throughput or response time that varies a lot from moment to moment, so the connection feels fine one minute and poor the next, even though nothing about your setup has changed.

High loaded latency

A big jump in response time specifically while the connection is busy sending or receiving data, so calls and games stutter during downloads or uploads but feel fine when the line is quiet.

These four problems can occur separately or together, and they often have different, non-overlapping causes. A connection with a slow download speed but a good idle latency behaves very differently from one with a fast download speed but severe loaded latency, even though both might get described the same way by a frustrated user: 'my internet is slow'.

Wi-Fi versus the internet connection itself

One of the most common sources of confusion is treating Wi-Fi and 'the internet' as the same thing. They are not. Your internet connection ends at the router; everything from there to your device is a separate, local wireless link with its own capacity, its own range and its own interference problems.

A router positioned behind walls, near a microwave, or shared with many neighbouring wireless networks can bottleneck a connection that is otherwise performing exactly as it should. In that situation, no change to your plan or provider will help, because the plan was never the limiting factor.

The quickest way to separate the two is to test with a cable plugged directly into the router, bypassing Wi-Fi entirely, and compare the result with a wireless test taken moments later on the same device where possible. A large gap between the two points squarely at the wireless link.

Other devices on your network, and the limits of your plan

Home networks are shared. A phone backing up photos, a games console downloading an update, a smart TV streaming in another room and a laptop syncing files can all be quietly using capacity at the same time you run a test, and every one of them takes a share of whatever your connection can deliver.

Separately, every plan has a contracted ceiling. A result close to that ceiling is expected, not a fault. A result well below it, particularly if it happens consistently and at a quiet time of day, is a more meaningful signal — but you can only interpret a number sensibly if you know what your plan actually promises.

Both of these are worth checking early, because they are free, quick and entirely within your control, unlike anything involving your provider's network.

Provider congestion, VPNs, and your device

Sometimes the cause sits further away. Providers share capacity across neighbourhoods and, at peak times such as early evening, that shared capacity can become genuinely constrained. This shows up as a connection that performs well in the morning and noticeably worse after dinner, on the same wiring and the same equipment.

A VPN adds its own encryption and routing overhead, and if its exit server is distant or busy, it can measurably reduce your effective speed and increase latency, independent of anything your provider is doing. Disabling it temporarily is a simple and free way to check whether it is a factor.

Your own device and browser can also be the limiting factor. An older device, a browser with many extensions or tabs consuming resources, or a background update running at the same moment can all reduce the speed a test reports without the underlying connection being at fault at all.

The test-server path and the time you test

A speed test measures the path between your device and a specific test server, not some abstract property of 'the internet'. If that server is distant, congested, or reached over a route that is itself under strain, the result reflects that path rather than your everyday browsing performance, which may use different routes to different destinations entirely.

Time of day matters for a related but separate reason: usage patterns across a whole neighbourhood or region shift throughout the day, and a connection can look completely different at 9am compared with 9pm. Testing only once, and only at one time of day, risks mistaking a temporary condition for a permanent one, or the reverse.

This is exactly why one number from one test is not enough evidence to draw a firm conclusion. A pattern that holds up across several runs, at more than one time of day, with other variables held constant, is what turns a single measurement into something you can actually act on.

A sequence for narrowing it down

Rather than guessing at a single cause, it helps to work through checks in order, starting with what is fastest and cheapest to rule out and only escalating once those are exhausted:

1. Run a reliable Norynt test to get a trustworthy baseline reading.
2. Check the primary issue the result identifies, rather than guessing at a cause.
3. Pause heavy traffic on every device on the network, then test again.
4. Test close to the router to reduce distance and interference on Wi-Fi.
5. Test over Ethernet to remove Wi-Fi from the path entirely.
6. Disable any VPN temporarily and test again.
7. Test at another time of day to check for a congestion pattern.
8. Compare your result with what your subscribed plan actually promises.
9. Contact your provider only after local causes have been narrowed down.

Each step changes one condition at a time. If a result improves noticeably right after a step, that step has identified a real contributor — even if it does not explain the whole picture on its own.