Office Wi-Fi Slow at Peak Hours: What Runs Out, and Four Tests You Can Run Yourself

Office Wi-Fi slow at peak hours is almost never a problem with your internet package. The symptom says so on its own: everything is fine at seven in the morning, video calls start breaking up around eleven, and by two in the afternoon an ordinary web page takes its time. Your subscription did not change between those hours. What changed is how many devices are competing for a turn to speak on the air. The four tests below find the cause in about an hour, with no paid tools and nobody called out.

Office Wi-Fi slow at peak hours: what actually runs out

Think of one access point as a single conversation in a room, not a bundle of parallel pipes. Inside that access point only one device may transmit at a time. Everything else waits its turn. Those turns are measured in thousandths of a second, so with ten devices nobody notices anything.

What runs out first is not bandwidth but airtime — the share of talking time on the air. An old phone at the far end of the room, showing two bars, transmits slowly, and for as long as it is transmitting everything else waits. So one weak device can hold up the entire room. It is also why a full signal icon on your laptop guarantees nothing at all.

A case we see often: a distributor in Sidoarjo with 28 staff, one ISP-supplied router by the front door, no additional access points. The device count is not 28. Everyone carries a phone, several have tablets, and there are two wireless printers plus a CCTV camera riding along. Eighty devices, one radio.

Sorting out the IT infrastructure in an office is a one-off job. The diagnosis is not, and it does not have to wait for a vendor visit.

Four tests to run at the busy hour

Run all of them between ten and two, when the office is genuinely full. A test at seven in the morning tells you nothing about this particular problem.

1. Cable versus Wi-Fi. Take one laptop off Wi-Fi, plug a LAN cable straight into the router or switch, and run a speedtest. Write the number down. Reconnect to Wi-Fi at the same desk and repeat it. If the cable result is close to your subscription but the Wi-Fi result sits well below it, the problem is on the wireless side. If both are low, the problem is the ISP uplink.
2. Count the devices actually connected. Open the router admin page — usually 192.168.1.1 or 192.168.0.1 — and find the DHCP client list. The number is nearly always far higher than the headcount. In our experience, above 25 active devices on a single radio you have found the cause without needing another test.
3. Look at your 2.4 GHz channel, and your neighbours’. On Android, a free WiFi analyzer app lists every network nearby with the channel it sits on. On Windows, run netsh wlan show networks mode=bssid at the Command Prompt; the output carries SSID, BSSID, Channel and Signal. Count how many other networks share the channel you are on.
4. Ping for two minutes. Run ping -t 8.8.8.8 on Windows, or ping 8.8.8.8 on macOS, for two minutes and still at the busy hour. What matters is not the average but the lost packets and the highest spike. Packets going missing, or a jump from tens to hundreds of milliseconds, explains a video call breaking up far better than any speedtest result does.

Reading the results

One note on that table: two rows can be true at the same time. An office in a multi-storey shophouse usually has both — devices piled onto one radio, and a 2.4 GHz channel contested by seven other tenants in the same building. Fix the cheapest one first, measure again, then move on to the next.

The repair order, starting at zero rupiah

The order matters more than the list does. The first three steps cost nothing at all, and in an office under 30 people they are often the whole fix.

1. Set 2.4 GHz to channel 1, 6 or 11 only, at 20 MHz channel width. In the 2.4 GHz band those three are the only channels that genuinely do not overlap — channel 3 or 9 interferes with both sides at once. A 40 MHz width on 2.4 GHz makes things worse rather than better, so leave it at 20 MHz.
2. Give the 5 GHz band its own network name, a "-5G" suffix is enough, and move every laptop onto it. There are far more free channels up there and neighbours rarely use them. The trade-off is real: 5 GHz has shorter range and concrete walls stop it more easily, so phones that walk around are better left on 2.4 GHz.
3. Move backups, cloud storage sync and Windows updates outside working hours. One machine uploading a 40 GB backup at eleven in the morning can take the whole office uplink with it, and no Wi-Fi setting will rescue that.
4. Only then add an access point — not a repeater. A business-grade access point runs Rp1–2.5 million per unit and has to be cabled back to the switch. A repeater or extender is cheaper and needs no cable, but it spends airtime twice on the same data, so capacity drops by roughly half. That fixes coverage, not capacity, and the peak-hour problem is almost always capacity.
5. Upgrade the internet package last. If test one showed the cable already fast, a bigger package changes nothing except the monthly bill.

If the three free steps leave the busy hour still stuttering, the access point count is probably the real shortfall, and that is worked out from a floor plan and the headcount per area rather than from a hardware catalogue. An hour with an IT consultant in Sidoarjo is usually enough to settle how many radios you need before anything gets bought.