Why storage benchmarks vary between browser runs

You run a storage test twice and get different speeds, even though nothing about your computer seems to have changed. That can happen because the test measures storage while the browser, operating system, and other apps are all sharing the device.

Use the Storage Test to compare large-file speeds, small writes, and the overall score. A few consistent runs can show whether the difference is ordinary variation or a slowdown worth investigating.

Repeat the storage test fairly

1. Open the Storage Test in the browser you normally use. Keep the same device and browser for each run.
2. Pause downloads, file copies, cloud sync, game updates, and other tasks that read or write large amounts of data.
3. Run the test once and note the large-file speed, small-write speed, and score. Avoid comparing only the score, since the two speed measures can behave differently.
4. Wait about a minute, then run the test two more times under the same conditions. Note whether results stay close, rise, or fall across the runs.
5. If the scores vary widely, restart the computer, let it sit for a few minutes, and repeat the three runs before opening other apps.

Small differences are not automatically a fault. A storage benchmark is a short sample of activity, not a guarantee that every future file copy will run at the same speed.

What the results mean

The three scores are close

Results that cluster around a similar range suggest the device is behaving consistently in those conditions. Small changes can come from normal background activity, measurement timing, or the way the operating system handles cached data.

Small writes vary more than large-file speed

Small writes involve many short operations, so interruptions from background tasks can have a noticeable effect. A sync service creating file records or an update checking lots of files may affect this result more than a single large transfer.

Large-file speed drops on later runs

A drive or its controller may slow down as it warms up, or as its fast temporary write area fills. Other activity can also compete for the drive. Give the computer time to cool and run the test again with background tasks paused. The browser test cannot tell you the drive's exact temperature.

Both speeds jump around

Look for changing conditions first: a download starting, a cloud folder syncing, low free space, or a computer switching power modes. Browser storage permissions can also affect how a browser-based disk test runs. The article What browser storage permissions mean for a disk test explains that limitation.

Every run is consistently slow

A repeatable low result is more useful than one unusually low score, but it does not prove the drive is failing. Check whether the same slowdown affects ordinary file work, and compare results again after removing background load. Browser tests cannot diagnose every drive fault or replace a full device health report.

How to reduce variation

1. Pause disk-heavy tasks. Stop large downloads, backups, file transfers, and cloud synchronization while testing. On Windows 11, Task Manager can show apps using the disk. On macOS, open Activity Monitor and check the Disk view.
2. Use a steady power mode. Connect a laptop to power and avoid changing its power setting between runs. On Windows 11, check Settings › System › Power & battery › Power mode. On macOS, check System Settings › Battery and turn off Low Power Mode for the comparison if it is enabled and available.
3. Let the device settle. If the computer or drive feels warm after a large transfer, wait several minutes before testing again. Repeated back-to-back runs can heat the storage device and change later results.
4. Keep browser conditions the same. Use the same browser, avoid switching between private and normal browsing, and close extra tabs or extensions that may be doing work. A different browser can use a different storage implementation, so its score is not a direct comparison.
5. Check available space. Very low free space can make normal computer tasks less predictable. Check the operating system's storage settings and remove or move files only if you have a safe backup and know what they contain.
6. Compare after a restart. Restarting can stop a stuck process or clear a temporary burst of background activity. Let the computer finish startup work before testing, then repeat the same three-run process.

Why a browser result can change

The Storage Test measures disk performance through a browser, rather than by running a dedicated drive diagnostic program. The browser and operating system manage access to storage, and other work can interrupt the test. The result is therefore a useful comparison under similar conditions, not a fixed specification for the drive.

Scores also reflect the type of work being measured. Reading or writing a large file is different from making many small writes. A drive can be quick at one and slower at the other, so focus on the result that matches the problem you notice in everyday use.

If repeated tests remain slow and file copies also stall, back up important files before doing more troubleshooting. A benchmark can suggest that performance changed, but it cannot confirm whether the cause is the drive, its connection, available space, or another part of the system.