Slow Wi-Fi:
is the problem the internet, the network or the access point?

Wi-Fi is slow. First determine what is actually slow.

The most common diagnosis for poor Wi-Fi is:

“The internet is slow.”

That may be true, but the two are not the same thing.

Between a laptop and the internet there are several separate layers: the wireless connection to the access point, the local network, the router or firewall, the connection to the ISP and only then the wider internet.

If you test everything at once, every problem looks the same.

Run the first test over Ethernet

Connect a computer to the same network using an Ethernet cable and repeat the task that felt slow.

If everything works normally over Ethernet, the ISP connection is probably not the first thing to investigate. The problem is somewhere between the device and the wireless infrastructure.

If it is equally slow over Ethernet, Wi-Fi may not be the cause at all.

Then check:

• internet throughput
• router or firewall load
• DNS
• VPN
• the local server or application you are accessing

This is why a single Speedtest is not enough to diagnose a network problem.

Is it slow for everyone or only one device?

If five computers work normally and one does not, the entire Wi-Fi network is unlikely to be the problem.

On that device, check:

• signal strength
• wireless adapter driver
• whether it is using 2.4 or 5 GHz
• whether a VPN is active
• whether a large download or sync job is running in the background
• whether the same problem appears on another network

If every user in the same part of the office has a problem, the situation becomes more interesting.

At that point, investigate the infrastructure rather than the individual device.

Signal strength is not the same as connection quality

Full Wi-Fi bars do not necessarily mean a good connection.

An area can have a strong signal and still suffer from interference or too many devices competing for the same channel.

A typical example is an office building where every neighbouring company runs its own access points. All of them work, all of them transmit and all of them can see one another.

The result can be a network that shows excellent signal strength while performance varies significantly in practice.

2.4 GHz and 5 GHz do different jobs

2.4 GHz generally reaches further and passes through obstacles more easily, but it is slower and often much more congested.

5 GHz offers more capacity and usually less interference, but the signal does not travel through walls as effectively.

Problems appear when a single access point is expected to cover a space that it cannot realistically serve.

Installing a stronger antenna is often not the answer. The laptop must also be able to transmit a usable signal back.

That is why business Wi-Fi should be designed around the physical space and number of users, not only the coverage figure printed on a product box.

Check roaming

If you have multiple access points, a device should move to the one that offers the better connection.

However, the client device itself plays a major role in deciding when to roam.

A user can therefore walk to the other end of an office while the laptop continues trying to communicate with a distant access point.

The symptom is interesting: Wi-Fi technically works but performs badly, then suddenly improves after Wi-Fi is turned off and back on.

That is a good indication that access point placement, transmit power and roaming behaviour should be examined.

Test the local network, not only the internet

If you have a local server or NAS, transfer a larger file inside the network.

This removes the internet connection from the test completely.

If the local transfer is fast while web access is slow, Wi-Fi may not be the cause.

If local traffic is slow as well, there is much stronger evidence that the wireless or LAN infrastructure should be investigated.

When the problem is not Wi-Fi

Many problems are reported as network problems even when the cause is somewhere else:

• DNS resolution is slow
• a VPN has high latency
• a business application or server is overloaded
• a database responds slowly
• a network share has a problem
• firewall inspection is delaying traffic

The user experience is the same:

“I click and wait.”

That is why the order of diagnosis matters more than immediately replacing equipment.

What you can test yourself

Run four simple tests:

1. The same computer and the same task, once over Wi-Fi and once over Ethernet.
2. A second computer in the same location.
3. The same computer close to the access point.
4. Local traffic to a server or NAS instead of internet traffic.

Those four results usually eliminate a large part of the possible causes immediately.

Do not replace equipment before you know what you are fixing

A new router will not fix poor access point placement.

A faster internet package will not solve a congested Wi-Fi channel.

A new access point will not help if the real delay is an overloaded server or business application.

Separate the problem into layers first.

Only then does it make sense to change equipment or configuration.

Sources and further reading

• Microsoft Learn — Advanced troubleshooting wireless network connectivity Official Windows guidance for diagnosing adapters, signal conditions, channels, roaming, drivers and wireless disconnects.
• Cisco — Wireless RF Reference Guide Technical reference covering RF spectrum, channels, interference and 2.4/5 GHz Wi-Fi behaviour.
• Cisco — Catalyst 9800 Series Configuration Best Practices Official wireless-controller best practices covering RF management, channel utilisation, band selection and client behaviour.