Why Is My MacBook Pro Running So Slow: Where the Work Piles Up

A MacBook Pro that felt fast a year ago and feels slow this morning has rarely aged into it. The hardware is the same. What changed is the number of things running at once, the number of things that start themselves at login, and the number of browser tabs that are still holding a live connection to a server somewhere. The machine is not degrading. The workload grew past what it was set up to carry.

That distinction matters because the two situations lead to opposite decisions. A genuine hardware limit is solved by buying memory, which on Apple Silicon means buying a different Mac. A workload problem is solved by changing an arrangement, which costs nothing. Most of the advice available for this search treats every slowdown as the second kind, or sells the first. What follows is how to tell them apart before spending anything.

Start by naming which kind of slow it is

There are three different complaints hiding behind the phrase "running slow", and they have different causes.

The first is the beachball. An app stops responding, the pointer becomes a spinning wheel, and everything else keeps working. This is one application in trouble, not the machine.

The second is a system-wide stall. Switching between windows takes a second, typing appears late, menus open slowly, and the effect follows attention around rather than staying in one app. This is a resource problem, and it is the one worth investigating.

The third is slow start-up and slow switching in the first ten minutes after logging in, followed by normal speed. This is almost always the queue of items that open automatically, plus indexing and sync catching up.

Before doing anything, watch for a day and decide which of the three describes the experience. Open Activity Monitor, which sits in the Utilities folder inside Applications, and leave it running in a corner. Click the CPU column heading to sort by usage, and look at what is at the top when the slowness happens. If one name sits at the top with a high percentage while the total is otherwise calm, the problem has a name and the rest of this article is optional.

Read the Memory tab before concluding the Mac needs more RAM

The Memory tab is where most self-diagnosis goes wrong, because the number people look at is the wrong number. Memory Used is almost always close to the amount installed, on every Mac, working correctly. Unused memory is wasted memory, so macOS fills it with cached files that speed up the next launch. A Mac showing 15 GB of 16 GB used is not necessarily in trouble.

The figure that actually answers the question is Memory Pressure, and Apple describes exactly what feeds it.

Memory Pressure: Graphically represents how efficiently your memory is serving your processing needs. Memory pressure is determined by the amount of free memory, swap rate, wired memory, and file cached memory. Source: support.apple.com

Two other rows on the same tab decide the verdict. Compressed is the amount of memory macOS has squeezed to keep more of it available, and the same Apple page explains that as a Mac approaches its maximum memory capacity, inactive apps in memory are compressed so active apps get more room. Compression is cheap and invisible. Swap Used is the amount of space being used on the startup disk to move unused files in and out of RAM, and that is not cheap, because the disk is slower than memory by a wide margin.

The practical reading is this. Memory Pressure staying flat with Swap Used near zero means the machine has enough memory for the work being asked of it, and the slowness has another cause. Memory Pressure spiking whenever a particular app comes forward, with Swap Used climbing into the gigabytes and staying there, means the work genuinely exceeds the installed memory. Apple publishes a short page on using Activity Monitor to decide whether a Mac could use more RAM, and on Apple Silicon that decision is a purchase decision, because the memory is part of the chip package and cannot be added later.

Browser tabs are the most common answer, and they are not equal

On a machine used for work in web applications, the browser is usually the largest single consumer, and the total is not proportional to the number of tabs. A parked documentation page costs almost nothing. A mail client, a chat workspace, a project board and a spreadsheet each hold an open connection, run timers, and re-render on incoming events whether or not they are visible. Ten of those is a heavier load than a hundred articles.

Chrome now ships a setting aimed at exactly this. Memory Saver deactivates tabs that are not in use and reloads them automatically on return, and it offers three levels: Moderate, which lets tabs go inactive after a longer period, Balanced, which Google marks as recommended, and Maximum, which deactivates them sooner. The same Performance section holds an exclusion list called sites that are always active, which matters because a tab that must never be reloaded, such as one holding a half-written message, belongs on that list rather than left to chance.

Google also documents which activities block deactivation entirely: active audio or video including calls, screen sharing, page notifications, active downloads, partially filled forms, pinned tabs, and connected USB or Bluetooth devices. That list is worth reading closely, because it explains why a chat application pinned as a tab never gets deactivated and never gets cheaper. The setting cannot help with the tabs that are the actual problem, because those are precisely the ones it is designed not to touch.

The things that were already running before the first click

If the slowness is concentrated in the first minutes after logging in, the cause is a queue rather than a shortage. macOS collects the list in one place: choose Apple menu, then System Settings, then General in the sidebar, then Login Items and Extensions.

Two lists live on that screen and they behave differently. The upper list holds apps, documents and folders that open when logging in. The lower group controls whether an app is allowed to run in the background, which Apple describes as performing tasks when the app is not open, such as checking for software updates or syncing data. Updaters, sync agents and helper tools accumulate there quietly over years, and each one was agreed to once, during an installation, as a checkbox nobody read.

There is a fast way to test whether that queue is the cause without removing anything. Apple documents holding the Shift key while clicking Log In, which temporarily prevents login items from opening. If the same Mac feels normal after a Shift-held login and sluggish after an ordinary one, the answer has been found and the only remaining work is deciding which items stay.

Storage belongs in the same section, because a startup disk with very little space left has nowhere to put swap. If Swap Used is high and free space is low, the two are related, and freeing space is the cheaper of the two fixes.

Match the symptom to the place to look

What is happening	Where to look first	What it usually means
One app beachballs, the rest is fine	Activity Monitor, CPU tab	That app, not the machine
Everything lags while several web apps are open	Memory tab: Swap Used, Compressed	Workload above installed memory
Slow for ten minutes after login, then fine	Login Items and Extensions	A start-up queue, not a shortage
Fans loud, body warm, speed drops after a while	Activity Monitor, CPU and Energy tabs	Sustained load, thermal limit
Feels busy but nothing is measurably loaded	Notification and switching pattern	An attention problem, not a resource one

The last row is the one that gets misfiled most often, and it is worth treating separately.

When the slowness is in the switching, not the silicon

There is a version of this complaint that no measurement supports. Memory Pressure is flat, no process is above a few percent, and the working day still feels like wading. What is slow in that case is the retrieval, not the machine. Finding the right window among forty tabs spread across several windows takes a second or two, that second happens dozens of times an hour, and every one of them arrives with a decision attached about whether to read the notification that just appeared.

Nothing in Activity Monitor shows this, so it survives every round of cleaning. The fix is not a faster Mac. It is an arrangement where each web application holds a fixed, findable place instead of competing for a slot in a tab strip, which is the idea behind Workspaces and the reason the same set of applications can feel calm in one arrangement and frantic in another. Keeping each application in its own window also keeps each one's session separate, so three accounts on the same service can stay signed in at once rather than trading places.

The measurable side effect is smaller than people expect and the felt difference is larger. Consolidating work applications into fixed windows does not reduce total memory use by much, because the same applications are still running. What it removes is the search. The Supported apps list is a reasonable way to check whether the handful of tools that make up a working day are covered before rearranging anything.

Heat is a speed setting, not just a noise

A MacBook Pro that is fast for twenty minutes and then noticeably slower, with the fans audible and the case warm near the hinge, is not failing. It is being held back on purpose. Sustained load raises the temperature of the chip, and the system lowers clock speed to stay inside its thermal limits. The result is a machine that benchmarks well for short bursts and feels sluggish during long ones, which is exactly the pattern that makes people suspect their Mac is wearing out.

The Energy tab in Activity Monitor is the right place to check this, because it ranks processes by energy impact rather than by momentary CPU use, and sustained energy is what produces heat. A video call that runs for an hour, a browser tab rendering an animated dashboard, and a build or sync job left running in the background all show up there even when no single one of them looks alarming on the CPU tab.

Two physical conditions make the ceiling arrive sooner, and both are worth ruling out before blaming software. A laptop working on a soft surface such as a bed or a cushion has less room to move air than one on a desk. Dust accumulated in the vents over several years has the same effect. Neither is a reason to reinstall anything, and both are cheaper to address than any of the other fixes in this article.

What to change first

Run one Shift-held login and one ordinary login on the same day, and compare. That single test separates a start-up queue from a real memory shortage in ten minutes, and it decides whether the next step is pruning Login Items or changing how the browser holds work applications. If the count that dominates the day turns out to be switching rather than loading, the arrangement to try next is one window per application, which is what SpaceDeck is built around.