How to compare RAM scores with memory compression on

Your RAM test score changes from one run to the next, and memory compression is enabled. That does not automatically mean your memory is slower or that the RAM is faulty. Compression is one way the operating system manages memory when it needs room for more work.

Use the Memory Test (RAM) to compare read, write, copy speed, and response time under consistent conditions. Then check the operating system's memory status so you can tell whether the scores were taken under similar conditions.

Compare RAM scores

1. Open the Memory Test (RAM) on the computer you want to check. Run it in the same browser each time.
2. Before the first run, note the score out of 100 and the read, write, copy, and response-time results. Also note how much memory is compressed, if your system shows that information.
3. Repeat the test two more times without changing apps, browser tabs, power settings, or other system conditions. Record each result rather than relying on one run.
4. Compare the typical result for each measure. If you are comparing two different memory-compression states, change only that state and repeat the same three-run process after the system settles.

A test run can create short-lived memory and processor work. Close large downloads and unnecessary apps first, but do not close the same set of apps in one test and leave them open in another. That changes the conditions you are trying to compare.

What the result means

Scores are close across repeated runs

Small differences are normal. The browser, operating system, background tasks, and current memory pressure all affect a browser-based test. If the read, write, and copy results stay in a similar range, a small change in the overall score is not strong evidence of a hardware problem.

Scores fall when compressed memory increases

This can happen when other apps are competing for memory or the computer is doing more work. Compression uses processor time, and the operating system may be moving or reclaiming memory while the test runs. The result shows how the system performed in that moment, not a fixed speed rating for the RAM.

Scores differ but compressed memory looks similar

Memory compression is only one possible influence. Browser activity, power-saving modes, heat, and background processes can also change the result. Compare each part of the test: a change in copy speed does not necessarily mean read speed or response time changed in the same way.

Compression is shown, but the score is normal

That is not a contradiction. Compressed memory is generally used to store less-active data in a smaller space. Seeing a compressed-memory amount does not mean the test's active data was compressed, nor does it prove that compression caused a score difference.

How to make the comparison fair

1. Check the memory status. On Windows 11, press Ctrl + Shift + Esc to open Task Manager, then choose Performance › Memory. Look for the amount shown as compressed within the in-use memory figure. On macOS, open Applications › Utilities › Activity Monitor › Memory. Check the Memory Pressure graph and the compressed-memory figure.
2. Keep the computer plugged in. On Windows 11, check Settings › System › Power & battery and use the same power mode for every run. On a Mac laptop, keep it connected to power for each run, or use the same battery condition and power settings throughout.
3. Wait for other work to finish. Pause file transfers, software updates, video exports, and large downloads. Wait a minute after closing an app before running the test, then keep that same routine for each comparison.
4. Use the same browser conditions. Keep the browser version, open tabs, and extensions unchanged. Avoid comparing a private window with a normal window, or one browser with another.
5. Compare repeated runs, not a single score. Record three results in each condition and compare the middle result or the general range. If one run is far outside the others, repeat it after checking for background activity.

Windows and macOS manage memory compression automatically. Their normal settings screens do not offer a simple on-and-off switch for a routine benchmark comparison. On a Mac, use the displayed memory status to describe the condition rather than trying to force compression off. On Windows, the compressed amount can change as memory demand changes, even though the feature remains enabled.

What this browser test cannot tell you

The Memory Test measures browser-accessible memory behavior, including read, write, and copy speed and response time. Its score is a convenient comparison, not a complete hardware diagnosis. It does not report the exact amount of installed RAM, directly measure the operating system's compression ratio, or identify a defective memory module.

Browsers also receive only a rounded hint about RAM size, so this test cannot confirm the computer's exact memory capacity. If you see an unexpectedly large or persistent performance drop, compare the test with normal use and check the computer's built-in system diagnostics before assuming compression is the cause.