A decision guide for slow internet
Start with a comparison that changes one condition. “Slow” might mean a low transfer rate, delayed game actions, call interruptions or a page that takes time to start. Those observations are useful even before you have a speed number.
| What you observe | A useful next check | What it can clarify |
|---|---|---|
| One device is slow | Compare the same task on a second device in the same place and connection. | Whether the difference follows the device or its app. |
| Wi-Fi varies by room | Repeat near the router and in the problem room, using the same device. | Whether to investigate the Wi-Fi part of the path. |
| Several wired and wireless devices are slow | Record quiet tests and compare more than one service. | Evidence for investigating shared equipment, the service or the provider path. |
| It gets worse during transfers | Pause your own transfers, repeat the task, then compare idle and loaded latency separately. | Whether competing traffic and delay under load deserve attention. |
| Only evenings are affected | Repeat the same setup at quiet and busy times over several days. | A repeatable pattern to give support, without assigning blame from the time alone. |
| Only one app or game is affected | Use its own quality indicators, status information and another session. | What a separate browser test cannot tell you about that session. |
| Direct mobile data is slow | Compare another location and time; check provider notices and plan limits. | Whether the symptom changes with mobile conditions. |
The table is InstantSpeedTest’s troubleshooting sequence, based on the technical distinctions in the sources below. It is a suggested way to collect your own evidence, not a report of tests performed on your connection.
Make a fair speed-test comparison
- Write down the device, connection type and approximate time. Note the app or action that feels slow.
- Run the internet speed test when your own large transfers are paused. Record download and upload separately.
- Repeat using the same test and setup. Compare one change, such as another device or location, rather than changing everything at once.
- Keep the normal results and the poor results. Include the actual app’s observations when asking for help.
A browser test measures a particular device, route and moment. A router’s built-in test measures a different part of the path. Results can differ without either being a complete explanation. Our test methods and limitations explain the measurements used by this site.
What a good Mbps result leaves unanswered
File throughput, delay and consistency describe different things. Gaming can be unresponsive even when a download finishes quickly. A video call can also suffer on an application path that differs from the speed-test path. Use in-game indicators or a meeting app’s own quality view when available.
For a file transfer, check the unit: 10 MB/s equals 80 Mbps before transfer overhead. That arithmetic example is not a measured result. A file host, application limit or storage workload can constrain an individual transfer. Use the download-time calculator to work with a rate you have observed.
Common questions
Does this troubleshooter detect my devices or router?
No. It uses only the four answers you choose. It makes no diagnostic network requests and does not read router settings, device details or other apps. Your answers are not included in this tool’s analytics events.
Should I buy a faster plan or a new router?
Collect the device, connection and time comparisons first. A larger speed number will not address every kind of slowdown. Share repeatable observations with the provider or equipment support before deciding what to replace.
Can a browser test prove that the ISP or game server is at fault?
No. A single browser path cannot identify every part of an application’s path. Game or call telemetry, repeated comparisons and provider information add evidence; they still need interpretation.
Can I use this without knowing any speed numbers?
Yes. Choose what you have observed, including the unsure options. Your suggested checks explain which comparison to try next. No speed test starts automatically.
Technical sources and review
Technical guidance checked on 22 October 2026. The branching order is this site’s decision guide; the linked vendors do not endorse this tool.
- Google Nest: troubleshooting slow internet — device, Wi-Fi placement, competing traffic and Ethernet-path considerations.
- Google Nest: interpreting a router speed test — test location, timing and the limits of a snapshot.
- Microsoft: Wi-Fi connection checks — comparing another device and Ethernet before broader changes.
- Apple: network conditions and slow performance — mobile location and congestion comparisons.
- Microsoft Teams: Call health — measurements from an actual meeting.
- EA: connection quality in an actual game — ping, jitter and loss on the game-data-center path.
- Netflix: stable connection and video-quality guidance — service-specific streaming requirements.
For more explanations, see what causes slow internet or browse the internet tools directory.