A high number on a performance screen can look alarming. Before acting on it, record what the computer was doing and whether the reading coincided with the problem you felt. A snapshot is an observation, not a verdict on the machine.
Start here
Connect the reading to a real task
Record the task first, then the category, value and timing you observed.
Use the built-in Task Manager
On Windows 11, press Ctrl + Shift + Esc to open Task Manager. Look at the Processes and Performance views. Microsoft describes Task Manager as a way to inspect CPU, memory and disk activity. See Microsoft's performance guidance.
This is an educational use of a Windows tool, not a claim that every Naked Tech assessment uses one fixed diagnostic procedure.
Give the numbers some context
| Record | Why it belongs beside the reading |
|---|---|
| The task you were doing | “Opening my browser” is more useful than an isolated number. |
| When the delay happened | Distinguish before, during and after the slow moment. |
| The displayed category and value | Keep the name and units; do not rename memory as storage. |
| Whether the reading changed | A brief peak and a continuing pattern are different observations. |
| Other work you recognised | Note an update or application you saw, without assuming it caused the delay. |
You do not need a universal “good” percentage. Avoid comparing your computer with a different machine doing different work. If a reading appears high, write down the observation and the symptom rather than diagnosing a failed part.
Make a short record
A fictional example:
Know what this exercise cannot decide
Put your observations into the assessment-notes checklist. If the wait happens mainly online, the computer or internet guide may be the more useful starting point.
What to read next
If you’d rather have local help, see our slow computer assessment.