The word doing all the work in “why is my internet so slow all of a sudden” is suddenly. Connections don’t gently degrade. They were fine Tuesday and unusable Wednesday, which means something changed — a firmware update pushed overnight, a new neighbor’s router landing on your channel, a cloud backup that kicked off at 9 a.m., a failing cable that finally corroded through. Your job is to find the change, not to buy a faster plan.
Here’s the fastest useful test before anything else. Plug a laptop into the router with an Ethernet cable, close everything except one browser tab, and run a speed test. Write down three numbers: download, upload, and ping. Then run the same test on WiFi from the same spot. If wired is fine and wireless is bad, you have a WiFi problem and you can ignore your ISP entirely. If wired is also bad, the problem is upstream — the modem, the line, or the provider.
That single comparison eliminates about 70% of the possible causes in under five minutes, and it’s the step almost everyone skips.
Start with scope: one device or everybody?
Before you touch a setting, figure out how wide the problem is. Walk around and ask. If one person’s laptop is crawling while four others are streaming fine, the network is healthy and that machine has an issue — a stuck update, a full disk, a bad wireless driver, an old 2.4 GHz-only adapter. If the whole office is complaining at once, stop troubleshooting laptops.
This distinction saves an enormous amount of wasted effort in small offices. We’ve watched a business owner reimage a perfectly good workstation because the shared line was saturated by an unattended Dropbox sync on someone else’s machine.
Reboot in the right order
Power cycling works more often than it deserves to, but sequence matters. Unplug the modem and the router. Wait 30 seconds — not two seconds, the capacitors need to drain. Plug the modem back in first and wait until its lights settle (usually 60–90 seconds). Then power the router. Then reconnect devices.
If a reboot fixes it for a few hours and it comes back, that’s diagnostic information, not a solution. Something is filling up or overheating — a router with a failing power supply, a memory leak in old firmware, or a device flooding the network.
How to actually run a speed test
Most speed test results are garbage because of how they’re collected. A few rules:
- Test wired first, from a machine plugged directly into the router. WiFi adds its own variable and hides the real line speed.
- Close Teams, Zoom, Spotify, and any sync client. A single active Zoom call eats 2–4 Mbps and skews everything.
- Run it three times, a few minutes apart. One bad result is noise.
- Test at the hour the problem happens. A 2 p.m. test tells you nothing about the 9 a.m. slowdown.
- Use two different test sites. If one server is congested you’ll blame your own network.
Compare the wired result to what you’re paying for. Cable and fiber plans should deliver roughly 80–95% of advertised download speed on a wired test. If you pay for 300 Mbps and see 240, that’s normal. If you see 45, call the provider.
Bandwidth is not the same thing as speed
This is the part that confuses people who’ve already “checked their speed” and found nothing wrong. A connection can test at 500 Mbps and still feel broken.
Bandwidth is capacity — how much data can move per second. Latency (ping) is delay — how long a single packet takes to make the round trip. Web browsing, video calls, and cloud apps are far more sensitive to latency and packet loss than to raw capacity. That’s why a 1 Gbps fiber line with 180 ms ping feels worse than a 50 Mbps line at 15 ms.
| Metric | Good | Marginal | Broken |
|---|---|---|---|
| Ping to a nearby server | Under 30 ms | 30–80 ms | Over 100 ms |
| Jitter (VoIP quality) | Under 15 ms | 15–30 ms | Over 30 ms |
| Packet loss | 0% | Under 1% | Over 2% |
| Ping under load (bufferbloat) | Rises under 30 ms | Rises 30–100 ms | Rises 200 ms+ |
Bufferbloat: the invisible killer
Run a ping to 8.8.8.8 in a command prompt (ping 8.8.8.8 -t on Windows, Ctrl+C to stop). Watch the response times while someone uploads a large file or a backup runs. If ping jumps from 20 ms to 300 ms during the transfer, your router is buffering aggressively and every interactive app on the network suffers.
The fix is quality-of-service or “smart queue” settings in the router, usually under Advanced > QoS. Set the bandwidth limits to roughly 85–90% of your measured wired speed. Consumer routers vary wildly in how well they do this; business-class gear handles it properly. If you run VoIP phones, this one setting is often the difference between clear calls and robot voice.
Symptom to cause: a quick reference
| What you’re seeing | Likely cause | How to confirm |
|---|---|---|
| Slow only on WiFi, wired is fine | Channel congestion, weak signal, old adapter | Scan channels; test standing next to the router |
| Fast downloads, choppy video calls | Latency, jitter, or packet loss | Continuous ping test; check jitter |
| Slow every day at the same time | Scheduled backup, sync, or update | Router traffic log; Task Manager > Network per device |
| Slow after the 20th of the month | Data cap throttling | Check usage in the ISP account portal |
| Pages hang then load fast | DNS resolution delay | Switch DNS to 1.1.1.1 and retest |
| One PC slow, others fine | Malware, driver, disk, or update backlog | Task Manager > Performance; full malware scan |
| Everything drops for 10–30 seconds | Failing modem, line noise, overheating router | Modem event log; check for signal errors |
| Slow only over VPN | VPN routing all traffic, distant endpoint | Test with VPN off; compare |
WiFi problems worth fixing
2.4 GHz vs 5 GHz
The 2.4 GHz band reaches further and penetrates walls better, but it’s crowded and slow. It shares space with microwaves, cordless phones, Bluetooth, wireless mice, and every neighbor’s router. In a strip mall or shared office building, 2.4 GHz is usually a lost cause during business hours.
The 5 GHz band has far more non-overlapping channels and much less interference, at the cost of range. For most small offices, keeping work laptops on 5 GHz and leaving 2.4 GHz for printers and IoT devices solves the problem outright.
On Windows, check which band you’re on: Settings > Network & Internet > Wi-Fi > Hardware properties. Look at “Network band.” If it says 2.4 GHz on a modern laptop sitting 15 feet from the access point, something is wrong with band steering.
Channel congestion
On 2.4 GHz only channels 1, 6, and 11 don’t overlap. If your router auto-selected channel 3 and the office next door is on 1 and 6, you’re getting interference from both. Log into the router, find the wireless settings, and manually set 1, 6, or 11 — whichever is least used nearby. A free WiFi analyzer app on an Android phone shows this in seconds.
On 5 GHz, set channel width to 80 MHz if the environment is clean and 40 MHz if it’s dense. Wider isn’t always better in a crowded building.
Where the router actually sits
In a lot of small offices the router lives in a closet, on the floor, behind a metal filing cabinet, next to the breaker panel. Every one of those is a signal problem. Get it up high, central, out in the open, away from metal and away from the microwave in the break room. If the office is larger than about 1,500 square feet or has thick interior walls, one router won’t cover it — you need a second access point wired back to the first, not a wireless extender that halves throughput.
Rule of thumb for office bandwidth: budget roughly 5–8 Mbps per person for normal work with video calls. A 10-person office wants at least 100 Mbps down and — this is the part people miss — at least 20–30 Mbps up. Video calls, cloud backups, and file uploads all live on the upstream side, and cable plans are notoriously stingy there. Asymmetric plans like 300/10 are a common cause of “fast internet that feels slow.”
Something on the network is eating the pipe
The single most common cause of a sudden office-wide slowdown is one machine doing something enormous. Candidates:
- A cloud backup running its initial full sync — that can be hundreds of gigabytes and takes days.
- Windows feature updates downloading to a dozen PCs simultaneously.
- OneDrive or Dropbox re-syncing a large shared folder after someone reorganized it.
- Security camera systems uploading footage offsite during the day.
- Someone streaming 4K video in the break room.
Most routers have a traffic or device list showing per-client usage. Look for the outlier. On an individual Windows PC, open Task Manager with Ctrl+Shift+Esc, click Performance > Ethernet/Wi-Fi, then the App history tab to see cumulative network use by app.
The long-term fix isn’t to yell at people. It’s to schedule backups after hours and set update deferrals so twelve machines aren’t downloading the same 4 GB package at 9 a.m.
DNS: when pages hang before they load
If sites take five seconds to start loading but then finish instantly, and downloads run at full speed once they begin, that’s a name-resolution delay, not a bandwidth problem. ISP DNS servers are frequently slow or half-broken.
Change it at the router so every device benefits. Cloudflare’s 1.1.1.1 and 1.0.0.1, or Google’s 8.8.8.8 and 8.8.4.4, are both fine. To change it on one Windows machine instead: Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties > DNS server assignment > Edit > Manual, turn on IPv4, and enter the addresses.
Afterwards, flush the cache from an admin command prompt with ipconfig /flushdns.
Throttling, caps, and the ISP conversation
If slowness started mid-month and clears on the 1st, you’re hitting a data cap. Many US providers apply a cap around 1.2 TB on residential-tier service and quietly slow you afterward. A small business on a residential plan can hit that easily with cloud backups. Business plans typically have no cap and come with a service-level agreement, which is the real reason to pay for one.
When you do call the provider, bring evidence: wired speed test results with timestamps, ping and packet loss numbers, and modem signal levels. “It’s slow” gets you a script. “Wired throughput is 38 Mbps on a 300 Mbps plan at 2 p.m. daily, upstream signal is out of spec at 52 dBmV” gets you a truck.
Hardware that quietly gave up
Consumer routers have a working life of about three to five years. They don’t die cleanly — they start dropping connections, leaking memory, and needing weekly reboots. If yours needs restarting to stay usable, replace it. For a business running VoIP or hosting anything, that’s overdue.
Also check cables. A crushed or kinked Ethernet cable, or an old Cat5 run stapled through a wall, can negotiate down to 100 Mbps or start dropping packets. On Windows, check the negotiated link speed under Settings > Network & Internet > Ethernet. If a gigabit port reports 100 Mbps, swap the cable before doing anything else.
Don’t rule out malware
A single compromised machine can saturate an office connection sending spam or acting as part of a botnet. Signs: constant network activity when nobody’s using the computer, browser redirects, unfamiliar processes with high network use, or a sudden spike in outbound traffic in the router log.
Run a full scan with Microsoft Defender (Windows Security > Virus & threat protection > Scan options > Full scan) plus a second-opinion scanner. On a business network, if one machine is confirmed infected, assume the others need checking too.
Common questions
Why did my WiFi get slow overnight with no changes on my end?
Usually because something changed on someone else’s end. A neighboring business installed a new router that grabbed your channel, your ISP pushed a firmware update to your modem, or a device on your network began an automatic sync. Interference in a shared building is the most common answer, and it’s why the same office can be perfect on Monday and unusable on Tuesday. Check your wireless channel first.
How much internet speed does a 10-person office actually need?
Around 100–200 Mbps down is plenty for typical office work, including everyone on video calls. Upload matters more than most people expect — aim for 20 Mbps or better. If you’re moving large files, running server backups offsite, or doing video production, scale up. Beyond about 300 Mbps, more bandwidth rarely improves the day-to-day experience; latency and WiFi quality do.
My speed test looks great but everything still feels slow. What now?
Look at latency and packet loss instead of throughput. Run a continuous ping and watch what happens when the network is busy. If response times balloon under load, that’s bufferbloat and QoS settings will help. If you see dropped packets, suspect a cable, a failing modem, or wireless interference. Fast-but-unstable is a very different problem from slow.
Should I use a WiFi extender to cover the whole office?
Generally no. A traditional extender repeats traffic over the same radio, which roughly halves throughput for everything connected to it and adds latency. For an office, run an Ethernet cable to a second access point, or use a mesh system that supports a wired backhaul. It costs a little more up front and eliminates a whole category of complaints.
Is it worth paying for a business internet plan?
If your business stops working when the connection does, yes. Business plans typically include no data cap, higher upload speeds, a service-level agreement with defined repair windows, static IP options, and support that doesn’t start by asking you to unplug the router. For a company relying on VoIP phones or cloud software all day, the difference in response time when something breaks is usually worth the premium on its own.