Network problems are notoriously hard to pin down because the fault could sit anywhere between your device, your router, your ISP's line, or the wider internet — and Wi-Fi adds a whole extra layer of radio interference and signal strength variables on top. Free diagnostic software can narrow this down considerably, letting you tell the difference between a genuinely weak Wi-Fi signal, a congested channel, a faulty cable, or a problem outside your home entirely. This guide covers the best free tools for the job and how to use each one.

NetSpot

NetSpot is one of the most useful free tools for diagnosing Wi-Fi coverage and signal strength issues around a home or office.

  • What it does: scans nearby Wi-Fi networks and shows signal strength, channel usage, and (in its visual heatmap mode) lets you map signal strength room by room by walking around with a laptop while it logs readings against a floor plan.
  • How to use it: run a "Discover" scan to see all networks in range, noting your own network's signal strength (measured in dBm — closer to 0 is stronger; below around -70dBm is typically where reliability starts to suffer) and which Wi-Fi channels are heavily used by neighbouring networks.
  • Interpreting results: if your router and several neighbours are all broadcasting on the same or overlapping channels, that's a strong sign of channel congestion, especially on the crowded 2.4GHz band. Switching your router to a quieter channel, or moving devices to the 5GHz band where possible, often resolves this without any hardware changes.

Pro tip: On 2.4GHz, only channels 1, 6, and 11 don't overlap with each other in most regions. If NetSpot shows your router on a different channel with other networks nearby, switching to whichever of 1/6/11 is least used is usually a quick, free fix.

Wireshark

Wireshark is the industry-standard free packet analysis tool, and while it has a steeper learning curve than the other tools here, it's invaluable for genuinely stubborn connectivity problems.

  • What it does: captures and displays every packet travelling across a network interface, letting you see exactly what your device is sending and receiving at a granular level.
  • How to use it for common problems: start a capture on your active network adapter, reproduce the problem (e.g. a webpage failing to load), then stop the capture and filter the results. Filtering for tcp.analysis.retransmission highlights packets that had to be resent — a high volume of these usually points to a poor or congested connection. Filtering for dns shows whether DNS lookups are resolving quickly or timing out, which is a common hidden cause of "slow internet" complaints that aren't actually a bandwidth issue.
  • Who it's for: Wireshark is overkill for simple Wi-Fi signal issues (NetSpot is better suited there) but is the right tool when you need to see exactly what's happening at the packet level — for example diagnosing why a specific application keeps disconnecting, or confirming whether a device is repeatedly trying and failing to reach a particular server.

Windows Network Diagnostics and Command-Line Tools

Windows includes several free, built-in tools that are often the fastest first step before reaching for third-party software.

  • ping: run from Command Prompt (ping 8.8.8.8 to test raw connectivity to Google's DNS servers, or ping google.com to also test DNS resolution). Consistent replies with low, stable latency indicate a healthy connection; timeouts or wildly varying response times point to instability somewhere on the path.
  • tracert: shows the route your traffic takes to reach a destination, hop by hop, which helps isolate whether a slowdown is happening on your home network, at your ISP, or further out on the internet.
  • ipconfig /all: displays your current IP address, DNS servers, and adapter details — useful for confirming your device actually received a valid IP address from the router rather than falling back to a self-assigned APIPA address (typically starting 169.254.x.x), which is a classic sign of a DHCP or router-side problem.
  • Windows Network Troubleshooter (right-click the network icon in the system tray) automates many of these checks and can fix common issues like a stuck adapter automatically, making it a reasonable first click before anything more advanced.

Pro tip: An IP address starting with 169.254 means your device never successfully got an address from the router — that's a strong pointer towards a router, cable, or driver problem rather than anything wrong further out on the internet.

GlassWire

GlassWire is a free (with a paid upgrade tier) network monitoring tool with a strong visual interface, useful for a different kind of diagnostic question: not "is my Wi-Fi weak" but "what is using my network right now."

  • What it does: shows real-time bandwidth usage broken down by application, plus historical graphs of network activity and alerts for new devices joining your network.
  • When it's the right tool: useful for diagnosing a connection that feels slow because something is quietly consuming bandwidth in the background — a stuck cloud sync, an unexpected update download, or an unfamiliar device on the network.

Speedtest by Ookla

The familiar Speedtest website and app remain a legitimate diagnostic starting point, not just a bragging-rights tool.

  • How to use it properly: run a test with the device connected via Ethernet directly to the router first, to establish a baseline free of Wi-Fi variables, then repeat over Wi-Fi from the same spot to see how much the wireless connection itself is costing you in speed.
  • Interpreting results: a large gap between the Ethernet and Wi-Fi results on the same device, in the same location, points squarely at a Wi-Fi issue (signal, interference, or an outdated wireless standard) rather than an ISP problem.

A Sensible Diagnostic Order

  1. Run ipconfig /all to confirm you have a valid IP address.
  2. Run a wired vs Wi-Fi Speedtest comparison to isolate whether the issue is wireless-specific.
  3. If Wi-Fi is the culprit, use NetSpot to check signal strength and channel congestion.
  4. If the problem persists over a wired connection too, use tracert to see where along the route delays are introduced.
  5. For anything still unresolved, Wireshark's packet-level view will usually reveal what's actually going wrong, even if the fix itself needs further research once you know the specific pattern.

Working through diagnostics in this order — from broad, easy checks to more detailed tools — resolves the large majority of home network complaints without ever needing to call an ISP's support line.

Was this guide helpful? Explore more Diagnostic Software guides, or browse all Tools & Buying Guides articles.