Why Is My Mac Running Slow?

CPU overload occurs when one or more processes consume all available processor cycles. A single misbehaving application can pin an entire core at 100%, leaving other tasks waiting for processing time. The result is a Mac that feels unresponsive to clicks, keyboard input, and window switching.

RAM pressure builds when the total memory requested by running applications exceeds the physical RAM installed. macOS compensates by compressing memory and writing overflow to a swap file on the startup disk. Both compression and swap operations consume CPU cycles and disk bandwidth, compounding the slowdown.

A full startup disk leaves macOS without the free space it needs for swap files, temporary caches, and virtual memory. When available space drops below 10% of the drive capacity, performance degrades noticeably as the system struggles to manage its working files.

Outdated macOS versions may lack performance optimizations, driver updates, and bug fixes that Apple ships in newer releases. Login items that accumulate over time launch automatically at startup, each consuming CPU and RAM before you open a single application. Malware, though less common on macOS, can run hidden processes that quietly drain system resources.

Activity Monitor's CPU tab lists every running process alongside its CPU consumption percentage. Clicking the %CPU column header sorts processes from highest to lowest usage, immediately revealing which application or service is consuming the most processor time.

The Memory tab provides a similar view for RAM consumption. The Memory Pressure graph at the bottom of the window uses color coding: green indicates sufficient memory, yellow means the system is compressing memory, and red signals heavy swap usage. A persistently yellow or red graph points to RAM as the bottleneck.

Processes you do not recognize may be system services or background agents. Common examples include mds_stores (Spotlight indexing), photoanalysisd (Photos face recognition), and WindowServer (display compositor). These processes normally finish their tasks and release resources, but a stuck process can consume CPU indefinitely.

macOS uses a memory compression system that shrinks inactive memory pages to free up physical RAM. Compression is fast but not free; it requires CPU cycles that would otherwise serve your applications. Under heavy memory pressure, the processor spends a measurable percentage of its time compressing and decompressing memory pages instead of running your tasks.

Swap occurs when compressed memory still cannot free enough RAM. macOS writes memory pages to a swap file on the startup disk, trading fast RAM access for dramatically slower disk access. Even on an SSD, swap is orders of magnitude slower than reading directly from RAM.

Page outs, visible in Activity Monitor's Memory tab, indicate how much data macOS has written to swap. A high page out count during normal usage confirms that the Mac does not have enough physical RAM for its current workload. The only permanent fix is reducing memory demand or, on Macs with upgradable RAM, adding more memory modules.

The swap system writes memory overflow to the startup disk. Without sufficient free space, macOS cannot create or expand swap files, forcing it to terminate background processes or refuse to open new applications. This makes the Mac feel frozen even though the processor and RAM may have capacity.

macOS also maintains caches for application data, system fonts, icons, and web content. These caches speed up repeated operations, but they require free disk space to function. A full disk forces the system to regenerate cached data repeatedly, wasting CPU cycles and disk bandwidth on work that should be instant.

APFS, the file system on modern Macs, uses snapshot technology for Time Machine backups and system updates. Local snapshots can consume tens of gigabytes. Checking storage in System Settings > General > Storage reveals how much space macOS has allocated to system data, caches, and other categories that can be reclaimed.

Diagnosing a slow Mac requires checking multiple metrics simultaneously. CPU load reveals whether a runaway process is consuming all available cycles. RAM pressure shows whether the system is compressing memory and swapping to disk. Disk usage confirms whether the startup drive has sufficient free space for macOS to operate efficiently.

Activity Monitor can display each of these metrics, but only one tab at a time. Switching between CPU, Memory, and Disk tabs while trying to correlate a performance issue is slow and disruptive. MoniThor consolidates all three into a persistent menu bar display that updates every second.

Color-coded values shift from green to yellow to red as each resource becomes constrained. A quick glance at the menu bar tells you whether CPU, RAM, or disk is the bottleneck, letting you focus your troubleshooting on the right area immediately.

Restarting clears memory leaks, resets runaway processes, and forces macOS to rebuild system caches. Many slow Mac issues resolve immediately after a restart because accumulated system state is wiped clean.

Closing unused applications and browser tabs frees both CPU and RAM. Each open browser tab runs its own process, and tabs with animations, video, or complex JavaScript can consume a full CPU core. Reducing open tabs from 30 to 10 often produces a noticeable improvement.

Freeing disk space gives macOS room for swap files and caches. Deleting large unused files, emptying the Trash, and clearing old downloads are quick ways to reclaim space. Maintaining at least 10% free on the startup disk prevents storage-related slowdowns.

Login items accumulate as you install applications. Open System Settings > General > Login Items and remove anything you do not need at startup. Fewer login items mean a faster boot and more available resources for the applications you actually use.

Updating macOS ensures you have the latest performance optimizations, driver updates, and security patches. Checking for malware with a reputable security tool rules out hidden processes that silently drain resources in the background.