Check small-write response on a home server PC

A compact home server can feel slow even when large files copy quickly. Opening a directory, updating a database, or saving many small files may take longer than expected because these jobs involve lots of small writes rather than one long transfer.

The Storage Test checks large-file speed and small writes in your browser. Use it to get a baseline, then narrow down whether the result points to the storage device, the test conditions, or a different part of the server.

Check small-write response

1. Open the Storage Test on the home server desktop itself. The result reflects the computer running the browser, not another device connecting to its shared folders.
2. Before running it, make sure the server is not busy with a backup, file synchronization, a large download, or another demanding task. Do not run a storage test while the machine is handling work you cannot safely interrupt.
3. Run the test and note the small-write result and the score out of 100. Also note the large-file result so you can compare the two types of work.
4. If the result is unexpected, wait until the computer is idle and run one more test. Keep the browser and power conditions the same so the comparison is useful.

Save the figures and the date as a simple baseline. A future test is more informative when you compare it with this computer's own earlier result, rather than with an unrelated desktop or a score found online.

What the result means

Large-file speed is good, but small writes are much slower

This pattern means the drive can move a continuous stream of data more easily than it handles many separate small operations. Small writes are common when a system updates file metadata, a database changes records, or an application saves many little files. The result can be affected by the storage type, available free space, background work, and the browser's storage environment. It does not prove that the drive is faulty.

Both results are low

The test may be running while another task is using storage, or the browser may be writing to a slower drive than the one that holds your server data. A USB connection, hub, or enclosure can also limit performance. Check which drive holds the browser profile and test again when the computer is quiet.

The result changes a lot between runs

Other work may be competing for the drive, or the system may be doing background maintenance. Some storage also slows during longer writes as its cache fills or its temperature rises. One browser test is a clue, not a diagnosis. Look for a repeatable pattern rather than treating one unusually low result as a failing drive.

The test looks healthy, but the server still feels slow

The storage result does not measure every part of a home server workload. Network sharing, the server application, memory pressure, and a client computer can all add delay. If local actions feel responsive but opening the same files over the network is slow, test the connection and the client separately.

How to improve the result

1. Let current work finish. Pause only nonessential backups, file synchronization, downloads, or indexing, then test again. Avoid stopping a backup or service that is protecting important data or serving other people.
2. Check free space on the system drive. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. A nearly full drive can make normal work harder, but do not delete server files just to improve a benchmark.
3. Check which drive the browser is using. The browser test uses browser-managed storage, which is usually associated with the drive holding the browser profile. That may not be the separate drive or volume that contains your shared folders or database. A good test result therefore does not clear every disk in the server.
4. Restart after pending maintenance. Finish any operating system update or scheduled maintenance, restart the computer when it is safe to do so, and test again after startup settles. On Windows 11, check Settings › Windows Update. On macOS, check System Settings › General › Software Update.
5. Check airflow and power conditions. A compact desktop in a closed cabinet may heat up during sustained work. Make sure its vents are clear and it has room to move air. If you compare results on a laptop, keep it connected to power and use the same power mode for each run.
6. Check the drive with the operating system or its manufacturer. If slow results persist while the computer is idle, use an appropriate drive-health check and review system warnings. Back up important data before further testing if the drive reports errors or disconnects.

When the drive may need attention

A slow small-write result on its own is not enough to call a drive defective. Take it more seriously if performance has fallen sharply from a repeatable baseline and you also see file errors, unexplained disconnects, long pauses, or operating system warnings. Back up essential data first. If the drive reports errors or the problem follows it to another computer, check the warranty and consider replacing it. A browser test cannot repair a failing drive or confirm its remaining life.

What a browser storage test can measure

A browser test can show how browser-managed data behaves on this computer, but it is not a direct measurement of every disk operation performed by your server software. It does not provide a complete native IOPS benchmark, where IOPS means input and output operations per second, and it may not test the volume where your server keeps its files. Browser permissions, the operating system, free space, and other activity can affect the result. For more detail, see why browser storage tests use temporary data.

The test uses temporary browser data. Your existing server files are not the test data, but keep normal backups before troubleshooting any storage problem.