How to Troubleshoot a Slow Internet Connection: Fing, WiFiman, and Other Network Diagnostic Apps

Start by proving whether the slowdown is inside your home network or coming from your internet provider. Do not reboot everything ten times and guess. Test speed, WiFi signal, latency, device load, and router health in that order. The FCC now uses 100 Mbps download and 20 Mbps upload as its fixed broadband benchmark, which gives you a practical reference point when judging your plan and test results [source: FCC].

TLDR: Run a wired speed test first, then compare it with WiFi results from apps like Fing or WiFiman. If Ethernet shows 280 Mbps but your phone shows 45 Mbps in the bedroom, the problem is likely WiFi coverage, not your provider. In a small home, moving a router from a TV cabinet to an open shelf can improve signal by 20–40% in weak rooms. If both wired and wireless tests are poor, contact your ISP with screenshots, timestamps, and test results.

Step 1: Test the connection, not your patience

Honestly, it feels like most internet troubleshooting starts with bad advice. “Restart the router” may help, but it does not explain anything. You need numbers.

Start with a wired Ethernet test if possible. Plug a laptop directly into the router or modem. Use a trusted tool such as Speedtest, Cloudflare Speed Test, or your ISP’s own test page. Write down:

• Download speed — affects streaming, downloads, and browsing.
• Upload speed — affects video calls, backups, and sending large files.
• Ping — the reaction time of your connection.
• Jitter — how unstable the ping is.
• Packet loss — lost data, often seen as freezes or drops.

If your plan is 500 Mbps and Ethernet gives you 470 Mbps, the ISP line is probably fine. If WiFi gives you 60 Mbps from the same room, your wireless setup is the weak point.

Step 2: Use Fing to find what is on your network

Fing is useful because it shows every device connected to your network. That matters. A slow connection may not be broken. It may just be busy.

Open Fing and scan your network. Look for phones, TVs, game consoles, cameras, laptops, and smart speakers. Then look for devices you do not recognize. A neighbor using your WiFi is rare, but not impossible. A forgotten security camera uploading all day is more common.

Fing can also help you check:

• Unknown devices using your network.
• Router IP address and basic network settings.
• Internet outages and connection drops.
• Device names, which help identify bandwidth-heavy gear.

The annoying part is that device names are sometimes vague. You may see “Generic” or “Unknown vendor.” Expect to waste a few minutes matching MAC addresses to real devices. Still, Fing is one of the quickest ways to spot a crowded network.

Step 3: Use WiFiman to check WiFi signal and channels

WiFiman from Ubiquiti is especially good for WiFi testing. It shows signal strength, nearby networks, and connection details. If you use Ubiquiti hardware, it becomes even more useful, but it still works well as a basic scanner.

Walk through your home with WiFiman open. Test near the router, then in the rooms where the internet feels slow. Watch the signal level and speed changes. A big drop between rooms usually means distance, walls, or interference are hurting the signal.

Pay close attention to these signs:

• Strong signal but slow speed: The network may be crowded or the router may be overloaded.
• Weak signal and slow speed: Move the router or add a mesh node.
• Good download but bad upload: This may affect Zoom, Teams, gaming, and cloud backups.
• High ping near the router: Check the ISP line, modem, or router CPU load.

Step 4: Check for interference and bad router placement

WiFi is picky. A router hidden behind a TV, inside a cabinet, or next to thick brick walls will perform badly. Microwaves, baby monitors, Bluetooth gear, and old cordless phones can also interfere.

Place the router in the open. Raise it off the floor. Keep it away from metal, glass, and large electronics. For many homes, the best place is a central shelf, not the corner where the cable enters the wall.

If you live in an apartment, channel crowding can be brutal. Apps like WiFiman, NetSpot, or AirPort Utility on iPhone can show nearby networks. If ten routers are fighting on the same 2.4 GHz channel, switch more devices to 5 GHz or 6 GHz if your router supports it.

Step 5: Look for latency, not just speed

A speed test can say 300 Mbps and your video call can still be awful. That usually means latency, jitter, or packet loss. Gaming and video calls care about stability more than raw speed.

Use tools like PingPlotter, Cloudflare Speed Test, or a simple ping test. If ping jumps from 20 ms to 300 ms every few seconds, something is wrong. It could be WiFi interference, a saturated upload connection, or trouble outside your home.

One common cause is cloud backup. If a laptop is uploading photos at full speed, everyone else may suffer. Pause backups and test again. If the connection improves at once, set upload limits in the backup app or router.

Step 6: Build a clean report before calling support

Support calls go better when you bring proof. Do not just say “the internet is slow.” Say what you tested and when.

1. Run one Ethernet speed test.
2. Run two WiFi tests in different rooms.
3. Scan devices with Fing.
4. Check signal strength with WiFiman.
5. Take screenshots with time and date.
6. Restart the modem and router once, then test again.

If Ethernet is slow after a reboot, contact your provider. If Ethernet is good but WiFi is poor, fix your router placement, add mesh coverage, or replace old hardware. A router from 2016 may still turn on, but it may not handle modern phones, TVs, cameras, and work laptops well.

Best apps to keep installed

• Fing: Best for finding devices and spotting unknown connections.
• WiFiman: Best for WiFi signal checks and quick wireless testing.
• Speedtest: Good for simple download and upload checks.
• Cloudflare Speed Test: Good for latency, jitter, and packet loss checks.
• NetSpot: Good for deeper WiFi surveys.
• PingPlotter: Good for tracking unstable routes and latency spikes.

A slow connection is not one problem. It is a symptom. Test in the right order, save the results, and make one change at a time. That is how you stop guessing and start fixing the real fault.