How to Improve Network Performance — Diagnose First, Then Fix

“The network is slow” is a symptom with a dozen possible causes, and guessing at fixes wastes time. The fastest route to a resolution is to narrow down where the problem is before changing anything.

Step 1 — Establish What “Slow” Means

Three different complaints get described the same way, and they have different causes:

Ask when it started, whether it affects everyone or one person, wired or wireless, and whether it is constant or intermittent. That alone eliminates most of the possibility space.

Step 2 — Work Outward, Layer by Layer

# 1. Is the local network healthy?
ping 192.168.1.1 -n 50        # gateway: expect <1 ms wired, 0% loss

# 2. Is the internet path healthy?
ping 8.8.8.8 -n 50            # expect stable RTT, 0% loss

# 3. Is DNS the problem?
nslookup google.com
nslookup google.com 8.8.8.8   # if this is much faster, your resolver is the issue

# 4. Where does latency appear?
tracert 8.8.8.8               # Windows
mtr 8.8.8.8                   # Linux/macOS — far better, runs continuously

Any packet loss to your own gateway is a fault, and it is local — cable, port, or WiFi. Loss that only appears several hops out is usually rate limiting on an intermediate router and often harmless if the final destination has none.

The Fixes, in Order of How Often They Are the Answer

1. Cabling and physical layer

This is the most common cause of unexplained slowness on a wired network, and the easiest to overlook.

Switch# show interfaces GigabitEthernet0/5 | include duplex|CRC|input errors|late collision

• CRC or input errors climbing — bad cable, bad transceiver, or interference. Replace the cable first; it is free and it is usually the answer.
• Duplex mismatch — one side half, the other full. The link works, slowly, with late collisions. Set both to auto, or both explicitly.
• Negotiated at 100 Mbps on a gigabit port — a damaged pair. 10/100 uses only pins 1, 2, 3 and 6; gigabit needs all eight, so a broken pair silently drops you to 100.

2. WiFi

If the problem is wireless only, wired diagnostics will show nothing.

• Move high-throughput devices to 5 GHz. The 2.4 GHz band has three non-overlapping channels and is congested everywhere.
• Set 2.4 GHz channel width to 20 MHz and pick channel 1, 6 or 11. A 40 MHz channel here interferes with everyone including you.
• Reposition the access point — central, elevated, away from metal, mirrors and the consumer unit. Free, and usually the biggest single improvement.
• Add access points rather than raising power. The client's transmitter is weaker than the AP's, so more power does not fix the return path.
• Check for a sticky client clinging to a distant AP or a failing 5 GHz signal.

3. DNS

Slow DNS feels exactly like a slow network — pages hang before they start loading, then render instantly. If nslookup google.com 8.8.8.8 is much faster than the default, change resolvers on the DHCP server so every client gets the fix.

4. Congestion and QoS

If a link is saturated, everything queues behind whatever is filling it. Look at interface utilisation before assuming a fault:

Switch# show interfaces GigabitEthernet0/1 | include rate

Where a link is genuinely full, QoS reprioritises rather than adding capacity. Mark voice and video as higher priority so they are served ahead of bulk transfers. Without QoS, a single large backup will destroy call quality on the same link.

5. Buffer bloat

An underrated cause of "fast on speed tests, terrible in use". Oversized buffers in routers and modems fill during a large transfer and add hundreds of milliseconds of latency to everything else. The signature is low ping when idle, very high ping during a download.

The fix is a modern queue management algorithm — fq_codel or CAKE — on the router, with the shaper set slightly below your actual line rate so the queue forms where you control it.

6. Broadcast domains that are too large

A few hundred hosts in one broadcast domain means every device processes every broadcast. Segment with VLANs — users, voice, guests, IoT, servers.

7. Spanning tree topology

If the root bridge was never set explicitly, the switch with the lowest MAC address won — frequently the oldest access switch in a cupboard. Traffic then takes an absurd path through it. Set the root explicitly on your core switch.

Switch(config)# spanning-tree vlan 1-100 root primary

8. TCP tuning over long distances

If transfers are fast locally and slow to a distant site, the constraint is likely the bandwidth-delay product rather than the link. Ensure TCP window scaling is enabled, and use parallel streams for bulk transfers.

9. The endpoints themselves

Test with iperf3 memory-to-memory. If iperf3 hits line rate but file copies do not, the bottleneck is disk, antivirus scanning, or the application — not the network.

iperf3 -c 10.10.10.5 -t 30 -P 4

What Does Not Help

• Buying a faster internet plan when the problem is latency, WiFi or loss. More bandwidth does not reduce latency.
• Upgrading Cat5e to Cat8 on a gigabit network. Cat5e carries a full gigabit; the cable was never the limit.
• Raising WiFi transmit power. It unbalances the link and increases interference for your neighbours.
• Enabling jumbo frames on a general LAN. Small gain, confusing failure mode if any device in the path disagrees.
• Rebooting everything without noting what changed. It sometimes works and teaches you nothing, so the problem returns.

Baseline Before You Need It

The hardest performance problems are the ones where nobody knows what normal looks like. Record, while things are healthy:

• Ping times to the gateway, the ISP's first hop, and a public server
• iperf3 throughput between key sites
• Interface utilisation and error counters on uplinks
• WiFi signal strength and channel usage in each area

With a baseline, "slow" becomes a measurable deviation instead of an opinion.

Frequently Asked Questions

Why is my internet slow even though the speed test is fine?

Speed tests measure raw throughput under ideal conditions. They do not show latency under load, jitter, DNS delay or intermittent loss. Buffer bloat in particular produces excellent speed test results and a terrible experience.

Does a better router improve speed?

Only if the router was the bottleneck — usually an old model that cannot route at your line rate, or a weak WiFi radio. It does nothing for an ISP problem or a cabling fault.

How do I know if the problem is WiFi or the internet?

Plug into Ethernet and repeat the test. If the wired connection is fine, the problem is wireless. Also ping your gateway — loss or high latency there is local, not the ISP.

What is buffer bloat?

Oversized buffers filling during heavy transfers, adding large amounts of latency to all other traffic. The tell is low ping when idle and very high ping while downloading. Fix it with fq_codel or CAKE on the router.

Should I use QoS at home?

It helps if several people share a connection and calls or gaming suffer when someone downloads. It cannot create bandwidth, only decide who waits.

How much throughput should a gigabit link give?

Around 940 Mbps. Protocol overhead accounts for the rest, so that figure is healthy, not a fault.