'My laptop's slow' is one of the least useful support tickets to receive, not because it isn't real, but because it doesn't say which of several genuinely different problems is happening. Slow could mean the disk is the bottleneck, or memory, or the processor, or the network, or none of the above and it's actually a dozen browser tabs and a security tool arguing with itself. Guessing wastes time and, worse, it's how businesses end up replacing perfectly good hardware for a problem a five-minute check would have found, or limping along on genuinely worn-out hardware because nobody wanted to be the one who called it.
Windows already has the tools to find out which resource is actually under pressure. Working through them in order turns a vague complaint into a specific, fixable cause, or a confident case for a new machine.
Step one: work out which resource is the bottleneck
Open Task Manager, using Ctrl+Shift+Esc, and go to the Performance tab while the laptop is actually feeling slow, not after it's settled down. The four graphs there, CPU, Memory, Disk and Ethernet or Wi-Fi, tell most of the story on their own.
- 1Disk sitting near 100% while CPU and memory look calm points to a disk problem, most often a laptop with a mechanical hard drive rather than an SSD, or several background processes, security scanning, Windows Update, OneDrive sync, competing for the same drive at once.
- 2Memory consistently near its limit, especially alongside heavy activity on the disk from paging, points to a memory problem, usually too many applications and browser tabs open for the amount of RAM installed.
- 3CPU sustained high across many processes, rather than spiking briefly, points to a genuine processor problem, or occasionally one runaway process worth identifying by name in the Details tab.
- 4Everything calm except a specific task, choppy Teams calls, slow file opens from a shared drive, points to a network problem rather than the laptop itself, and is worth testing on a different Wi-Fi network before assuming the hardware is at fault.
Resource Monitor, reachable from a link at the bottom of the Performance tab, goes a level deeper if the Task Manager view isn't conclusive, showing which specific process is driving disk or network activity rather than just the total.
Startup applications
A laptop that takes minutes to become usable after login, rather than being generally sluggish once running, usually has too much launching automatically at startup. Task Manager's Startup Apps tab lists everything set to launch with Windows along with a relative startup impact rating, and disabling anything that doesn't genuinely need to run in the background, an old printer utility, a vendor's update checker, a chat app nobody uses, is a safe, reversible change most users can make themselves.
Storage pressure, and what it does to a machine syncing OneDrive
A disk running low on free space slows Windows generally, since the operating system needs working room for temporary files, the page file, and routine background maintenance, and performance tends to degrade well before the disk is technically full. On a laptop syncing OneDrive, low disk space compounds the problem specifically: OneDrive is constantly re-evaluating which files are downloaded locally versus online-only, and that housekeeping itself competes for disk activity on a drive that's already stretched thin. A machine that's both nearly full and syncing a large OneDrive account is often fighting itself.
Browser tabs and extensions
Modern browsers run each tab as something close to its own process, which is good for stability and bad for a laptop with limited memory sitting open with forty tabs across three windows. Chrome and Edge both have their own built-in task manager, opened with Shift+Esc inside the browser, that shows memory and CPU use per tab and per extension separately from Windows' own Task Manager. Extensions are worth checking specifically: most sit quietly, but ad blockers, shopping assistants and productivity tools that run continuously in the background can hold a surprising amount of memory even when their tab isn't the one open.
Pending updates and the sleep-versus-restart trap
A laptop that's been put to sleep every night for weeks rather than properly restarted accumulates memory that never gets reclaimed, background processes that never get a clean slate, and Windows and application updates that sit downloaded but not yet installed until a genuine restart happens. Closing the lid feels the same as shutting down; it isn't. A proper restart is a legitimate diagnostic step, not just the generic first line of every support script, and it's worth ruling out before assuming a slowdown needs a deeper fix.
Security software running two at once
A machine running two real-time security tools at the same time, commonly leftover consumer antivirus software that was never removed when the business's managed security tool was installed, spends real CPU and disk time with each one scanning the other's activity. This is a surprisingly common finding on fleet laptops that changed hands or were onboarded quickly, and checking the installed programs list for a security product nobody remembers installing is worth doing before assuming the slowdown is age-related.
Where fixing stops and replacing starts
Once the checks above are done and the laptop is still slow, the honest question becomes whether it's worth fixing rather than replacing. A few signals are worth weighing together rather than any single one on its own:
- A laptop still running a mechanical hard drive rather than an SSD is behind on performance no matter what else gets fixed; an SSD upgrade is often the single highest-impact change available on older hardware.
- Warranty and manufacturer support status matter more than age alone; a machine just out of warranty carries more risk per repair than one still covered.
- Repeated support tickets on the same machine, rather than a single one-off issue, are a sign the underlying hardware is the actual constraint, not the workload on it.
- Many business fleets plan around a roughly three to four year replacement cycle as a rule of thumb, not because hardware stops working at that point, but because the balance of reliability, support cost and staff time tends to tip around there.
None of this needs to be a guess, either. The same Task Manager checks that diagnose a specific fault also make the fix-or-replace conversation an evidence-based one rather than a feeling, which matters when it's a business making the call rather than one person deciding about their own laptop.