How to retest large-file read speed after a browser update

Your large-file read speed changed after your browser updated, and it is hard to tell whether the drive got slower or the test changed. A browser update can affect how a test runs, so one new result is not enough to diagnose your storage.

Use the Storage Test to compare results under repeatable conditions. The steps below help you check whether the difference persists, then narrow down whether it follows the browser, the device, or its current workload.

Retest large-file read speed

1. Open the Storage Test in the browser you updated. Use the large-file read test, and note the result and score.
2. Keep the setup as close as possible to your last test. Use the same computer, drive, browser, and connection. If you tested while plugged in, plug in again.
3. Close extra tabs and apps that are downloading, syncing, or copying files. Wait a minute for activity to settle, then run the test three times.
4. Write down each result rather than relying on the best one. Compare the three readings with your earlier result, and note the browser version if you know it.
5. If the difference remains, run the test in a second browser as a separate check. Treat that as a new comparison, not as a direct before-and-after result.

Browser storage benchmarks can vary between runs. The browser, operating system, background activity, and cached data can all affect a measurement. For more on normal variation, see why storage benchmark results vary between browser runs.

What the result means

The read speed is close to the old result

If repeated readings are similar to your earlier result, the update probably did not cause a lasting change in large-file read performance. A small difference can come from normal test variation. Keep the new readings as a baseline and check again only if you notice a real slowdown in file opening or copying.

The result is consistently lower in the updated browser

If all three readings are noticeably lower, the change is repeatable, but it does not prove the drive is failing. The browser update may have changed how the browser runs the test, or another system condition may have changed at the same time. Compare with another browser, then repeat the test later with the same setup.

The readings swing widely between runs

Large swings usually mean the conditions are not steady enough for a clean comparison. A download, cloud sync, antivirus scan, or another disk-heavy task may be competing for storage or processor time. Close those tasks and try again after activity settles.

Another browser gives a different result

A gap between browsers points toward browser or test behavior, but it does not identify a faulty browser or drive by itself. Different browser engines can handle storage work differently. See why storage results change when you switch browsers, and use the same browser for any direct before-and-after comparison.

Both browsers show a lasting drop

A consistent drop in more than one browser makes a browser-specific change less likely. Check for background activity, power-saving settings, a loose connection, or a change to the drive or cable. A browser test still cannot diagnose the drive's health or prove that it is wearing out.

How to get a cleaner comparison

1. Restart the browser. Close all browser windows, reopen the same browser, and run the test again. This clears a stuck or unusually busy session without changing your system settings.
2. Keep browser conditions consistent. Use the same browser and profile for the before-and-after check. Temporarily turn off extensions that might affect pages or storage, then restore them after testing.
3. Pause other disk activity. Stop large downloads, file copies, backups, and cloud sync while testing. On Windows 11, check Settings › Windows Update for an active download. On macOS, check whether a file transfer or sync is still running before you start.
4. Match the power setting. On Windows 11, open Settings › System › Power & battery › Power mode and use the same mode for each run. On a Mac laptop, open System Settings › Battery and keep Low Power Mode in the same state as before.
5. Check the drive connection. If you are testing an external drive, connect it directly to the computer instead of through a hub. Try another port or cable only after recording a baseline, since changing the connection also changes the test conditions.
6. Restart the computer. If the result remains low across browsers after the quick checks, restart the computer and test again before changing drivers or other system settings.

When the drive may be the problem

A browser test alone cannot establish that a drive is damaged. Look for a wider pattern: everyday file copies are also slower, the drive disconnects, files take unusually long to open, or your operating system reports errors. Back up important files before troubleshooting a drive that behaves erratically.

If an external drive stays slow when connected directly to another port and another computer, the drive, cable, or enclosure may be at fault. If the problem follows the drive and real file transfers are affected, contact the manufacturer while it is under warranty or ask a repair shop to check it. Do not use a low browser score by itself as a reason to replace a drive.

What a browser read test can and cannot show

The Storage Test measures how quickly the browser can read test data through the storage features available to it. It is useful for comparing the same device under similar conditions. It does not report every detail of a drive, test its full health, or guarantee the speed you will get in every app.

A browser update can change the measurement path even when the physical drive has not changed. That is why a repeatable comparison matters more than one unusually high or low number. The test runs in your browser, and its storage results are not a substitute for a drive health diagnostic.