Why a browser storage score changes after a restart

You run a storage test, restart your computer, and get a different score. That does not automatically mean your drive has changed or is failing. A restart changes what the computer is doing in the background, and browser-based tests can also vary from run to run.

Use the Storage Test to compare large-file speed and small writes. The steps below help you make a fair comparison and work out whether a score change points to normal variation, a setting, or a possible drive problem.

Compare storage scores fairly

1. Open the Storage Test on the computer and drive you want to check. Use the same browser and keep the computer connected to power for each run.
2. Run the test once before restarting. Note the score and the large-file and small-write results, if shown.
3. Restart the computer. After signing in, wait a few minutes for startup apps and system activity to settle, then open the same browser and test the same drive again.
4. Run the test two more times under the same conditions. Compare the range of results, not just the best score, and note whether one part of the test changed more than the others.

If the drive is nearly full or other programs are copying files, pause the comparison until those conditions are steady. For an external drive, use the same cable, port, and hub arrangement each time.

What the result means

The score changes, but repeat runs are close together

A single difference between before and after a restart is often ordinary test variation. A browser test runs through the browser and operating system, so it can be affected by scheduling, background work, and the state of the computer. If repeated runs in each condition cluster together, compare their typical results rather than treating one score as definitive.

Small writes change more than large-file speed

Small writes involve many short operations, so background activity and system responsiveness can have a noticeable effect. A running update, file scan, or sync can compete for storage access. Check whether the difference repeats when the computer is otherwise idle before assuming the drive has a fault.

Large-file speed changes substantially

Large transfers can be affected by the drive's temperature, connection, available space, and the amount of data written in a test. If you are testing an external drive, a loose connection or different USB port can also change the result. Repeat the comparison with the same connection and give the drive time to cool if it feels warm.

The score stays much lower after every restart

A low result across several runs is more useful evidence than one surprising score. Look for ongoing system activity, a power-saving setting, a nearly full drive, or a changed connection. A browser score can reveal a slowdown, but it cannot identify every drive fault or replace a full diagnostic from the drive maker.

How to reduce score changes

1. Keep the test conditions the same. Use the same browser, drive, port, cable, and power source. Disconnect unnecessary external storage and avoid copying large files during the comparison.
2. Wait for startup activity to finish. After a restart, updates, cloud sync, indexing, or security scans may use the drive. Wait until activity settles, then test again. On Windows 11, check Settings › Windows Update for an update that is still installing or waiting for a restart.
3. Use a consistent power mode. Battery-saving modes can reduce performance on some computers. On Windows 11, check Settings › System › Power & battery › Power mode and use the same choice for both tests. On a Mac, check System Settings › Battery and keep the power mode consistent where that option is available.
4. Close apps that use the drive. Pause large downloads, file transfers, backups, and cloud sync while testing. Close other browser tabs and programs you do not need, then repeat the run.
5. Check available space. A drive that is almost full may behave differently from one with plenty of free space. Remove only files you no longer need, or move them to another drive, then compare again.
6. Check the connection. For an external drive, reconnect it firmly and try a direct port on the computer instead of a hub. Keep the same port and cable for each run so the comparison is meaningful.

When to suspect the drive

A score change by itself does not prove that a drive is damaged. Be more concerned if the drive repeatedly disconnects, files fail to open or copy, the computer reports storage errors, or results remain far below the drive's usual performance across several tests with consistent conditions. Back up important files before running more tests if you see errors or disconnections.

If the same problems follow an external drive to another computer, its cable, enclosure, or drive may be failing. For an internal drive, use the computer or drive maker's diagnostic and support process. A browser benchmark measures observed speed, not the drive's complete health.

Why a restart can change a browser test

A restart clears some temporary system state, but it also starts background services and apps again. Before a restart, the computer may have accumulated open programs or pending work. Immediately afterward, it may be busy with updates, scans, or synchronization. Either situation can change how much time the browser gets to run its test.

Storage devices can also behave differently depending on temperature, free space, and recent activity. A browser test measures the result of the whole path through the browser, operating system, connection, and drive. It is best used to compare the same computer under repeatable conditions, not as a precise specification for the drive.