Storage speed test
How fast is your browser's storage?
Writes a file to your browser's own storage on this drive and reads it back, in big blocks and in small random ones, three times. The file is deleted when the test ends.
Not started yet.
Your browser's storage
- Big blocks, writing
- —
- Big blocks, reading
- —
- Small random blocks, writing
- —
- Small random blocks, reading
- —
How this test works
A worker writes a file of the size you choose to the browser's own storage on this drive, in 1 MiB blocks, flushes it and reads it back. Then it writes and reads 4,096 blocks of 4 KiB at random places in a second file. It does all this three times and keeps the median of each figure, then deletes its folder.
How to read the result
The two big-block lines are MB/s, decimal megabytes as drive makers count. The two small random lines add IOPS: how many separate operations the storage answered a second. On most drives the random figures sit far below the sequential ones; that is the shape of normal, not a fault. Reads can look faster than the drive is, because the system keeps recent files in memory.
Common faults
A test that won't start says why: no room for the file, a browser that can't give a page fast access to its storage, or one that refuses it right now, as private windows often do. Figures far below a second run on the same machine usually mean something else was using the drive. Figures far below a native benchmark are expected: the test measures the browser's path, not the drive.
What a browser can't see
A browser can't reach the drive itself, only its own storage on it, through its own layers. The system keeps recent files in memory, which can make reading look faster than the drive is. This isn't the speed on the drive's box.