Performance guide

Why is my Mac slow? An evidence-first checklist

"Slow" can describe delayed app launches, a beachball, laggy typing, long builds, poor network response, or a Mac that never settles after startup. Diagnose the specific symptom before choosing a fix.

1. Describe when the slowdown happens

Note whether the problem occurs after login, while opening one application, during video calls, while compiling code, when waking from sleep, or all the time. A repeatable trigger narrows the investigation and gives you a way to verify improvement.

If the slowdown began recently, compare it with installed applications, startup changes, storage growth, battery behavior, backups, and system updates from the same period.

2. Check storage pressure early

A nearly full startup disk can affect updates, temporary work, virtual memory, and applications that need space for databases or media. Confirm current free space and whether it is still falling. Then measure broad sources before deleting files.

Freeing a small, verified amount of space is a useful test. If the symptom does not change, continue the investigation rather than repeatedly clearing caches.

3. Interpret memory as availability, not just use

macOS deliberately uses memory for caches, so a high "used" percentage is not automatically a problem. Look at available memory, memory pressure, swap behavior, and whether the slowdown aligns with opening a specific set of applications.

Quit one high-memory application you can safely reopen, repeat the affected task, and compare the result. Do not terminate unfamiliar system processes merely because they appear near the top of a list.

4. Review CPU and energy-heavy processes

A process using sustained CPU can cause heat, fan activity on supported models, shorter battery runtime, and reduced responsiveness. Sort processes by CPU and energy impact, then identify the owner, command, elapsed time, and risk classification.

Protected macOS processes should not be terminated through a cleanup workflow. For a third-party app, save work and quit it normally first. If the process returns immediately, a login item, background service, or helper may be relaunching it.

5. Inspect startup and background items

Login items, launch agents, launch daemons, and modern Background Task Management records can all add work after sign-in. Review the developer, scope, disposition, executable path, and whether the item is orphaned before changing it.

Disable one nonessential item through the application's own setting or macOS Settings, restart when appropriate, and compare startup behavior. Keep security, backup, accessibility, and device-management software in mind before disabling a helper.

6. Look for sleep blockers and unfinished background work

A Mac that does not sleep as expected may continue indexing, syncing, backing up, compiling, or playing media. Sleep assertions identify which process is asking macOS to stay awake, but an assertion is not automatically malicious or unnecessary.

Check whether the task is expected to finish. Interrupting a backup or sync can create a larger problem than the temporary slowdown.

7. Separate local performance from network delay

If only web pages, cloud documents, package downloads, or remote development tools feel slow, inspect network activity and listening ports. A stuck local development server, VPN, sync client, or high-bandwidth process can look like a general Mac problem.

Binding to a network interface does not by itself prove internet reachability. Treat port scope as one piece of evidence and keep firewall or router behavior separate.

8. Verify the change

1. Repeat the same task that felt slow.
2. Compare the same measurements before and after.
3. Record the action and result.
4. Reverse the change if it did not help and had a cost.
5. Continue with the next most likely cause.

Tend's Timeline and maintenance plans are designed around this loop: identify an issue, open the owning tool, take a bounded action, and advance only when the exact issue disappears.