How to Check Wi-Fi Speed Properly in a South African Home

Run a Wi-Fi speed test near the router, use a local server, and repeat it from the problem room at different times. A wired baseline helps South African fibre or LTE users separate line performance, busy-hour congestion and home radio coverage.

Build Lab · 10 Sept 2026 · 6 min read · NetNinja ·

Build a wired baseline before blaming the router

A useful Wi-Fi speed test is a small investigation, not a single number captured while everyone at home is streaming. Testing beside the router, in the room with the complaint and through Ethernet separates radio coverage from the fibre or LTE connection feeding it. Repeating those checks at different South African busy-hour times gives a much clearer picture of what needs attention.

Quick Answer

Pause large downloads, test near the router with a nearby server, then repeat the test from the problem room. Record download, upload and latency rather than focusing on one headline result. A wired test with one device connected is the key comparison: if Ethernet is slow too, the issue may be the incoming service or congestion rather than Wi-Fi coverage.

✅ Make the first test fair

Choose one device that is reasonably current and close unnecessary applications before testing. Background game updates, cloud backups, video calls and another household member's stream can all change the result. If practical, ask others to pause heavy use for a few minutes so the first reading measures the connection rather than a crowded home network.

Stand near the router for the baseline. Use a nearby South African test server where possible, because it shows how the access line behaves before distance to an overseas service becomes part of the story. Note the date, time, selected server, download result, upload result and latency. A screenshot is useful, but a short written record lets you compare several tests without trying to remember which image was which.

Do not treat a single excellent or poor result as the final answer. Repeat the same method in the morning, late afternoon and evening if the complaint appears mainly after work or school. LTE tower load, neighbourhood wireless activity and provider congestion can rise at busy times; fibre users can also see a difference when a household has many devices active.

📶 Compare Wi-Fi with Ethernet

Connect one suitable computer to the router by Ethernet, temporarily disconnect or pause other demanding devices, and run the same kind of test. This is not a promise of the fastest number possible; it is a way to remove walls, distance and wireless interference from the test. If the wired result is healthy while the bedroom Wi-Fi reading is weak, focus on coverage and radio conditions. If both are poor, gather evidence about the line or service before blaming the router.

Pay attention to latency as well as download speed. A connection can report a decent download figure yet feel poor in a call or an online game if latency jumps sharply. For gaming, use the servers you actually reach after the local baseline. A Johannesburg-based result and an overseas game server answer different questions, so label them accordingly.

🧩 Test the room, not only the subscription

Move to the spot where the connection feels unreliable and repeat the exact test. Concrete walls, metal furniture, appliances, neighbouring networks and the placement of the router can change a Wi-Fi signal dramatically. A router tucked into a cupboard or placed low behind a television may have a harder job than the same unit positioned openly and centrally.

An older phone can make a capable network seem slow. Its Wi-Fi generation, antenna design, battery-saving behaviour and background activity may impose the limit. Test with a second device before buying anything. If the problem affects only one handset or laptop, compare its settings and software updates before changing the whole network.

When household coverage is genuinely the limiting factor, look at the layout before choosing equipment. The wireless networking category helps frame the difference between network devices, while wireless router options give a focused place to compare router features. The number of rooms, wall materials, device count and fibre or LTE handoff should guide that comparison.

🛡 Collect evidence before contacting the provider

If Ethernet and Wi-Fi are both slow, make a small record before contacting an ISP. Include the date, time, test server, whether the device was wired or wireless, download, upload, latency and any packet-loss result supplied by the test. One device directly connected is much more useful evidence than a vague report that every room feels slow.

For LTE, record signal conditions and whether the slowdown follows a regular time pattern. For fibre, distinguish a failed Wi-Fi connection from a line that is slow even over Ethernet. The provider can only act on a useful symptom when the tests show what happened, where it happened and whether the home radio link was removed from the comparison.

Frequently Asked Questions

What is the best way to start a Wi-Fi speed test?

Pause large downloads, test close to the router with a nearby server and record download, upload and latency.

Why should I test with Ethernet as well?

Ethernet removes wireless distance and interference, helping show whether the fibre or LTE service is already slow before Wi-Fi is involved.

Which speed-test server should I choose in South Africa?

Use a nearby local server for the access-line baseline, then compare a distant destination when your actual service connects overseas.

Why does my result change during the evening?

Household activity, local radio use, mobile tower load and provider congestion can increase at busy times. Repeated tests reveal whether there is a pattern.

Can an old phone make Wi-Fi look slow?

Yes. Its wireless generation, antenna design and background activity can limit the result below what the router and line can provide.

What evidence should I give my ISP about slow fibre?