Skip to main content

PC slow in the afternoon? Run this test before buying a new one

A PC that slows down around 3 p.m. does not necessarily need replacing. A twenty-minute test, with the right gauge, separates a memory shortage, a runaway process and a real hardware limit.

Avatar of Diane
CMDglows article cover on Windows performance
  • In the morning your PC keeps up without effort. Around 3 p.m. everything turns sluggish: tabs reload, the video call stutters, and you start browsing laptop listings, usually on a feeling.
  • A feeling does not tell you whether memory is running out, whether a process is burning the processor in the background, or whether the gauge you are reading has stopped being honest. Buying on that basis costs money and rarely fixes the problem.
  • This test takes twenty minutes spread across a normal working day. It installs nothing: Task Manager, already built into Windows, is enough.

You probably know the pattern. In the morning the machine keeps up. Around 3 p.m. the cursor hesitates, the browser takes a second to respond, and the question arrives: do you need a new PC?

The trap is answering on a feeling. A machine that slows down in the afternoon may be short of memory, carrying a process that eats resources for nothing, or being read through an indicator that no longer reflects reality. Three causes, three fixes, and a purchase only solves the last one.

The test below separates them over one working day.

The gauge can lie

Before you read a number, you need to know which one to trust. On a loaded machine, I compared several indicators with Task Manager. Two traps kept coming back.

The Performance widget of the Xbox Game Bar froze on old values: 94% CPU on screen while Task Manager showed 30%. A third-party utility, TrafficMonitor, stayed pinned at 100% while Task Manager showed between 56 and 83%. The project has open tickets about this same gap and has for a long time. In both cases the number looked believable. It was wrong.

The rule that follows: during the test, only Task Manager counts. Open it with Ctrl + Shift + Esc.

The test, step by step

  1. Open Task Manager on the Performance tab. Right-click a graph and choose Summary view: only a column of values remains.
  2. Work normally all day. Keep your tabs, your tools, your rhythm. Do not close anything for the test, or you measure a machine you do not actually use.
  3. At 10 a.m., 1 p.m. and 3 p.m., or as soon as things slow down, note three numbers: memory, CPU, disk.
  4. When it slows, switch to the Processes tab and sort by Memory, then by CPU. Note the top two names in each column.

What your numbers tell you

If memory stays above 85% during working hours, the machine starts spilling into the disk, and that is usually where everything slows down. Before concluding that your PC is too weak, check whether your model accepts more RAM: some laptops solder it to the board. If it can be upgraded, that is often the cheapest fix. If it is soldered, memory becomes the real argument for a new machine.

A process holding 80% of the processor for several minutes while you ask it nothing is not your machine’s fault. Close it, and uninstall it if you no longer use it. A processor that climbs during an export or a compile and then drops back is simply doing its job.

If nothing saturates and everything still feels slow, look at the disk. A spinning hard drive combined with apps launching at startup often explains what the graphs do not show. An SSD is then the most visible change, long before you replace the processor.

What the test does not tell you

One day will not tell you whether your disk is wearing out: that needs its health indicators, a separate check. It also does not measure your graphics card for games or for a local AI model. If that is your question, you need a dedicated test.

What this changes for you

The test gives you a verdict before you spend anything: a process to stop, a setting to change, or a real reason to replace the machine. To keep a permanent indicator and learn to read it day to day, the System Health lesson of the Windows module walks through the method step by step.

Sources

Measurements: my own captures on a loaded machine. Link checked on November 1, 2026.

See the source for this article
  • zhongyang219, TrafficMonitor project, ticket “CPU usage values in taskbar widget different than the Task Manager” — GitHub

Was this article helpful?

Related Articles