The short version
“The Wi-Fi is slow” is a symptom reported by users, not a diagnosis. In most business sites the access points are the last thing at fault. The cause is usually further back: an internet service that cannot carry the load, a switch or uplink that saturates, cabling that never supported the access point properly, a channel plan competing with the tenancy next door, or a handful of devices using most of the available airtime.
Working through the layers in order costs nothing and prevents the most common outcome, which is buying new hardware that does not fix the complaint.
| Layer | Typical symptom | Quick test |
|---|---|---|
| Internet service | Everything slow, wired and wireless | Speed test from a wired device |
| Gateway or firewall | Slow under load, fine when quiet | Check CPU and session counts at peak |
| Switching and uplinks | One area slow, others fine | Check port utilisation and errors |
| Cabling | One access point underperforms | Test and certify that run |
| Wireless design | Slow in specific rooms | Survey coverage and channel use |
| Devices | One or two users affected | Test a known-good device in the same spot |
Start with a cable, not the Wi-Fi
Before touching anything wireless, plug a laptop directly into the network and repeat the complaint. This single test splits the problem in half.
If the wired connection is also slow, the wireless network is not the fault. Look at the internet service, the gateway and the switching. If the wired connection is fast and consistent while wireless is not, the problem lives in the wireless design, the access point uplinks or the devices themselves.
Do this at the time of day the complaint happens. A network that performs perfectly at 8am and poorly at 11am is telling you about contention and load, not about equipment failure.
Check what the internet service actually delivers
Many sites are still running a service that was sized for a smaller team or a different way of working. Cloud phone systems, video meetings, hosted applications, cloud backups and camera remote access all changed the shape of business traffic.
Look for three things. First, whether the plan’s speed matches the current headcount and workload. Second, whether upload is the constraint rather than download, which is common on services where the two are not symmetrical and matters a great deal for video calls and cloud phones. Third, whether the service is contended at peak times.
If phones and video calls degrade while file downloads still work, that is a quality-of-service and upload problem, not a bandwidth problem. Our guide to business internet failover and redundancy covers how to size and back up the connection properly.
Look at the uplink behind each access point
An access point can only deliver what its cable and switch port allow. A modern access point serving a busy floor sits behind a single cable run, and that run is often the forgotten part of the design.
Common findings include an access point connected through an old or poorly terminated cable, a switch port negotiating at a lower speed than expected, an unmanaged switch daisy-chained under a desk, or several access points sharing one uplink back to the comms room. Any of these will cap the wireless experience regardless of how capable the access point is.
Check switch port speed, errors and utilisation. Errors and re-negotiations point at cabling. Sustained high utilisation points at design. If the cabling itself is suspect, data and fibre cabling work may be the actual fix, and Cat6 vs Cat6A explains where the extra headroom is worth paying for.
Placement and channel planning beat unit count
Wi-Fi is shared airtime. Every device on an access point takes turns, and slower devices take longer turns. That is why one legacy scanner, an old printer or a phone clinging to a distant access point can affect everyone nearby.
The most common design problems are:
- Access points mounted where cabling was convenient rather than where coverage is needed
- Units placed above suspended ceilings, inside comms cupboards or behind metal
- Too many access points on the same channel, competing with each other
- Channel width set too wide for a dense environment, reducing the number of clean channels
- Transmit power set high on every unit, so devices hold onto a distant access point instead of moving to a closer one
- Neighbouring tenancies in the same building using the same channels
In a multi-tenant building the airspace is shared with everyone around you. A site survey shows what is actually in use, not what should be. Where a network has grown without a plan, Wi-Fi and network solutions work usually starts with a survey rather than a hardware order.
Separate the traffic that does not belong together
Guest devices, staff laptops, phones, printers, cameras and payment or booking systems all have different needs. When they share one flat network and one wireless network, a busy guest device can affect a phone call.
Separating traffic with distinct wireless networks and VLANs, then applying sensible limits to guest access, is often the single highest-value change on a small business network. It also makes troubleshooting far easier, because problems can be isolated to one group of devices.
Find the devices using the airtime
A small number of devices frequently account for most of the load. Cloud backups running during business hours, a workstation syncing a large dataset, video streaming on the guest network, or a device stuck retrying a failed connection can all consume disproportionate airtime.
A managed network platform will show which clients are consuming bandwidth and airtime, which access point they are on, and how they are connecting. Without that visibility, troubleshooting becomes guesswork. This is one of the practical arguments for a managed platform, covered in Ubiquiti networks for small and growing businesses.
When it really is the hardware
Sometimes the equipment genuinely is the limit. Signs include access points several generations old, consumer routers acting as the main gateway, unmanaged switches with no visibility, and hardware that no longer receives firmware updates.
At that point the question is not “which access point should we buy” but “what does this site need to support for the next five years”. Office Wi-Fi upgrade planning covers how to scope that properly, including device counts, coverage areas, cabling and switching.
Helpful starting points
If the whole site is slow including wired connections, start with the business internet service. If specific areas are poor, start with Wi-Fi and network solutions and a coverage survey. If the comms room is undocumented and nobody can say what connects where, begin with comms room cleanup and network documentation, because troubleshooting an undocumented network is guesswork.