Measure the problem you actually notice
For your own connection or one you are authorised to test. Workplace networks, managed routers and essential connected equipment need their responsible team. If there is no connection at all or it repeatedly disconnects, use the related fault guide rather than treat every interruption as a speed problem.
Step 1 of 8
In this guide
Describe the task and the time pattern
Describe the task and the time pattern
Write down the task, device, connection type, room and approximate time. Is a download taking longer, an upload stalling, a video call responding late, or just one website slow to open? Note whether it started after a change and whether the problem lasts all day or appears during particular activities. Avoid recording private meeting details or customer content.
Download and upload rates describe data transferred over time, commonly shown in Mbps. Latency describes delay; a test’s ping is usually a round-trip measurement in milliseconds. A large download number does not prove a call will respond promptly. Cloudflare explains the difference between bandwidth, throughput and latency. Test results describe a particular path and moment, not every app.
If the internet is entirely unavailable, start with internet-not-working checks. For repeated disconnections, record the pattern using the dropout guide. If ordinary online tasks are working normally again, stop; there is no need to change settings just to chase a higher headline result.
Keep the actual task, timing and affected scope. A description or a single speed figure is useful evidence, not a diagnosis or completed repair.
Compare the affected task and device
Compare the affected task and device
On the affected device, try another familiar public website or ordinary online task that does not expose private data. Check the affected service’s legitimate status page if available. If only that service fails while other tasks behave normally, keep its error and timing and use its support route before changing the whole network. Do not clear valuable browser sessions, reinstall apps or delete local files as a first comparison.
If possible, try a comparable task on another supported device in the same location and on the same intended network. Confirm a phone is not silently using mobile data or a fallback connection, without interrupting essential connectivity to force the test. Different devices and apps have different capabilities, so a faster phone does not by itself identify a faulty component in the computer.
If local apps and documents are sluggish too, look at the computer performance checks. If only an authorised work app or VPN path is affected, record that distinction for its IT team and keep required security in place. If several unrelated tasks and devices are slow, continue with shared activity and connection comparisons. Stop once the actual normal task works; otherwise retain the narrower result.
Keep app, device and network comparisons separate. One faster comparison device narrows the enquiry but does not prove the original device needs replacement.
More checks5 detailed checks
Compare Wi-Fi location and a supported wired path
Compare Wi-Fi location and a supported wired path
If practical, use the same device and task near the router or intended access point, then in the affected room. Keep the device on a firm, ventilated surface and avoid a trip hazard. Better nearby performance suggests the local wireless path deserves attention; it does not automatically mean an extender or faster plan is the answer. Walls, interference, the device and the path between mesh units can all matter.
For a wired comparison, use a supported computer/adapter and a known suitable Ethernet cable connected to an authorised router LAN port. Microsoft’s Ethernet guidance distinguishes that port from the Internet/WAN connection. Follow exact equipment labels and instructions. Do not move the incoming service lead, connect directly to unfamiliar NBN equipment or alter building cabling. Skip this test if the correct path is unclear.
Confirm the test uses the intended connection; do not assume plugging in a cable makes an app choose it. Have the responsible person help where checking that would interrupt managed or essential access. Use comparable times and activity, and restore the normal connection afterwards. NBN’s wired and wireless explanation provides context, but a slow wired test can still include adapter, cable, device, router and external limitations. If room or path differences persist, retain them for targeted help rather than reset the network.
Restore normal connections and keep the location/path result. A better wired result suggests local Wi-Fi involvement; a slow wired result alone does not prove an ISP fault.
Record download, upload and delay carefully
Record download, upload and delay carefully
Use your provider’s recommended reputable test and instructions where possible. Check that you are testing internet performance, not a tool that audits how quickly a website you own loads. Cloudflare’s test documentation explicitly distinguishes those purposes. You do not need to install a booster, grant remote access or provide account passwords to read a result. Check a test’s privacy information before using it.
Speed tests transfer data and may interfere with live calls or capped mobile/satellite services. Confirm available data and a suitable window first. Record download, upload and latency/ping with their displayed units, date/time, device, room, Wi-Fi or wired path, test service/server if shown and other known activity. If the tool reports loaded latency, jitter or packet loss, preserve the exact labels rather than call them all speed. Do not publish an unredacted result that includes private network or location information.
A small number of comparable checks at an affected and an unaffected time is more useful than continuous tests. Use the same method and record changed conditions; a different server or device can change the result. Do not interpret a Wi-Fi link rate, router marketing number or MB/s file-transfer figure as an equivalent internet Mbps result. Stop testing if it disrupts others. If the original task is now normal, stop changes and retain the observations; otherwise compare them with the service’s actual terms and capabilities.

Keep units, test path and conditions with every result. A test to one server is not a universal pass/fail score for every service or a guarantee of future performance.
Compare plan capability and busy-time results
Compare plan capability and busy-time results
Read the current provider plan information for your actual service: download and upload expectations, any typical busy-period information, data allowance or shaping, technology constraints and equipment requirements. Ask the provider to explain anything unclear. The Wi-Fi router’s advertised wireless rate is not the internet plan speed, and a plan headline is not a guarantee that each wireless device will achieve it.
Compare like-for-like results and ordinary use at the times that matter. Several devices slowing together at busy times is useful evidence, but shared activity, local equipment and external congestion can overlap. A particular app can also depend on a remote server or managed route. NBN notes that the home setup and factors beyond it both affect experience; do not assign the fault from one test.
If useful capacity is consistently used up and the local path and devices support the intended service, discuss a suitable plan or equipment change with the provider. Get the expected benefit, compatibility, costs and limitations explained before deciding. Extra download bandwidth will not necessarily resolve delayed responses, a weak wireless path, a slow device or one overloaded website. Do not buy a new router, extender or plan simply because a diagnostic page offers one. Keep the current working configuration until an agreed change and recovery plan exist.
A plan comparison or upgrade recommendation is not an implemented fix. Keep the limits and evidence clear, and seek the responsible provider’s assessment when the expected outcome is uncertain.
Verify normal use and finish
Verify normal use and finish
Resume paused optional work, restore the usual supported connection and try the ordinary task that was slow. Check it in the room and at a representative time where it matters. For a call, use a normal agreed call or app check without exposing someone’s private conversation; for transfers, use non-sensitive content appropriate to your data allowance. Do not disrupt essential services to manufacture a test.
If several people share the connection, confirm the agreed normal activities remain usable together. Keep any remaining device, room or time-specific failure separate. One fast test while everything else is paused does not confirm the household or workplace’s actual needs are met.
If the required use is satisfactory, stop changing settings and retain a short private record. If it remains poor or returns, take the recorded conditions and comparison results to the appropriate provider, app support or IT team. Avoid repeated resets or buying hardware without a diagnosis.
Stop after representative normal use is satisfactory and temporary changes are restored. A single favourable measurement does not prove every device, time or dependency is healthy.
Back to the symptom checkerWhen should you get help with slow internet?
When should you get help with slow internet?
For an apparent service-wide problem, contact your internet provider with affected times, plan, equipment models, ordinary tasks, comparable wired/Wi-Fi results and any known outage reference. Use its legitimate support channel; do not include passwords or configuration exports. Ask what the results establish, what remains uncertain and what test or remedy comes next.
If only one app, managed VPN or workplace network is affected, its responsible team needs the exact error and scope. If local files and applications are slow too, investigate the computer as well. For an unclear local network, devices or room coverage, our internet performance support can help investigate the part you are authorised to manage.
Agree the scope, any interruption, recovery and how normal use will be checked. Keep essential services and protection working. A useful assessment can recommend a more suitable setup or provider enquiry without promising a particular speed, zero lag or a guaranteed result from an upgrade.
Keep the current usable connection, security and private evidence intact while the responsible team investigates. Escalation is a next step, not proof the fault has been fixed.
Book IT support



