DIAGNOSTIC TOOLKIT
Wi-Fi Troubleshooter: Diagnose Connection Problems
Browsers cannot read router signal strength reliably. The most useful approach is to compare the same device beside the router, in the problem room and over Ethernet where possible.
How this check works
The troubleshooter starts with scope rather than a speed threshold: does the problem affect every device and room, particular locations or only one device? That first split changes the most useful next test. A widespread problem suggests checking the access connection; a location problem suggests Wi-Fi coverage; a single-device problem suggests local settings or hardware.
The wizard does not scan the router or silently collect network details. It presents a route based on the answer selected and links to a test that can add evidence. No automated decision can see wiring, router lights, account status or radio conditions that the browser does not expose.
Prepare for a useful result
Use one device and one browser for comparisons. Pause cloud backups, game downloads, streaming and large file transfers, then note whether the device is connected by Wi-Fi, Ethernet, mobile data or a VPN. Run the check at least three times instead of choosing a single unusually good or bad result.
Change only one condition at a time. For a Wi-Fi problem, compare beside the router with the affected room. For a suspected broadband fault, add an Ethernet result if practical. Record the time because congestion and provider work can make the same connection behave differently during the day.
What the result can tell you
If Ethernet is healthy but a distant room is poor, the broadband package is unlikely to be the immediate limitation. If all devices fail on both wired and wireless connections, check official provider information and the router state. If only one device fails beside the router, update, reconnect and compare its settings.
Intermittent faults need a record of time and conditions. Note whether the router restarted, lights changed, calls failed, or only one application was affected. That evidence prevents an unrelated hardware purchase from masking the original issue.
Limits of this browser test
A browser sees the complete path from this device to LumaProbe, including the device, local network, provider route and test server. It cannot isolate the broadband line on its own. Browser scheduling, security software, VPNs, extensions and background activity can also influence a short test.
Treat the result as diagnostic evidence, not a contractual line measurement or a live provider-outage declaration. A provider can test a different network boundary and report a different valid number. The most useful conclusion usually comes from controlled comparisons and repeated observations.
What to do next
Follow the linked diagnostic, then make one reversible change and retest. Free changes include moving the router into the open, pausing heavy traffic, reconnecting a device, checking official status and replacing a visibly damaged cable with a known-good one.
Buy equipment only when the comparison identifies a matching limitation. Mesh is for coverage across several rooms, Ethernet is for stable fixed-device links, a switch adds wired ports, and a USB adapter adds Ethernet to a device without a socket. None of these repairs a provider outage.
Read the complete LumaProbe test methodology and privacy notes →