What slow random writes feel like in everyday apps

An app may pause while saving a small change, take a while to open a project, or freeze briefly as it updates a list. Large file copies can still look fast. These symptoms can happen when storage struggles with many small writes, but they can also come from the app, a sync service, or other work on your computer.

The Storage Test checks large-file speed and small writes in your browser. Use it to look for a pattern, then compare the result with what your everyday apps are doing.

Test storage and connect the result to the slowdown

1. Open the Storage Test. Run it on the computer and drive where you notice the pauses. If the browser asks for permission to use storage, allow it so the test can run.
2. Wait for other work to finish. Pause large downloads, file copies, backups, and cloud syncing if you can. These tasks compete for storage and can change the result.
3. Check both kinds of results. Look at the small-write result as well as the large-file result. Small writes are closer to the repeated little updates many apps make, while a large-file result is more like copying one continuous file.
4. Repeat the app action. Try the save, project opening, or list update that usually feels slow. Note whether it pauses at the same point, and whether the file is stored locally or in a cloud folder.
5. Run the test again under similar conditions. A repeatable result is more useful than one run taken while the computer is busy. Compare results from the same device and drive, rather than treating the score as a universal rating.

What the result means

Small writes are slow and everyday saves pause

This is consistent with storage taking longer to handle lots of small updates. Apps may save settings, indexes, cache data, or autosave information in small pieces. It is a useful clue, not proof that the drive is failing: available space, background activity, and the app itself can also affect the result.

Large-file speed looks good, but small writes lag

A drive can move one large file quickly yet take longer when it has to handle many separate updates. That can feel like delays when opening a project with many parts or when an app updates a database. A large-file speed alone would not reveal this difference.

Both results are slow

Check whether the test ran while another task was using the drive, and whether the drive is nearly full or connected through a slow port, cable, or hub. If repeated tests stay low under quiet conditions, investigate the drive and connection before assuming an individual app is the cause.

The test looks normal, but one app still pauses

The slowdown may be in that app, its add-ons, a cloud service, or the files it is working with. A browser test cannot recreate every app's workload or measure every kind of random access. Try a different file stored locally, then compare with another app that saves to the same drive.

How to reduce the pauses

1. Let background work finish. Pause large downloads, backups, and cloud sync while testing or working on a project. If the pauses stop when that activity ends, storage contention may be part of the problem.
2. Check available space. A nearly full drive can leave less room for temporary files and routine updates. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. Remove only files you recognize and no longer need.
3. Try a local copy. If the file lives in a shared or cloud-synced folder, copy it to a local folder and repeat the same action. A pause that happens only in the synced copy may involve the network or sync software rather than the storage device alone.
4. Close apps you are not using. Browsers, photo libraries, backup tools, and system updates can write to storage in the background. Close them temporarily, wait a minute, and repeat the test and the app action.
5. Reconnect external storage directly. For an external drive, try another port and a known-good cable. Connect it to the computer rather than through a hub, then test again. A connection problem can limit performance even when the drive itself is capable of more.
6. Restart and retest. A restart can clear a stuck app or background task. Run the Storage Test again before reopening the app that showed the slowdown.
7. Check drive health if the problem persists. Use the diagnostics provided by your computer or drive maker. Back up important files first, especially if the drive disappears, reports errors, makes unusual noises, or causes frequent freezes.

When it may be the drive

A low small-write result by itself does not show that a drive is damaged. The result can vary with the drive type, connection, available space, browser, and background work. Look for a consistent pattern across several quiet test runs, along with real symptoms such as repeated application hangs, failed saves, read errors, or the drive disconnecting.

If the drive reports errors or your files become inaccessible, stop running repeated tests and make a backup of anything you can still read. Replace a failing external drive or ask a repair professional to inspect an internal drive. If the drive is healthy but is an older hard drive, moving the affected apps and files to an SSD can make small, scattered updates feel much quicker.

Why small writes can matter more than a big copy

A large copy mostly moves data in a continuous stream. Random writes are small changes made in different places, so the drive has to handle many separate requests. That pattern appears in ordinary work, but the amount varies by app and task. The Storage Test gives you a way to compare small writes with large-file speed, not a precise prediction of how every program will feel.