When a Mac Runs Slow

A slow Mac produces a particular kind of quiet despair: everything still works, nothing works quite fast enough, and the temptation is either to ignore it or to buy a replacement. Between those two poles sits a methodical middle, because sluggishness almost always has a findable cause, and the causes announce themselves in a fairly reliable order. This checklist walks that order, from the cheapest and most common culprit to the honest question of hardware, and every step uses tools already on the machine. Nothing here requires purchases, and nothing requires opening the case.

First, define what slow means

Measurement before medicine. Note precisely what feels slow: startup, logging in, launching applications, switching between them, web pages, file saves, or everything at once. A machine that is slow only in the browser has a browser problem, not a Mac problem; a machine slow from the moment of login has a startup problem; a machine slow only in one application has an application problem. Ten minutes spent pinning the symptom down saves an afternoon of scattered fixes. Write the answer down, because the end of this checklist is comparing the machine against that first note.

Step one: storage space

Start here because it is the most common cause and the cheapest to check. About This Mac, from the Apple menu, shows Storage settings; System Settings offers the same view on newer systems. When a drive approaches full, the system loses room for the temporary files it needs for almost everything, and slowness spreads across every application at once. The working rule of thumb is to keep roughly a tenth of the disk free, more on small drives. Clearing space is unglamorous work: empty the Trash, look at the Downloads folder, which on most machines holds years of installers and duplicates, offload old photo libraries and video files to an external drive, and let the system's own storage recommendations show the large items. The commands in the Terminal basics guide, notably du, show exactly where the space went when the graphical view is too vague. And before any large deletion, the discipline from the backup guide applies: have a backup first, because cleanup done in a hurry is how files are lost properly.

Step two: login items and background helpers

The second look goes to everything that starts with the machine. System Settings carries a Login Items panel listing applications and background helpers allowed to launch at startup, and most machines accumulate years of them, updaters, cloud sync clients, assistants for printers long gone, each taking memory and a slice of processor forever. The honest review is to ask of each entry what it does for work done this month, and to remove the ones without an answer; they can be reopened when needed. The same panel on recent systems shows which items had the largest impact at last login. This step rarely transforms a machine alone, but it compounds with every other one, and it shortens startup immediately.

Step three: Activity Monitor, the honest witness

Activity Monitor, in the Utilities folder, is the machine's own account of itself, and Apple's Activity Monitor user guide documents every column. Sort the CPU tab by percentage and watch for a process holding the processor at the top while nothing visible is happening; the names vary, a browser helper, an indexer, a sync client, an application stuck in a loop, but the pattern does not. The Memory tab tells its story through the memory pressure graph at the bottom: green means the machine has room, yellow means it is working at the edge, red means it is swapping to disk, which reads as exactly the sluggishness being investigated. The Energy tab shows which applications draw the most power, a fair proxy for background misbehaviour. The discipline is to observe before quitting anything: a process doing genuine work, a scheduled backup, a photo analysis pass, will finish and release the machine, while a stuck one will sit at the top indefinitely, and the difference is the diagnosis.

Step four: the quiet system work

Some slowness is the machine thinking, and the two famous examples both announce themselves. Spotlight, the search index, rebuilds itself after a large file change or a system update, visible in Activity Monitor as processes named mds and mdworker, and it finishes faster if the machine is left plugged in and busy rather than interrupted. Photos analyses a library after an upgrade, recognising faces and scenes, which can run for a night or a week depending on library size. This work is one time, self limiting, and worth letting finish, because interrupting it only prolongs the aggregate. The trap is mistaking it for a fault and reinstalling in response, which resets the work and the slowness together. The measurement habit from step three distinguishes the cases: genuine system work tapers off over days, faults do not.

Step five: the browser, a small operating system of its own

When the slowness lives mainly in web work, the browser is the first suspect, and the investigation is proportional. Count the tabs; each one holds memory and some hold scripts running in the background, and a session of eighty tabs is a workload in itself. Review the extensions, which sit inside every page and can slow all of them for one feature occasionally used. Empty the cache if a specific site misbehaves, and test the same pages in a second browser with no extensions: if the machine is quick there, the Mac was never slow, the browser was. This step costs ten minutes and settles a surprising share of slow Mac complaints from readers who were certain the machine was dying.

When hardware is the honest answer

After the checklist, some machines remain slow for physical reasons, and saying so plainly is kinder than promising otherwise. A machine whose memory pressure sits permanently red with a normal workload needs more memory, which on most modern Macs means a different machine, since the memory is built in. A machine with a spinning hard drive, common in older models, transforms with a solid state drive, where such an upgrade is possible. A battery in a poor state can pull performance down on portable models, and the system reports its condition in the battery settings. Age itself is a fair answer: a machine carrying a decade of service and a current operating system it was never designed for is allowed to feel its years. The checklist's value is knowing the difference between a machine that needs attention and a machine that needs replacing, and that knowledge is worth its hour.

The rhythm that keeps the machine quick

Most slow Mac episodes trace back to the same small neglects compounding: a drive creeping toward full, a startup list growing by one helper a year, a browser accumulating tabs and extensions. A brief seasonal pass through this checklist, the same rhythm the Workshop section preaches throughout, keeps those causes from ever combining. The readers who never meet this problem are not the ones with better machines; they are the ones with the checking habit, and the habit takes twenty minutes a season.