How to establish a disk speed baseline after setup

After setting up a computer, you may want to know whether its storage is performing normally before adding more software or files. A baseline gives you a record to compare against later, such as after an update, a repair, or a change to your setup.

The Storage Test measures large-file read and write speeds, small writes, and a score. Run it under steady conditions and save the results. Treat them as a comparison point for this computer, not as a universal pass or fail grade.

Record your first disk speed baseline

1. Open the Storage Test on the computer you want to check. Use the same browser and computer for future comparisons.
2. Finish initial setup first. Let operating system updates and large file transfers complete, then restart if an update requests it. Connect a laptop to power and close applications that are installing, downloading, or copying files.
3. Run the test and let it finish. Note the large-file read speed, large-file write speed, small-write result, and score. Do not compare just the score while ignoring the individual results.
4. Run the test two more times under the same conditions. Write down all three results so you can see how much they vary. Avoid running other heavy tasks during the tests.
5. Save the date, computer, browser, power state, and results in a note. If you know whether the test is checking internal storage or a connected drive, record that too. Do not assume a browser test lets you select a physical drive unless the tool clearly offers that option.

Browser storage permissions can affect what a disk test is able to access. If the test asks for permission or its results seem unexpected, see What browser storage permissions mean for a disk test.

What the results mean

Large-file read and write speeds

These results show how quickly the test can read and write larger blocks of data. They are useful for comparing the same computer over time, but they are not guaranteed to match a drive maker's advertised speed. Advertised figures are often measured with different hardware, software, and test conditions.

Small writes are much slower than large-file results

This can be normal. Many small writes involve more separate operations than writing one large block, so the results can look very different. Keep the small-write result in its own column instead of treating it as a failed version of the large-file result.

The score changes between runs

A small change does not automatically mean the drive is getting worse. Background updates, file syncing, power settings, browser conditions, and other activity can affect a run. Use the three results to understand your normal variation, and compare later tests with the same method.

The test cannot access storage or does not complete

This points to an access or browser limitation, not proof that the physical drive is faulty. Check the browser's prompt and permissions, then try again in a supported, up-to-date browser. The browser test does not provide a complete diagnosis of drive health or detect every hardware fault.

How to make future comparisons fair

1. Wait until setup activity has stopped. Updates, app installations, indexing, and cloud sync can use storage in the background. Let them finish before recording a baseline or comparing against one.
2. Use the same power state. Test a laptop while plugged in, or use the same battery condition each time. On Windows 11, check Settings › System › Power & battery for its power mode. On macOS, check System Settings › Battery and keep Low Power Mode consistent between runs.
3. Keep the computer idle during the test. Close large downloads, file copies, game updates, and backup jobs. A video playing or a few open documents matter less than another task reading or writing many files.
4. Keep the browser and permissions consistent. Use the same browser when possible. Private browsing, managed browser settings, or changed storage permissions can alter what the test can access. Do not clear browser data just to make a result look cleaner.
5. Compare a group of runs, not one number. Use the middle result from three runs as a simple reference, and keep the other two to show the spread. If a later result is much lower, repeat the same three-run process before drawing a conclusion.

When a low result needs follow-up

A low browser result by itself does not prove that a drive is damaged. First repeat the test under the same conditions and check whether the computer was busy or using a different power mode. If the drive also disappears, reports errors, or makes unusual noises, back up important files before troubleshooting further. A browser speed test cannot confirm that stored data is safe.

If the same problem continues across repeated checks, use the computer maker's storage diagnostics or ask a repair professional to check the drive. For a new computer still under its return period or warranty, keep your notes and contact the seller or manufacturer before attempting repairs.

What a browser baseline can and cannot show

The Storage Test is useful for repeatable comparisons, but a browser does not have the same access as a dedicated drive diagnostic. The test's results reflect the storage the browser can use and the conditions during that run. They do not identify every physical drive characteristic, confirm drive health, or guarantee the exact speed of future file copies.

Use this baseline as a reference for the same computer and test setup. If you change the drive, browser, operating system, or storage permissions, record a new baseline rather than treating the new result as a direct continuation of the old one.