How it works
Slowness has different signatures. Processor load, memory pressure, storage exhaustion, and a weak wireless signal each degrade a device in their own way, and each points somewhere different.
Match the symptom to the resource: everything sluggish at once suggests a system-wide constraint, while one application stalling on files suggests storage or that application alone.
Common error
Do not treat every slow device as a network problem. A machine that struggles equally when disconnected is telling you the network is not the cause.
Worked example
A student reports slow video editing even when the laptop is disconnected. Interpret these readings before changing the network.
Evidence
CPU: 18%
Memory: 97%
Free storage: 22 GB
Offline editing: still slowMemory pressure is the strongest lead among the supplied readings. Close an unnecessary application and repeat the same editing operation while watching memory use. Offline slowness weakens the claim that internet bandwidth is the cause; it does not prove memory is the only issue.
Exercises
1.2.1
A workstation has 98% CPU usage, 40% memory usage, and normal network latency during a slow export. Which resource should you investigate first?
Show solution
Investigate processor load and the process performing the export. Compare export time and CPU load before and after a controlled application change rather than upgrading the internet connection.
1.2.2
A laptop is fast beside the access point but slow across the building, with the same application and workload. What comparison would test a wireless hypothesis?
Show solution
Compare signal quality and transfer performance in both locations, and compare with a wired connection if available. Keep the workload fixed to separate location-dependent wireless effects from application processing.