Define “slow” and why it happens

“Slow internet connection” can mean different things: low download/upload speed, high latency (delay), frequent buffering, or unstable performance. The cause is often one of three areas: your device or browser/app, your local network (router, Wi‑Fi, cabling), or your internet service (ISP-side congestion, outages, or line issues). Because these causes overlap, the goal is to narrow down where the slowdown originates.

A simple model: test locally first, then network

Start with checks that can be done quickly and that help you separate “local” from “network” problems:

  1. Power-cycle with intent Restart your modem/ONT and router (in that order, if they are separate), then wait a few minutes for the connection to stabilize. Re-test after it comes back up, because some slowdowns are temporary.

  2. Remove variables Test using a different device if possible, and test a different application (for example, a streaming site vs. a file download). Also try a different browser. This helps identify whether the issue is tied to one device or app.

  3. Change how you connect If you use Wi‑Fi, test near the router and compare with a wired connection (Ethernet) if available. A wired test that performs normally often points to Wi‑Fi signal quality, interference, or congestion rather than your internet plan.

Practical checks you can repeat

To get useful answers, measure consistently:

  • Run speed and latency tests at least twice, and note the results.
  • If possible, test at different times of day to see whether it correlates with peak usage.
  • Check whether other people/devices are using bandwidth at the same time (updates, cloud backups, streaming). Sudden slowdowns are frequently explained by concurrent heavy usage.
  • If you see high latency or packet loss (symptoms like “games feel laggy” or “calls keep stuttering”), prioritize local network checks and stability over raw speed alone.

For Wi‑Fi specifically:

  • Look for interference sources (microwaves, thick walls, and many neighboring networks).
  • Ensure the router is placed where the signal can spread (not hidden behind furniture).
  • If your router supports it, consider using a less busy band/channel (without assuming one setting is always better).

Differences and limits: when the cause is unclear

Even with good testing, some situations are hard to pinpoint from the outside:

  • If multiple devices are slow at the same time, and a wired test is also slow, the likely cause is upstream (network/ISP-side) rather than only Wi‑Fi.
  • If only one device or one app is slow, the cause may be device settings, background tasks, DNS issues, or application-specific throttling.
  • If results vary dramatically between tests, the connection may be unstable; in that case, stability checks (how often it buffers, and whether latency spikes) matter more than a single speed number.

A key limitation: without access to line diagnostics or provider logs, you can only infer the cause. Treat your observations as indicators, not proof.

What to do next based on what you find

Use your results to decide your next step:

  • If wired works well but Wi‑Fi does not: focus on Wi‑Fi placement, interference, and device distance.
  • If both wired and Wi‑Fi are slow: gather your test times and results, then contact your ISP or router support with what you observed.
  • If only one device/app is affected: check for updates, background downloads, and whether the app behaves differently on a separate device.

If the issue persists, keep a short log (time, test type, device used, wired vs. Wi‑Fi). This makes support conversations more efficient and helps avoid guesswork.