Blog

Small-write response changed after a browser update?

Find out whether a browser update changed the test conditions or revealed a storage slowdown, and compare small-write results fairly on the same computer.

Michael ReedHardware tests 4 min read

Your computer may feel the same, but the Storage Test shows a different small-write result after your browser updates. That does not automatically mean your drive has slowed down. The browser, background activity, power settings, and normal run-to-run variation can all affect a browser-based storage test.

Use the Storage Test to compare results under controlled conditions. This guide explains what a changed score can tell you, how to repeat the test fairly, and when a change may point to a storage problem.

Compare small-write results fairly

  1. Open the Storage Test in the browser you updated. Keep the computer plugged in if it is a laptop, and close file transfers or other tasks that use the drive.
  2. Run the test and note the small-write result, the large-file result, and the overall score. Also note the browser and version shown in its About page, plus whether the computer is plugged in or running on battery.
  3. Run the test two more times under the same conditions. Compare the middle result, not just the highest or lowest one. If the three runs differ widely, the test conditions may not be steady enough for a useful comparison.
  4. Check whether the browser updated recently, and whether the operating system or another app changed at the same time. A browser update can alter how browser storage work is scheduled, so compare only runs made in the same browser, profile, and computer setup.
  5. If you want a second reference, run the test in another browser. Treat that as a separate comparison, not a direct before-and-after result. Browser changes can affect storage test results.

What the result means

Small writes changed, but large-file speed stayed similar

This can happen when the two test types respond differently to browser scheduling, background tasks, or the storage device's handling of many small operations. Small writes are short operations, so their response can vary more than large sequential transfers. A difference in one test run is not enough to diagnose a failing drive.

Both small writes and large-file results changed

Look for a broader change in conditions, such as a power mode switch, an active download, a cloud sync, low free space, or another program using the drive. Repeat the test after the computer is idle. If results remain consistently lower in the same setup, check whether the change affects everyday tasks too.

Results vary widely between runs

The browser test is seeing inconsistent conditions, or the drive's performance varies under the current workload. Close demanding apps, wait for updates and file copies to finish, then test again. Browser storage results can vary between runs for reasons unrelated to a hardware failure, as explained in why storage benchmarks vary between browser runs.

How to get a steadier comparison

  1. Restart the browser. Close it fully, reopen the same profile, and run the test with only the test page open. This clears some temporary browser activity without changing the drive.
  2. Let background work finish. Pause file copies, downloads, cloud backups, game updates, and large exports. Wait a few minutes after they finish before testing again.
  3. Keep power conditions consistent. On Windows 11, check Settings › System › Power & battery › Power mode and use the same mode for each run. On a Mac laptop, check System Settings › Battery › Low Power Mode and keep it in the same state. Do not compare a plugged-in run with a battery-powered run as if the conditions matched.
  4. Check free space. If the drive is nearly full, clear space using the operating system's usual storage tools, then repeat the test. Avoid deleting files just to chase a score if the computer is working normally.
  5. Use the same browser profile. A private window, a different browser, or a profile with different extensions and privacy settings may behave differently. Keep those factors the same when comparing runs.

When the drive may be the problem

A browser score alone cannot confirm that a drive is damaged. Take the result more seriously if the slowdown repeats across several tests and you also notice files taking longer to open or save, frequent stalls, copying errors, or operating-system warnings. Back up important files before troubleshooting further. Use the computer's built-in drive health checks or contact the device maker or a repair shop if you see warnings or repeated errors.

If only the browser score changed after an update and your usual work still feels normal, do not assume the drive is failing. A browser storage test uses temporary data and cannot reproduce every normal file operation or give a complete drive-health diagnosis. Learn more about why browser storage tests use temporary data.