Recreate a delay you can see, such as a pause when exporting a file or switching back to a busy browser. Start Activity Monitor and note when the slow action begins and ends. A spike that happens while you are waiting is a more useful clue than one you notice several minutes later.
Let the Mac sit briefly with the same apps open before each run. Note those apps and repeat the slow action at least once. Change only one voluntary workload at a time when you need a comparison.
CPU during work
In the CPU tab, Idle shows the part of CPU capacity that is unused. System and User divide activity between the system and user apps or related processes. Sort the process list by CPU and observe which process climbs during the delay. For an illustrative task, export a short video of your own and watch the exporter from start to finish. High exporter CPU during the export is expected. The same process staying busy minutes after the export ends deserves a separate check.
Memory across application switches
Read the Memory Pressure graph during a switch between your open apps. macOS can use spare RAM to cache files, so a high amount of used RAM alone is a weak signal. Pressure reflects how well memory serves the current demand and incorporates factors such as swap and cached memory. In a repeatable example, open your usual document set and compare the time to switch back to the same editor. After saving your work, close one app that was using substantial memory and repeat the switch. Falling pressure alongside a faster switch helps link the symptom to memory demand.
Disk activity during the delay
The Disk tab shows disk reads and writes. Look for a process whose counters rise during the pause, for example a backup completing or an app importing a sample archive. High transfer totals across the session can include activity long before the slowdown. Compare the time of the I/O with the pause. If a backup is writing heavily during your import, wait for it to finish. Then time a similarly sized import and compare the Disk tab at the same stage.
| Pattern that repeats | What to try next |
|---|---|
| CPU rises for one process at every delay | Pause that voluntary task and retry the action |
| Memory pressure rises when switching apps | Close one large workload and repeat the switch |
| One process reads or writes around each pause | Move the test outside that process's busy interval |
Record the task, time to finish, relevant tab and what changed during retest. If every reading looks ordinary while a single app hangs, investigate what that app was waiting on, such as a network request or a missing external drive.
Time the symptom before trying a fix
Choose an action that is simple to repeat. For example, open a small local document and measure the time until you can edit it. Keep the app and the file the same for the first two trials. Record whether the delay happened during an export, after returning to an idle app, or while a backup was running. Use the clock on the other part of the screen or a stopwatch so you can relate a graph change to the observed delay. A rising graph ten minutes later may belong to a different task.
Check the process list and the graph for a short interval before the action. Then watch while you perform it. A CPU spike can be expected from a program decompressing a file or rendering video. If the action slows whenever a second program also uses significant CPU, pause that voluntary work when safe and repeat. Time the change. A task finishing faster after a competing process is quiet gives you a reason to investigate shared load. It does not establish how the app will behave in a different workload.
Compare a useful memory and disk example
Imagine the editor takes fifteen seconds to become responsive after you switch back from a browser. Note the time and the pressure graph. Save your work and close one ordinary app that uses substantial memory. Then run the same switch with the same editor document. If the pause becomes shorter and pressure falls, record that comparison. Look at the trend and swap activity as well as any total in the window. Freeing memory without a change in elapsed time does not establish that memory caused the original pause.
For disk, use a test where the background work has a clear beginning and end. A photo import might be slow while a backup is writing heavily. Before the import, note the backup process and recent I/O. Wait for the backup to complete, then import a similar sample into a test folder. Check both the elapsed time and which processes changed. A one-time network download or external-drive reconnect can affect the same example, so keep the real source and destination paths in your notes.
| What changed around the pause | What to compare next |
|---|---|
| Exporter CPU rises and drops when the job finishes | Compare its elapsed time with other voluntary work paused. |
| Memory pressure grows when apps are switched | Compare the same switch after saving and closing one large workload. |
| Heavy writes overlap an import | Retest after the writing process finishes. |
| One app pauses with no matching graph change | Try a local file or check which resource that app is waiting for. |
Keep the comparison useful to someone else
Describe the system and task in ordinary terms. A note such as “PDF export sat for 19 seconds while a backup was writing, and took 8 seconds with it finished” is more helpful than saying the Mac was slow. Use illustrative values as a way to plan the comparison. When you measure, record the exact elapsed time and the app name. Keep the original workload mostly intact so you can reproduce a result.
Avoid force quitting a system process simply because its graph moved. For an app that terminates during the same action, save the timestamp and use the Mac crash report guide to find the relevant report. If it is a short sign-in delay, use the startup timing procedure so you can distinguish readiness from work you choose to launch later. Change one expected cause and see whether the original symptom follows it.


