Why drive performance changes after a long write session

Your drive starts copying quickly, then slows down after several minutes. Or a storage test gives a different result after you have written a lot of data. This does not always mean the drive is failing. Many drives change speed as their cache fills, they heat up, or the computer handles other work.

Use the Storage Test to compare large-file speed with small-write performance, then check the drive under consistent conditions. The goal is to find out whether the slowdown is repeatable and limited to one drive, or caused by a setting, connection, or background task.

Compare performance before and after writing

1. Open the Storage Test on the computer you want to check. Run it once while the system is idle and note the large-file and small-write results.
2. Write or copy a normal, non-sensitive file to the drive that seems slow. Use a file large enough to keep the transfer going for several minutes, but do not fill the drive just to test it.
3. When the transfer slows or finishes, wait a few minutes and run the Storage Test again. Keep other downloads, backups, and apps that write files paused during both runs.
4. If the problem is on an external drive, repeat a real file copy to that drive using the same cable and port. The browser test is useful for comparing runs on the same computer, but it may not test a particular external drive directly.

Write down the time, drive, connection, and whether the computer was plugged in. A single run is only a snapshot. A repeated pattern is more useful than a one-off score.

What the results mean

Writing is fast at first, then settles at a lower speed

This is common with many solid-state drives. Some use a fast portion of flash memory as a temporary write cache. Once that cache fills, new data may go to slower memory directly, so the transfer rate drops. The lower sustained speed can still be normal for that drive. It is especially noticeable when writing a large amount of data in one session.

Performance improves after the drive sits idle

The drive may have needed time to cool down or finish internal housekeeping. Solid-state drives can reorganize stored data after heavy writes, and some devices reduce speed when hot. A short pause followed by a faster run points to a temporary limit, not proof of damage. See why SSD speed drops during thermal throttling for more on heat-related slowdowns.

Small writes are slow, but large-file speed is steady

Small writes involve many separate operations, so they can behave very differently from one large sequential transfer. File system activity, available free space, and background apps may affect them. A low small-write score by itself does not show that the drive is failing.

Both results stay low or become erratic

Check whether the computer is busy, the drive is nearly full, or an external connection is unstable. If file transfers also pause, disconnect, or produce errors, stop using the drive for important files until you have another copy. A browser benchmark cannot verify every part of a drive or prove that its data is safe.

How to narrow down the cause

1. Let the drive rest, then retest. Stop large copies and give the computer several minutes to settle. Run the same test again without changing the setup. If speed returns, a temporary cache, heat, or background activity is more likely than a permanent fault.
2. Check for other disk activity. On Windows 11, press Ctrl + Shift + Esc to open Task Manager, then look at the Processes list and sort by disk activity. On macOS, open Applications › Utilities › Activity Monitor and inspect the disk activity view. Pause a backup or sync only if you know it is safe to do so.
3. Check free space and power mode. A nearly full drive can have less room for temporary work and internal management. On Windows 11, check Settings › System › Storage and Settings › System › Power & battery › Power mode. On a Mac laptop, check available storage in System Settings › General › Storage and whether System Settings › Battery has Low Power Mode enabled. Compare runs using the same power mode.
4. Test an external drive with a different connection. Connect it directly to another USB port, without a hub, and use the same cable for each comparison. A slow cable, adapter, hub, or port can limit speed even when the drive itself is capable of more.
5. Check for a repeatable drive-specific problem. Test with a second computer or a different drive on the same port. If one drive repeatedly slows, disconnects, or reports file errors while another works normally, back up important data and check the drive maker's support guidance.

When the drive may need service

A drop from an initial burst to a lower steady speed is not enough on its own to diagnose a fault. More concerning signs include repeated read or write errors, files that become unreadable, unexplained disconnects, or severe slowdowns that persist when the drive is cool and idle. Back up anything you still can before running more tests.

If the drive is under warranty, save the test conditions and error messages, then contact the seller or manufacturer. Replace an external cable or enclosure only after testing with a known-good alternative. If a drive contains important files and begins failing, avoid repeated benchmarks and get help with recovery before trying repairs.

Keep at least one separate backup of important files. A speed result describes a moment of performance, not the condition or safety of your data.