What a CPU score out of 100 really means

A CPU score out of 100 can look like a grade, but it is not a percentage of your processor’s maximum ability or a measure of how healthy it is. It summarizes how your device handled a particular test.

The Processor Test reports single-core and all-core performance, each with a score out of 100. Here is what those results can tell you, and how to use them without reading too much into one number.

Run the processor test

1. Open the Processor Test on the computer you want to check.
2. Close programs and browser tabs that are doing demanding work, such as video exports, large downloads, or games.
3. Follow the instructions shown by the test and let it complete its single-core and all-core checks. Keep the browser tab open while it runs.
4. Note both scores and, if you are checking a change, write down the browser, power state, and other conditions that could affect the result.

For a useful comparison, run the test under similar conditions each time. A result from a cool laptop plugged into power is not a fair direct comparison with one from a hot laptop running on battery.

What the result means

The score is a rating for this test

The number condenses measured processor performance in the test into a score on a 100-point scale. It is not a universal CPU rating shared by every benchmark. A score of 70 does not mean the processor is using 70 percent of its capacity, is 70 percent healthy, or is 70 percent as fast as the best processor available.

Use the score to compare results from the same test, especially on the same device. The number does not directly tell you a processor’s clock speed in GHz, the exact time an app will take, or how it will perform in every kind of work.

The single-core score reflects one stream of work

Single-core performance shows how the processor handles work that mainly runs on one core at a time. It can help explain responsiveness in tasks that do not spread their work across many cores. It does not represent every part of everyday use, since apps also depend on memory, storage, graphics, and software.

The all-core score reflects work spread across cores

The all-core result shows performance when the test can use multiple processor cores at once. It can be more relevant to parallel tasks, such as some rendering or encoding work. Do not expect it to match the single-core score. The tests exercise the processor differently, so compare each result with its own earlier results.

A lower result on one run may be temporary

Background apps, power-saving settings, heat, and browser conditions can all affect a test. A single lower number does not prove that the CPU is failing. If scores vary between attempts, see why CPU scores change between tests and repeat the check under steady conditions.

A similar score does not guarantee identical performance everywhere

Browser tests run through the browser and the operating system, so they cannot reproduce every desktop app, game, or professional workload. Use the score as a quick performance check, not as a promise about how a particular program will run.

How to get a more reliable score

1. Close demanding background work. Pause video exports, games, large file transfers, and other heavy tasks before testing. You do not need to close ordinary documents or settings windows.
2. Use steady power settings. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery › Low Power Mode. A power-saving mode may reduce performance to save energy.
3. Give the computer room to cool. If the laptop is hot or its fans are running hard, let it cool on a firm surface with its vents clear. Heat can make some processors reduce speed to protect themselves.
4. Keep the test conditions consistent. Use the same computer and browser, keep the device plugged in or unplugged in the same way, and avoid running other heavy work during the test. This makes changes easier to interpret.
5. Check whether the result repeats. If the first score seems unusually low, wait for the computer to settle and run the test again once. If the result stays low, compare with your own earlier score and look for a matching slowdown in the tasks you care about.

When to investigate a low score further

A score deserves more attention when it is consistently lower than your own baseline and the computer also feels slower in everyday work. Check whether the problem began after a settings change, an operating system update, or a change in how the computer is powered. A browser benchmark cannot identify a faulty component by itself, so treat the score as a clue rather than a diagnosis.

If the test result is steady but only one app is slow, the cause may be that app, its settings, or another part of the system rather than the processor. If the whole computer slows under load, gets unusually hot, or shuts down, back up important files and ask a qualified repair professional to check it.

Why the score is not a percentage

A score out of 100 is easy to read, but the number is not a measurement like 100 degrees or 100 megabytes per second. It is a rating produced for a specific test and scale. That makes it useful for a quick check and for comparing similar runs, but not for claiming that one CPU is a certain percentage faster in every situation.

For a fair before-and-after comparison, focus on repeatable changes in both scores and on what you notice when using the computer.