First decide what “slow” means
Does a webpage take five seconds to start loading? Does a 4K video pause? Does a large upload creep along? Those symptoms can have different causes. A download result describes how quickly your device receives test data from a particular endpoint. Upload measures sending. Latency measures response delay; jitter describes how much that delay varies. A good result in one column does not guarantee a good experience everywhere.
A six-step isolation test
- Identify the affected activity. Check whether the problem affects all sites or only one stream, app or game. If only one service fails, look for a service-side outage before blaming your provider.
- Measure with no other heavy tasks. Pause large downloads, cloud backups and game updates. Open the NextWatch AI speed test, run a real measurement and record results. Browser tests measure the route to their own servers, not a universal internet speed.
- Move closer to the router. Use the same device and test again in the same room. A large improvement suggests wireless interference, weak signal, wall attenuation or mesh backhaul rather than a whole-line fault.
- Compare with Ethernet where possible. A wired test removes much of the Wi-Fi variable. Use a cable and port fast enough for your plan; a 100 Mbps Ethernet connection cannot reveal gigabit performance.
- Test another device. If one laptop is slow but another is fine in the same place, investigate its Wi-Fi adapter, power-saving settings, browser extensions or background traffic.
- Repeat at different times. Record morning and evening readings for a few days. Consistently slow peak-hour results may indicate congestion, but the pattern alone cannot establish which network is responsible.
What the comparison tells you
| Observed pattern | Likely next check |
|---|---|
| Wi-Fi is slow; Ethernet is much faster | Router placement, band selection, interference, mesh signal and wireless adapter |
| One device is slow; others are normal | Device software, adapter, browser, background apps or malware scan |
| Every device is slow, wired and wireless | Modem status, provider outage, access-line fault or plan limitations |
| Speed tests look good, but one app struggles | Service-side congestion, server location, video bitrate or app settings |
| Download is fine, but calls break up while uploading | Upstream saturation, loaded latency and queue management |
Check the wireless environment
Put the router in an open, central position rather than behind a television or inside a cabinet. Distance, floors, thick walls and nearby networks all affect reception. A 2.4 GHz band often travels farther but shares congested spectrum; 5 GHz generally offers more capacity at shorter range. Your actual result depends on your equipment, location and interference. If you use mesh Wi-Fi, check whether the satellite node itself has a reliable backhaul connection.
A simple test is to compare one device at the same distance before and after changing one setting. Avoid changing channel, band, router location and DNS all at once: you will no longer know which change helped. Restarting the modem once can clear temporary faults, but repeated restarts are not a substitute for diagnosis.
When Mbps is not the problem
A 300 Mbps download result can coexist with high ping or uneven latency. Video calls, multiplayer games and remote desktops often care more about responsiveness than peak throughput. Heavy uploads can fill a queue and delay unrelated traffic, especially on connections with modest upstream speed. If the problem happens during backups, pause them and compare latency while idle and under load. Read our guide to download, upload, ping and jitter for what the numbers mean.
When to contact your provider
Keep a small evidence log: date and time, device, Wi-Fi/Ethernet, speed and latency, outages reported, and any modem error indicators. Share your subscribed plan and the difference between wired and wireless readings. Ask the provider to inspect the line or access network if multiple devices remain slow on a direct wired connection. For satellite links, weather, visibility and obstruction can also influence the path; use the dedicated Starlink diagnostics for context.
What to do next
Run a fresh real browser speed test after each change and compare like with like. If your main symptom is buffering, follow the video buffering checklist rather than repeatedly chasing peak Mbps. The goal is a repeatable diagnosis, not the largest single test number.
Independent methodology: These are general troubleshooting steps, not measurements of your line. For additional provider-specific guidance, see Telstra's internet speed troubleshooting.