How to interpret slow random-looking storage writes

A storage test can show fast large-file writes but much slower small writes, or speeds that seem to jump around from one run to the next. That does not automatically mean your drive is failing. Small writes behave differently from copying one large file, and the operating system can affect the result.

The Storage Test measures disk speed for large files and small writes. Use the two results to see whether the slowdown is limited to a particular kind of work, then check the factors that can change the numbers.

Compare large-file and small-write results

1. Open the Storage Test on the computer or device whose storage you want to check.
2. Pause large downloads, file copies, backups, and other tasks that may be using the drive. Keep the device plugged in if it is a laptop.
3. Run the test and note the results for large files and small writes, along with the score out of 100.
4. Run it once more under the same conditions. A similar result is more useful than a single number, especially if the first run was unexpectedly slow.

Compare the two types of write result on the same drive. The score is a summary, not a pass or fail mark, and it does not tell you how much storage space the drive has.

What the result means

Small writes are much slower than large-file writes

This is common. Small writes involve many separate operations instead of one long, continuous transfer. The drive and operating system may need to locate each piece, update file information, and manage other work between writes. Mechanical hard drives are especially affected because their read and write heads must move between locations. A solid-state drive can also be slower on small writes than on large ones.

If you mainly notice delays when opening a folder with many small files, installing software, or saving frequent changes, this difference may explain the symptom. It does not, by itself, show that the drive is damaged.

Large-file writes are slow too

A low result in both categories can point to a broader bottleneck, but it is not a diagnosis. Other programs may be using the drive, an external drive may be connected through a slower port or hub, or the drive may be nearly full. Repeat the test after checking those conditions.

The result changes a lot between runs

Storage speed is not always steady. Background updates, cloud sync, antivirus scans, file indexing, heat, and the drive's own cache can all affect a short test. Some drives accept data quickly at first and slow down after their fast cache fills. Compare repeat runs made with similar power, temperature, free space, and background activity.

The score is low, but the drive seems usable

The score is a compact way to compare test results, not a universal rating for every drive model. Browser tests also run through the browser and operating system, so they are not the same as a specialist drive test that measures a particular random-write pattern or drive specification. Look at the measured write results and the real tasks that feel slow, rather than treating one score as proof of a fault.

How to check for a bottleneck

1. Stop other disk activity. Pause downloads, file transfers, backups, and cloud syncing, then rerun the test. On Windows 11, open Settings › System › Storage to review storage use. On macOS, open System Settings › General › Storage. Avoid deleting files just to improve a score unless you know you no longer need them.
2. Check how full the drive is. Leave free space available, especially on a solid-state drive. A drive with very little free space may have less room for temporary files and its internal management work. Free space will not make every small write fast, but it can remove one possible constraint.
3. Connect an external drive directly. If you are testing a USB drive, try another port and remove the hub or dock temporarily. A USB-C connector does not guarantee a particular transfer speed, and hubs can add a bottleneck. See why external drives slow down through USB hubs if a hub is part of your setup.
4. Repeat the test in a consistent state. Use the same connection, power source, and approximate temperature. Close apps that write files in the background. If the drive is external, do not unplug it while a test or file operation is still running.
5. Compare with the task that feels slow. Copying one large video file is mostly a large-file workload. Installing an app or copying a folder full of tiny documents creates more small operations. A test result may explain why one task is slow without predicting every other task.

When the drive may need attention

A slow small-write result alone is weak evidence of a failing drive. Take it more seriously if the slowdown is new and persistent, or if it comes with file errors, repeated disconnects, freezing during ordinary file access, or files that cannot be read. Back up important files before troubleshooting further.

For an internal drive, check the computer maker's or drive maker's built-in diagnostic guidance. If a diagnostic reports errors, or the drive keeps disconnecting after you have tried a different cable or port, arrange service or replacement. For an external drive, also test another cable and computer before deciding that the drive itself is at fault.

Why small writes look random

Random writes means writing data to many separate locations, rather than filling one continuous stretch of a drive. The Storage Test reports large-file speed and small-write speed, which helps show how the drive handles different kinds of work. Small writes are a useful comparison, but do not assume they represent every random-write benchmark or a fixed number of tiny operations per second.

For a more meaningful comparison, use the same computer, drive connection, and test conditions. A single low result can reflect temporary activity. A repeated slowdown that matches what you experience in everyday tasks is a better reason to investigate.