How to Speed Up a Slow Computer
A practical checklist to diagnose and improve a slow desktop or laptop.
Choose one slow task and measure it before changing settings. A delayed website, a slow app launch and a laptop that slows down after twenty minutes need different investigations. This guide helps you decide which focused troubleshooting guide to use and whether a change actually helped.
In this guide
Identify the scope of the slowdown
Write a short description such as “my saved document takes a long time to open” or “video calls break up while local apps work normally.” Restart after saving work, let pending startup activity settle, and try the same task again. Note whether the problem occurs on battery, while plugged in, or both.
| What is slow? | Useful comparison | Next step |
|---|---|---|
| One website or online app | Try a different site and another device on the same network | Separate Wi-Fi and service problems |
| Only the browser | Compare the same task in a clean browser profile | Check tabs, extensions and profile |
| Windows startup and several apps | Observe activity after startup and during the slow task | Use the Windows 11 workflow |
| A game or demanding local app | Repeat the same scene or workload | Measure the limiting resource |
A comparison narrows the search; it does not prove the cause. If another device is fast, differences in its connection or software can still matter. Keep the task as similar as possible.
Observe resource use before closing apps
On Windows, open Task Manager with Ctrl + Shift + Esc and look at Processes and Performance while reproducing the slowdown. On a Mac, open Activity Monitor and inspect CPU and Memory. Note which process stays busy rather than treating a brief spike as a fault.
Memory allocated to apps and caches is not automatically wasted. On a Mac, Memory Pressure helps interpret whether the system is meeting current memory demand. On Windows, compare memory use and disk activity with the timing of the symptom. Neither a full-looking chart nor a single percentage establishes that you need new hardware.
Close an app normally after saving its work. Avoid force-stopping unfamiliar system processes. Pause one optional background task through its own controls, repeat the slow task, then restore it if there is no useful difference. Do not turn off security protection to obtain a faster-looking measurement.
Run a comparison you can reproduce
Keep a small measurement log: task, power source, apps open, time taken, change made and result. Use the same file or workload, and repeat the comparison. File caching and background updates can make a second run faster even when your change did nothing.
| Condition | Three task times | Middle value |
|---|---|---|
| Normal startup apps | 42, 44, 43 seconds | 43 seconds |
| One optional sync task paused | 31, 29, 30 seconds | 30 seconds |
In this example, the middle result improves by 13 seconds, or about 30% of the original time. That supports investigating the sync task; it does not prove the sync software is defective. Restore it and repeat to see whether the delay returns. A one-second change amid large run-to-run variation is weaker evidence.
Choose maintenance or an upgrade from the evidence
If storage is crowded, review your files and use the operating system's storage tools. Back up anything important before deletion. If slowness follows sustained use and heat, clear external vent obstructions and follow the device manual; a laptop on bedding has different airflow from one on a hard surface.
Consider more RAM only after checking workload demand and upgrade compatibility. Consider an SSD when a compatible system's storage is the demonstrated limitation. Some devices have soldered memory or storage, so an apparently simple upgrade may not be available. Use the upgrade decision guide before spending money.
Repeated read errors, unexplained shutdowns or inaccessible files change the priority: preserve important data and investigate reliability before running long benchmarks. If a change makes behavior worse, undo it and record the result. Keep improvements you can explain and reproduce.
Sources and scope
This diagnostic worksheet uses documentation and illustrative measurements, not a benchmark of your computer. Consult Microsoft's Windows performance guidance and Apple's explanation of memory use in Activity Monitor for the platform controls. Send a correction with the system version and the step that differs.