Your team says “the internet is slow.” Someone restarts the router, things feel better for an hour, and by the afternoon the complaints are back. Sound familiar?
A restart treats the symptom, not the cause. In Uptime Institute’s 2024 outage analysis, four in five survey respondents said their most recent serious outage could have been prevented with better management, processes, and configuration.
Here are the steps IT professionals follow, what each result means, and when to hand things to an expert.
9 Steps to Troubleshoot Network Performance Issues
Work through these in order, and change only one thing at a time so you know what made the difference.
1. Identify the Network Performance Problem
“The network is slow” is hard to fix. “Video calls drop for sales every morning” is much easier. Answer these first:
- Who is affected? One person, one department, or everyone?
- What is slow? The internet, a specific app, or internal files and printers?
- When does it happen? All day, at certain times, or since a recent change?
- Where does it happen? On Wi-Fi only, wired connections, one area, or for remote users?
| If you notice… | Start by looking at… |
|---|---|
| Only one person is affected | That person’s device |
| Only Wi-Fi users are slow | Wi-Fi coverage and access points |
| Everyone slows down at busy times | Bandwidth and congestion |
| Problems began after a change | Recent configuration updates |
Not sure what could be behind the slowdown? Our overview of common causes of network performance problems can help you narrow it down.
2. Check the Internet Connection and Available Bandwidth
- Connect a computer to your network with a cable, not Wi-Fi.
- Run a speed test at a quiet time, then again during a busy period.
- Compare both results, including upload speed, with your internet plan.
What it tells you: If speeds are low even when the office is quiet, the problem may be your internet provider or connection equipment. If speeds only drop during busy hours, your bandwidth may not match your demand.
3. Inspect Network Hardware and Connected Devices
Check the physical basics before assuming something complex:
- Loose, damaged, or tightly bent network cables
- Warning or error lights on your modem, router, firewall, and switches
- Equipment that runs unusually hot
- If only one computer is slow, pending updates, high CPU usage, or outdated network drivers on that machine
What it tells you: A single faulty cable or overheating switch can cause problems that look much bigger. If one device suddenly starts behaving oddly, it may be a bottleneck, and our guide to finding network bottlenecks shows how to confirm it.
What it tells you: A single faulty cable or overheating switch can cause problems that look much bigger. If one device keeps standing out, it may be a bottleneck, and our guide to finding network bottlenecks shows how to confirm it.
4. Test Network Latency and Packet Loss
Latency (delay) and packet loss (data that never arrives) can make a fast connection feel slow.
- Open Command Prompt on Windows or Terminal on a Mac.
- Run a continuous ping for a minute or two, such as ping -t 8.8.8.8 on Windows or ping 8.8.8.8 on a Mac.
- Run tracert (Windows) or traceroute (Mac) to a slow website or service to see each hop along the way.
What it tells you:
- High or jumpy response times point to latency issues
- “Request timed out” replies suggest packet loss
- If delay starts within the first one or two hops, the issue is likely inside your network. If it starts further out, it may be your internet provider.
5. Troubleshoot Wi-Fi Connectivity and Signal Strength
If wired computers work fine and wireless ones don’t, focus on Wi-Fi:
- Check signal strength at the desks or rooms where people complain
- Note how many devices connect to each access point during busy periods
- Move a laptop closer to the access point and test again
What it tells you: If performance jumps when you move closer, coverage or interference is the likely cause. Fixing it means changing access point placement or channels, best planned with proper Wi-Fi survey tools.
6. Check for Network Congestion
Most business routers and firewalls can show which devices and applications use the most bandwidth. Look for:
- Cloud backups, software updates, or file syncing during work hours
- A single device using far more bandwidth than the rest
- Slowdowns that line up with meetings or daily routines
What it tells you: If one app or device dominates traffic when things slow down, you’ve found a strong lead. Our article on causes of network congestion problems explains why this kind of traffic creates problems.
7. Review Network Configurations
Ask what changed shortly before the problem started:
- New firewall rules or security settings
- New equipment, VLANs, or Wi-Fi networks
- Newly installed business applications
What it tells you: Recent changes are a common source of new problems. Have your IT team review any you find before rolling anything back.
8. Check Network Devices for Firmware and Software Issues
Outdated firmware on network devices can cause slowdowns, crashes, and security gaps.
- Check each device’s admin page for its current firmware version.
- Compare it with the latest version on the manufacturer’s website.
- Review device logs for repeated errors or warnings.
What it tells you: Vendors regularly release updates that fix known performance bugs and security flaws. Updates can briefly take devices offline, so they should be scheduled carefully as part of a layered approach to cybersecurity.
9. Apply the Fix and Verify Network Performance
Once the likely cause is clear, apply one fix at a time and test again:
- Make a single change, such as rescheduling backups or replacing a faulty cable.
- Repeat the same speed, ping, and traceroute tests from earlier.
- Compare the new results with your original ones.
- Ask affected users whether things actually improved, and document the change.
Why it matters: If nothing improves, undo the change and move to the next likely cause.
Why Seek Professional Network Support for Troubleshooting Instead of DIY
These steps help you understand and describe a problem. Fixing deeper issues safely is another matter:
- The right tools: Monitoring platforms and traffic analyzers show what happened before a problem started, not just what you see now.
- Less risk: One wrong firewall or switch setting can take your whole office offline or open a security hole.
- Faster answers: Experience with similar networks means patterns are spotted quickly instead of through trial and error.
A remote and onsite IT support team can take on the deeper diagnostics and fixes, so problems are solved properly the first time.
Conclusion
Troubleshooting a network for performance issues works best as a process of elimination. Define the problem, check your connection and hardware, test latency and packet loss, then look at Wi-Fi, congestion, configurations, and firmware before verifying that your fix actually worked.
If you already have internal IT staff but network issues keep stretching them thin, you can share the workload with a co-managed support team while keeping control of your environment.
FAQs
1. What tools are used to troubleshoot network performance?
Common built-in tools include ping for latency and packet loss, tracert or traceroute for finding where delay starts, ipconfig for checking IP settings, and nslookup for testing DNS. IT teams also use network monitoring platforms and traffic analyzers for deeper visibility.
2. Why does restarting a router fix network problems temporarily?
A restart only clears the device’s memory and resets stuck connections, which can relieve symptoms of software bugs or overload. So, it’s not a permanent fix!
3. How long does network troubleshooting usually take?
It varies. Simple issues like a faulty cable can be found in minutes, while intermittent problems may take days of monitoring to catch in the act.
4. Can network problems be fixed remotely?
Many can. Configuration changes, firmware updates, traffic analysis, and monitoring are often handled remotely. Physical problems, such as damaged cabling, failing hardware, or Wi-Fi coverage gaps, usually need someone on site.