Why Is My PC So Slow? Diagnose and Speed It Up
My PC is slow — here is how to find out why. Measure memory, CPU and disk pressure, find the files responsible, and check nothing unexpected is running in the background. Works on Windows 10 and 11, Mac and Linux.
10 minutes · uses System Report, Disk Usage, Large Files, Open Ports · Last updated 2026-10-17
Step 1: Take a baseline
Run System Info first. You are looking for two numbers: memory usage above roughly 85%, and any disk with less than 10% free. Those two conditions explain a large share of "my PC is slow" reports on their own — a full C drive or exhausted RAM will make any computer crawl. Note the OS build too — it matters when you search for known issues.
Real output from our test machine (hostname and IPs redacted)=== System Report ===
Computer : LAPTOP-XXXXXXX
OS : Microsoft Windows 11 Pro for Workstations (build 26200, 64-bit)
Uptime : 233.2 h
--- CPU ---
Model : AMD Ryzen 7 7735HS with Radeon Graphics
Cores : 8
--- Memory ---
Total : 13.31 GB
In use : 10.81 GB
Usage : 81.3%
--- Fixed disks ---
C: 474.72 GB total 333.71 GB free 30% used
--- Network (IPv4, excluding loopback) ---
vEthernet (Default Switch) x.x.x.x
Local Area Connection 3 x.x.x.x
Local Area Connection* 10 x.x.x.x
OpenVPN Data Channel Offload for NordVPN x.x.x.x
Local Area Connection* 8 x.x.x.x
x-ovpn-tap x.x.x.x
Wi-Fi x.x.x.x
NordLynx x.x.x.x
Bluetooth Network Connection x.x.x.x
Read-only report - nothing was changed on this machine.
Step 2: Find which folder is eating the disk
If a disk is nearly full, run Disk Usage against your home folder. Full disks make Windows and macOS thrash: updates fail, browsers crash, swap files cannot grow. The top two or three entries are usually the answer.
Step 3: Find the single biggest files
Folder totals tell you where to look; Large Files tells you what to actually delete. A forgotten 8 GB installer, an old game download or a duplicated video backup is often the whole story.
Real output, threshold set to 100 KB on our project folderScanning: C:\Users\you\Documents\Pctools
Threshold: 100KB per file
(read-only: large folders take a while)
Largest files (showing 5):
7.3 MB C:\Users\you\Documents\Pctools\vendor\rampstack-skills\.git\objects\pack\pack-8514f6036a216d2b3f929c526b0aa1e024dc77a3.pack
3.1 MB C:\Users\you\Documents\Pctools\.opencode\node_modules\effect\dist\unstable\httpapi\internal\httpApiScalar.js
3.1 MB C:\Users\you\Documents\Pctools\.opencode\node_modules\effect\src\unstable\httpapi\internal\httpApiScalar.ts
2.5 MB C:\Users\you\Documents\Pctools\vendor\claude-seo\.git\objects\pack\pack-71444a146c0490b26cf6ddd332ae4f3d25cd079e.pack
1.9 MB C:\Users\you\Documents\Pctools\.opencode\node_modules\effect\dist\unstable\httpapi\internal\httpApiSwagger.js
Nothing was deleted or moved. Review each path before you remove anything yourself.
Step 4: Check nothing unexpected is listening
Only if the machine still feels wrong — for example after removing software — run Port Scan against 127.0.0.1. A leftover dev server or an old media service is common; an unfamiliar port on a machine you do not administer is a reason to investigate further.
Real scan of our own test machine, catching the local preview server on port 3000Scanning 127.0.0.1 - 6 ports, 200 ms timeout each
(connect scan only; scan machines you own or are authorised to test)
No open ports found in the scanned list.
Note: a filtered (firewalled) port looks the same as a closed one to this kind of scan.
How to read the results
Numbers only help if you act on them. Use this table to turn a reading into a decision:
| If you see | It usually means | Next step |
|---|---|---|
| Memory above ~85% | Too many programs resident, or a leak | Close background apps; check Task Manager / htop for the top consumer |
| Disk under 10% free | Windows needs headroom for swap and updates | Free 10–15% using the free-disk-space guide |
| One folder dominates | Downloads, a game library, VM images, a backup folder | Move it to another disk or prune it |
| High CPU while idle | Background indexing, updater or malware | Check the process list; run a malware scan if nothing legitimate explains it |
| Unknown listening port | Leftover service or unfamiliar software | Identify the owning process, then close the port or uninstall |
Where this stops working
This workflow diagnoses capacity and resource pressure. It does not detect malware, failing hardware or driver problems. If memory and disk look healthy and the machine is still slow, the cause is usually CPU thermal throttling, a failing disk (check S.M.A.R.T. values) or software that needs a proper profiler — not more cleanup utilities.
Security notes
Three of the four tools here are strictly read-only. Port Scan opens outbound connections and should only ever be pointed at machines you own. If you suspect malware, use a real scanner such as Windows Defender or ClamAV rather than a cleanup tool; do not download "PC cleaner" software from adverts.
Common questions
What should I check first when my PC is slow?
Run System Info and look at two numbers: memory usage above roughly 85%, and any disk with less than 10% free. Those two conditions explain a large share of "my PC is slow" reports on their own. If both look healthy, continue to the CPU and disk checks in this guide.
RAM and disk look fine but the machine is still slow. Why?
Then the cause is usually CPU thermal throttling, a failing disk (check S.M.A.R.T. values), background indexing or an updater, or software that needs a proper profiler. This workflow diagnoses resource pressure only; it does not detect malware or failing hardware. If you suspect malware, use Windows Defender or ClamAV.
Do these scripts fix anything on their own?
No. Three of the four tools are strictly read-only, and the fourth only opens outbound connections for the scan. They measure and report; the fixes in each step are yours to apply by closing the background app, freeing disk space or stopping the service. Nothing changes unless you decide it should.