Slow internet: a useful speed-test diagnosis
Record the actual failure, then compare the same device by cable, near the access point and in the problem room under documented conditions. Keep upload and delay observations alongside download results. Confirm that the original call or transfer works after any change.
- Write down the symptom before opening a test
- Prepare a comparison that isolates one change
- Read download, upload and responsiveness separately
- Compare cable, nearby Wi-Fi and the problem room
- Turn measurements into a useful support record
- Questions about this guide
- Further reading
- Related help
- Terms in this area
- Read next
- Tell us about your own situation.
- Services
- Resources
- Company
- Get in touch
Record the actual failure, then compare the same device by cable, near the access point and in the problem room under documented conditions. Keep upload and delay observations alongside download results. Confirm that the original call or transfer works after any change. A speed test is a useful observation, but it is not a diagnosis on its own. A disappointing download result can come from the wireless connection, the test device, other household traffic, the provider path or the test service. Repeating tests without recording those conditions often produces more numbers without a clearer next step. Use this guide to build a small, controlled comparison for a connection you are authorised to manage. Keep the internet contract and actual equipment details available, protect work sessions from disruption and record what fails in real use. The examples describe how to investigate; they do not set universal speed targets or promise a particular result. Record the actual failure, then compare the same device by cable, near the access point and in the problem room under documented conditions. Keep upload and delay observations alongside download results. Confirm that the original call or transfer works after any change. Write down the symptom before opening a test Start with the task: a call breaks up, a file takes too long to upload, a stream pauses or every website fails. Note whether the problem affects one device, one room, one application or the whole household. Record the time and whether another large transfer was running. Distinguish a page that loads slowly from a device that cannot connect at all. Check the service’s status when only one application is affected, using its official support route. A speed test cannot prove that a particular website is healthy. Write a simple acceptance goal such as completing the normal work call from the desk while other routine household tasks continue. That gives later measurements a purpose. Avoid changing the subscription or replacing a router until there is evidence about which part of the path is limiting that task. Prepare a comparison that isolates one change Use a known device with a current browser or supported test application. Note whether it connects by Ethernet, Wi-Fi or mobile data; make sure the result belongs to the connection you intend to investigate. Keep the same test service and server selection for a comparison where possible, and record both rather than assuming all tools produce identical result
Why are two tests different?
The device, route, server, background traffic and time of day may all differ. Note those conditions and repeat a controlled comparison. A difference is a reason to investigate, not proof that a tool or provider is being dishonest.
Does a strong download result guarantee clear calls?
Not on its own. Upload speed, delay, interruptions, the application and your local connection all matter too. Test the real call in its usual spot and under its normal load, instead of letting the download number stand in for it.
Should I restart or reset the router immediately?
When it is practical, gather the simple evidence first. A supported restart may well be fine, but agree on the interruption and note whether the problem comes back. A factory reset is a different matter, since it can remove essential settings and should follow a documented recovery plan.