Mac Slow After Waking From Sleep? Here's Why
A Mac that takes thirty seconds to feel normal after waking is not failing. Several things happen at once when it wakes, and on a machine with a lot open, or a nearly full disk, they collide. Here is what is actually happening and which parts you can change.
What happens in the first thirty seconds
On wake, macOS reconnects Wi-Fi and re-authenticates, remounts network volumes, resumes every cloud sync client, reloads pages that were purged from memory, and lets any app that requested a wake window do its work. On a healthy Mac with plenty of free memory and disk, that is a couple of seconds. On a loaded one it is a queue.
Check memory pressure first
Open Activity Monitor → Memory and look at the Memory Pressure graph at the bottom, not the numbers above it.
- Green — memory is fine. The slowness is something else on this list.
- Yellow or red — macOS is compressing and swapping. Waking means decompressing a lot of memory at once, which is exactly the delay you feel.
Check the Swap Used figure on the same screen. A large number here on a Mac that has been asleep is the clearest explanation there is. The fix is having fewer things open, particularly browser tabs, or more memory.
# quick view of memory and swap
vm_stat | head -8
# top processes by memory right now
ps aux | sort -nrk 4 | head -8
Cloud sync is the second suspect
iCloud Drive, Dropbox, Google Drive and OneDrive all resume on wake and check what changed while you were away. If you sleep the Mac at the office and wake it at home, that is a large reconciliation running at exactly the moment you want to type.
Watch Activity Monitor → Network and Disk for the first minute after waking. If either is busy, that is your answer. Most sync clients let you limit bandwidth or pause, and pausing for the first minute after a wake is a reasonable habit on a busy machine.
Wi-Fi reconnection
If the Mac feels responsive but nothing loads for twenty seconds, it is the network rather than the machine. macOS has to reassociate and get an address, and captive portals in offices and hotels make it worse. Reducing the number of remembered networks helps: System Settings → Network → Wi-Fi → Advanced, remove old ones and move your main network to the top.
Disk space, which affects everything
An SSD with very little free space slows down substantially, and macOS also needs room for swap. Check it:
df -h /
Below about 10% free, everything on this page gets worse. Freeing space is the highest-value fix if that is where you are.
Spotlight and Photos, after any big change
If the sluggishness is not confined to the first minute after waking but lasts for hours, check whether an index is rebuilding. Spotlight reindexes after macOS updates, after restoring from a backup, and whenever a large volume is connected. Photos re-analyses its library for faces and scenes on a similar trigger.
# is Spotlight indexing right now?
mdutil -s /
Both show up in Activity Monitor as mds, mds_stores or photoanalysisd using sustained CPU. Neither is a fault and both finish on their own, usually within a day. Leaving the Mac plugged in and awake overnight is the fastest way through it.
What to change
- Turn off Power Nap in Battery → Options. It means the Mac has been working while asleep, and it wakes with a backlog.
- Set Wake for network access to Never, so the machine sleeps properly rather than half-waking repeatedly.
- Close what you are not using before a long sleep, especially browser windows.
- Keep 10% of the disk free as a working minimum.
- Restart weekly. Not superstition: it clears leaked memory from long-running apps, which is the single most common reason a Mac that was fine in March is sluggish in June.
Power Nap, wake for network access and the other sleep behaviours are one-click toggles in Mainspring, each described in plain English and reversible.
Try Mainspring free →Signed & notarized by Apple · 1-day free trial · $29 once