What a 100-point CPU score can and can't tell you

A CPU test gives you a number, but that number can be easy to misread. A score of 80 does not mean your processor is using 80 percent of its capacity, or that it is 20 percent slower than every processor with a score of 100.

The Processor Test measures single-core and all-core speed and gives a score out of 100. Here is what those results can help you check, what they leave unknown, and how to compare scores without drawing the wrong conclusion.

Run the CPU test fairly

1. Open the Processor Test on the computer you want to check.
2. Close games, video exports, large downloads, and other tasks that are keeping the computer busy.
3. Run the test and note the score, plus the separate single-core and all-core results.
4. If you are checking a change, repeat the test under similar conditions. Keep the same computer, browser, power source, and settings where possible.

A browser test measures the processor while it is working in that browser, not in every program on your computer. A busy system or a different power state can affect the result, so treat one run as a snapshot rather than a permanent rating.

What the result means

The score is high or low on the test's scale

The score gives you a compact way to describe this test run. It is useful for comparing runs made with the same test and similar conditions. It is not a universal CPU grade: a score of 90 does not mean 90 percent of some maximum possible processor speed, and a score of 45 does not automatically mean a fault.

Single-core and all-core results differ

Single-core speed reflects work that uses one processor core at a time. All-core speed reflects work spread across several cores. A gap between the two is normal because the processor changes its speed and power use depending on how many cores are busy. The results can help you compare the two kinds of workload, but they do not predict an exact launch time, export duration, or frame rate in a particular app or game.

A repeat run is much lower than the first

Changing conditions may be affecting the result. Other tabs, background tasks, battery power, or heat can reduce performance during a later run. A lower score alone does not identify which cause is responsible or prove that the processor is damaged.

The score looks good, but the computer still feels slow

The CPU may not be the part causing the delay. Slow storage, limited memory, graphics performance, network problems, or an issue in one particular app can all make a computer feel sluggish. A short browser CPU test does not check all of those causes.

What to check if the score seems wrong

1. Let other work finish. Pause large downloads, file copies, video exports, and software updates, then run the test again. Avoid using the computer heavily while it runs.
2. Use a consistent power source. If you are comparing a laptop, run both tests plugged in or both on battery. Windows 11 power options are under Settings › System › Power & battery › Power mode on supported laptops. On macOS, check System Settings › Battery and note whether Low Power Mode is on.
3. Give the computer a chance to cool. If the case feels unusually hot or the fan is working hard, stop demanding tasks and allow it to cool before testing again. A browser cannot report the exact CPU temperature, so the score cannot confirm overheating by itself.
4. Repeat the same test. Use the same browser and close extra tabs. If one run is an outlier but several similar runs are close, do not treat the outlier as proof of a hardware problem.
5. Check for a wider slowdown. If everyday tasks remain slow, look at storage, memory, graphics, and the specific app involved. A CPU score cannot identify which component is responsible.

What a 100-point score cannot prove

The score does not tell you the exact CPU temperature, power draw, or whether the processor is healthy under every type of load. It cannot certify that a computer will run a particular game at a particular frame rate, or estimate exactly how long a video export will take. Those tasks use different software and can depend on graphics hardware, memory, storage, cooling, and settings.

It also cannot establish that two computers are equivalent just because their scores match. Different processor designs can perform similarly in this test but behave differently in specific programs. For the same reason, a score change after an update does not prove that the update caused a lasting hardware change. Repeat the test under controlled conditions before treating a small difference as meaningful.

When to look beyond the score

Use the result to ask a focused question: did this computer's test result change under similar conditions, or does one kind of CPU work score differently from another? If the score is consistently unusual and the computer also slows, overheats, or shuts down during normal tasks, check the cooling and power setup and consider a repair diagnosis. The browser score is a clue, not a complete hardware inspection.