Slow Internet in the Office: Step-by-Step Troubleshooting

Short answer: work from the ISP to the employee

"The internet is slow" is a symptom, not a diagnosis. The cause almost always sits in one of five places: the ISP line, the router, Wi-Fi, local cabling and switches, or a specific device. Troubleshooting means ruling out each link of the chain in turn, not changing everything at once.

The key rule: compare measurements under the same conditions — same device, same speed test service, repeated at different times of day.

Step 1. Separate Wi-Fi from the ISP

Connect a laptop by cable directly to the router and run several speed and latency (ping) tests.

• Fast on cable, slow on Wi-Fi — the problem is inside the office, most likely the wireless network.
• Slow on cable too — the problem is the router or the ISP.

If you can, plug in by cable to the ISP's equipment, bypassing your own router. That settles whose responsibility it is.

Step 2. Check Wi-Fi

Typical causes of slow wireless:

• Weak signal: walls, floors, distance. Speed drops long before the connection is lost.
• Crowded 2.4 GHz band: neighbouring networks and devices interfere. Move laptops and phones to 5 GHz.
• One access point for the whole office: with many clients it cannot keep up. You need more access points or a mesh system.
• Old devices: one slow client can drag down others on the same access point.

Step 3. Find the bandwidth hogs

Often the line is simply saturated. Usual suspects: cloud file sync, backups, OS updates, video calls, streaming, torrents.

How to find them:

1. Open per-device traffic statistics in the router interface (if available).
2. Check whether the slowdowns line up with backups or updates.
3. On a suspect computer, look at network activity in Task Manager or Resource Monitor.

The fix is QoS (priority for calls and work services), rate limits for background jobs and moving heavy tasks outside working hours.

Step 4. Check router load

A home router serving dozens of office devices is a frequent culprit. Signs of overload: high CPU usage in the interface, freezes, a reboot that helps only for a while, a limit on simultaneous connections.

What to do:

• update the firmware;
• check whether heavy features (deep packet inspection, a VPN server) are running on a weak device;
• if the router cannot cope, replace it with a small-business model.

Step 5. DNS and cables

DNS. If sites take a long time to "think" before opening but downloads are then fast, DNS may be the issue. Set a different public DNS server on one computer and compare.

Cables and ports. Check the link speed in the network adapter status. If it shows 100 Mbps instead of 1 Gbps, the cable, connector or switch port is at fault. A damaged or hand-crimped patch cord is a common and invisible cause.

Step 6. What to tell the ISP

If the problem is confirmed on a cable that bypasses your router, call the ISP with facts:

This gets a technician out faster than "everything is slow".

Common mistakes

• Testing only over Wi-Fi and blaming the ISP straight away.
• Replacing the router without checking cables and load.
• Rebooting and calling the problem solved — it will come back.
• Not writing down test results.