What a single-core score means for browser responsiveness

A browser page can feel slow even when your computer has several processor cores. Some of the work needed to respond to a click or update a page happens in a sequence, so one busy core can matter more than the total power available across all cores.

The Processor Test measures single-core and all-core speed and gives each a score out of 100. Here is how to read the single-core result, what it can and cannot explain, and how to check whether your computer is the reason a browser feels unresponsive.

Run the processor test fairly

1. Open the Processor Test on the computer whose browser feels slow.
2. Save your work, then close demanding tasks such as video exports, large downloads, or games. Leave the browser and ordinary background services running.
3. Run the test and note both the single-core and all-core scores. Keep the computer plugged in if you normally use it that way.
4. Repeat the test once under the same conditions. If the results are very different, wait a few minutes and check whether other work is using the computer.

For a useful comparison, use the same computer, browser, power state, and general workload each time. A score from a different device or a different browser environment is not a direct measure of how much faster your everyday pages will feel.

What the score means

A relatively strong single-core score

The processor handles the test's single-core work well compared with the scale used by the test. This is a good sign for tasks that depend on one core at a time, including some parts of page scripts and interface updates. It does not guarantee that every website will respond quickly. A page can still be held up by a slow connection, a busy main thread, a large image, an extension, or another bottleneck.

A low single-core score and a higher all-core score

Your processor can do more work when several cores are busy together than when one core works alone. That difference is normal for many processors. It can matter when a browser task cannot split its work into smaller parts, but it does not mean the processor is defective or that every page will be slow.

Both scores are low, or today's score is lower than usual

The computer may be running under conditions that limit processor speed, or another task may be competing for time. A low result can also reflect the device's age or the way the test runs in that browser. Compare it with your own earlier result under similar conditions before drawing a conclusion from the number alone.

The score is steady, but the browser still feels slow

The processor may not be the main cause. A website might be waiting for network data, loading a lot of content, or running scripts that keep the page busy. If only one site has the problem, compare it with another site and check that site's own behavior before changing system settings.

What to check when browsing feels slow

1. Check for a temporary workload. Pause a large download or video export, then try the same page again. A short-lived burst of work can make clicks and scrolling lag.
2. Compare with a clean browser session. Open the page in a private window, where extensions may be disabled depending on your browser settings. If it responds better, disable extensions one at a time to find a possible cause.
3. Check the power mode. On Windows 11, open Settings › System › Power & battery › Power mode and check the selected mode. On a Mac laptop, open System Settings › Battery and check Low Power Mode. A power-saving setting can reduce performance to extend battery life. Compare results using the mode you usually use, rather than treating a different mode's score as your normal result.
4. Retest after the computer cools down. If the laptop is hot or its fans are running hard, let it rest on a firm surface with its vents clear. Then repeat the processor test. A lower score while hot can point to reduced performance under heat, but the score alone does not identify the cause.
5. Restart the browser and computer. If many tabs or apps have been open for a long time, restart them and test again. This can clear a stuck process, though it will not fix a slow connection or a problem limited to one website.

Why single-core speed can affect a browser

A browser uses multiple processes and can spread some work across cores. However, many interface tasks have to happen in order. For example, a page may need to finish processing an interaction before it can update a specific part of the screen. If that work takes too long, the page can feel delayed even when other cores are available.

This is why a single-core score can be relevant without being a complete browser responsiveness rating. It measures processor performance in this test, not the time it takes your browser to load a particular site, draw every frame, or receive a response from a server. The all-core score helps describe performance when work can use more cores, but it cannot replace the single-core result or predict every workload.

Use the score as a clue, not a diagnosis. If the test results are consistent but only one browser or site is sluggish, focus on that browser, page, or connection before assuming the processor needs an upgrade.