There are a few ways to find performance issues. Below is a zero cost method: - Check the routers CPU and Memory usage. - Check the switches CPU and Memory usage - In the router, monitor the connections, arrange the view by in and out throughput. Identify the MAC address or IP using the most bandwidth. - Go to the machine, router, switch, device. Repeat the 2 steps above. If you're on a Windows computer, go to Resource Monitor (not task manager), and check out the Network Tab. This shows you the app using the most bandwidth, and where the traffic is going. Once you identify the culprit, you can set rules in the router and switch to either stop the offending traffic, or separate it from the main network.

1 Finding the root problem does not require different tools if the root problem of the network is identified - diagnosis is very important and critical 2. Using tools related to that main problem

To troubleshoot network performance issues on a tight budget, I’d start by identifying the root cause using free or low-cost diagnostic tools to analyze traffic, bottlenecks, or hardware limitations. Prioritizing fixes with the biggest impact—like optimizing configurations or reallocating bandwidth—ensures resources are used efficiently. Regular monitoring and simple upgrades, such as firmware updates or improved cabling, can also enhance performance without breaking the budget.

When facing network performance issues on a tight budget, here’s how to troubleshoot effectively: Check for Bottlenecks: Start by identifying areas of congestion. Test Hardware: Ensure routers, switches, and cables are functioning well. Optimise Bandwidth Usage: Prioritise critical traffic (e.g., VoIP, cloud applications) and limit non-essential usage during peak times. Update Firmware: Ensure your network devices have the latest firmware updates, as these can improve performance and fix bugs. Evaluate Wi-Fi Interference: If using Wi-Fi, check for interference from other networks and devices.

From my experience, you always start with what you have. Check for the local layer 1 issues first. Once physical issues are ruled out (where applicable) its then time to get into the logs. Beyond that, there are many open source software options for you to use to check for resource utilization, and software issues. I find the biggest issue is generally trying to squeeze the money out to get it fixed.