Mac running slow? Check CPU and memory first
A slow Mac is not always a storage problem. Check whether the machine is actually under load before you delete files, reboot twice, or start changing settings.
If your Mac feels slow, check CPU load and memory pressure first. If those signals are calm, deleting random files will probably not fix the live problem. If one of them is high and stays high, open Activity Monitor and find the process.
This is a triage guide, not a promise that one number explains every slowdown. Wi-Fi, storage, browser state, thermal load, external displays, sync tools, and one bad document can all matter. The point is to stop guessing before you change the wrong thing.
Disclosure: I build teenystat, a Mac menu bar app for CPU usage, memory usage, fan speed, per-core load, and trend checks. It is useful for the first signal. It does not replace Activity Monitor when you need a process name.
Quick answer
| Signal | What it suggests | What to do next |
|---|---|---|
| CPU high and sustained | An app, helper process, browser tab, build, export, or background task is busy. | Open Activity Monitor and sort by CPU. |
| One core repeatedly spikes | A single-threaded task or stuck helper may be the bottleneck. | Watch whether the same action triggers the spike. |
| Memory pressure rises | The Mac may be compressing memory, swapping, or struggling with the current app mix. | Open Activity Monitor's Memory pane. |
| Fan trend climbs with load | The slowdown may be tied to heat or sustained work. | Let the task finish or reduce the workload before troubleshooting deeper. |
| CPU and memory are calm | The issue may be storage, network, app state, a document, or external hardware. | Move to the specific symptom instead of quitting apps blindly. |
01Stop before you delete files
File cleanup is useful when the disk is low. It is a poor first answer when the Mac is slow during a live workload. Deleting installers will not stop a browser helper from using CPU. Emptying Desktop will not lower memory pressure if the open app mix is the problem.
The better first question is: what changed while the Mac felt slow? A video call started. A build kicked off. A browser tab froze. Photos began syncing. An external display woke. A large document opened. That context tells you which signal to check first.
The companion hub, Mac desktop cleanup for files and performance, covers when file clutter, temporary handoff, storage, and system load are separate problems.
02Check CPU load and shape
CPU is the first live signal because many slowdowns are really busy-work problems. Activity Monitor can show the exact process, but you do not always need to start there. A menu bar CPU readout can tell you whether opening Activity Monitor is worth the interruption.
TeenyStat reads CPU load through host_processor_info, computes usage from tick deltas, and shows aggregate CPU plus per-core bars in the popover. Aggregate CPU answers "is the Mac busy?" Per-core shape answers "is the work spread out or stuck on a narrow path?"
Use the per-core view as a clue, not a verdict. If one core jumps whenever you type into one app, export a file, run a script, or load one web page, you have a reproduction path. The deeper guide is checking Mac CPU usage per core.
03Read memory pressure before memory used
A high memory-used number is not automatically bad. macOS uses memory for useful cache. The better question is whether memory pressure is rising and whether swap or compression is involved.
TeenyStat shows used versus total RAM in the menu bar and breaks memory into active, wired, compressed, used, and free values in the popover. That is enough for a quick read. Activity Monitor's Memory pane is better when you need pressure, cached files, swap used, and app-level memory.
If memory pressure is low, do not quit apps just because the used number looks big. If pressure is high during the slowdown, reduce the current app mix and check which apps are holding memory. The deeper explainer is Mac memory pressure vs memory used.
04Use fan trend as a correlation signal
Fan speed does not diagnose a process by itself. It helps you match the slowdown to heat and sustained work. Fan high, CPU high, and a known export running is one story. Fan high while CPU and memory look calm is another.
TeenyStat reads fan count and fan RPM through AppleSMC when a fan is available. On fanless Macs, it avoids leaving the menu bar on a fan value that cannot exist. If fan speed is available, watch the trend alongside CPU and memory instead of treating RPM as a universal normal.
The related fan guide is Mac fan keeps running? Check CPU, memory, and fan speed first.
05Open Activity Monitor when you need names
A menu bar utility should keep you from opening Activity Monitor every time the Mac hiccups. It should not pretend to replace Activity Monitor. When CPU or memory is sustained, you need process names, columns, and the ability to inspect or quit a process.
Open Activity Monitor when the first signal stays high, when one interaction reliably causes a spike, when memory pressure rises into yellow or red, or when the Mac stays slow after the obvious workload ends.
The workflow is simple: menu bar for the first signal, Activity Monitor for the process name, deeper app-specific debugging only after you can reproduce the slowdown.
06Clean storage when storage is actually involved
Storage cleanup has its place. Apple's storage guidance tells you to check storage in System Settings, review categories, move or delete large files, clean Downloads, remove old backups, uninstall unused apps, and empty Trash after files are really ready to go.
Use that path when the startup disk is almost full, updates cannot install, copy operations fail, or storage categories show obvious waste. Do not use it as a substitute for CPU and memory triage when the Mac is slow during a specific task.
If the slowdown is partly a file-workflow problem, a file shelf can keep temporary files out of Desktop while you decide where they belong. The companion TeenyShelf guide is clean up Mac desktop clutter with a temporary shelf.
A practical slow-Mac pass
- Notice what was happening when the slowdown started.
- Check CPU for 30 to 60 seconds without changing anything.
- Check memory pressure and swap if the Mac feels stuck or apps pause.
- Watch fan trend if the Mac is hot or loud.
- Open Activity Monitor only when CPU or memory stays high.
- Clean storage only if disk space is low or file operations are blocked.
- Change one thing, then repeat the same workload.
FAQ
What should I check first when my Mac is slow?
Check CPU load, memory pressure, and whether the slowdown matches a known workload. If the signal stays high, open Activity Monitor to find the process.
Does high memory used mean my Mac is slow?
Not by itself. macOS uses memory for cache. Memory pressure, swap, compression, and app behavior are better diagnostic clues than memory used alone.
Can TeenyStat tell me which app is slowing down my Mac?
No. TeenyStat shows CPU usage, memory usage, fan speed, and trends. Use it for triage, then use Activity Monitor when you need the exact app or process.
Sources checked
- TeenyStat feature claims were checked against the TeenyStat homepage and local Swift source for CPU reading through
host_processor_info, memory reading throughhost_statistics64, AppleSMC fan readings, per-core charts, sparklines, thresholds, alerts, and fanless-Mac behavior. - Apple Support: View CPU activity in Activity Monitor on Mac.
- Apple Support: View memory usage in Activity Monitor on Mac.
- Apple Support: Free up storage space on Mac.
Keep the first performance signal visible.
teenystat is a lightweight Mac menu bar app for CPU usage, memory usage, fan speed, per-core load, thresholds, and alerts.