Drive bottleneck during remote work: how to check

A work laptop can feel slow even when the internet seems fine. Files take a long time to save, apps pause while opening documents, or a cloud sync stalls during a busy workday. The drive may be the bottleneck, but network delays, background activity, or low free space can look similar.

Use the Storage Test to check large-file speed and small writes in your browser. Then compare the result with the tasks that are actually slow, so you can decide whether to look at storage, syncing, or another part of the setup.

Check drive performance

1. Open the Storage Test on the computer you use for work. Close large downloads and file copies first, and pause cloud syncing if you can do so without interrupting important work.
2. Run the test and let it finish. It checks large-file read and write speed, small writes, and provides a score out of 100.
3. Note the results and what the computer was doing. A video call, open browser tabs, antivirus scan, or active sync can affect the test.
4. Repeat once under similar conditions. If the numbers change a lot, close demanding programs and check whether storage activity is still running in the background.
5. Compare the result with a specific task, such as opening a local document or saving a file to the computer. Then try that same task with cloud sync paused, if appropriate.

The test runs in browser-managed storage, not as a direct inspection of the drive hardware. Treat its score as a clue for comparing results on the same computer, not as a universal pass or fail mark.

What the result means

Large-file reads or writes are slow

Large-file performance matters when you copy video, download a large work folder, or save a big export. If those tasks are slow too, storage could be part of the problem. But a slow download can also be caused by the network or the remote server, so compare a local file copy with an online download before deciding.

Small writes are much slower than large-file work

Small writes happen when an application updates many little pieces of data, such as settings, caches, or document changes. A low result may match pauses when opening apps, saving lots of small files, or working in a project with many components. Read more about what slow small-write performance means for daily use.

The results improve after you close programs

Another task may have been competing for storage time. Cloud sync, system updates, backup software, or a browser with many active tabs can make both the test and everyday work slower. Check which process is active before blaming the drive.

The test looks reasonable, but remote files are still slow

A browser storage test does not measure the speed of your company file server or cloud provider. If local files open normally but shared files stall, check the network connection, sync client, or service status. A drive can also be fast enough for this test while an individual app has its own delay.

Repeated results are low or inconsistent

That is a reason to investigate, not proof that the drive is failing. Browser workload, available space, temporary storage limits, heat, and background tasks can all influence a run. Keep the conditions as similar as possible when comparing results.

How to fix a drive bottleneck

1. Close active file tasks. Wait for large copies, downloads, backups, and software updates to finish. If syncing is causing a work slowdown, pause it briefly only when your organization's rules and current files allow it.
2. Check free space. A nearly full drive can leave less room for temporary files and work in progress. In Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. Remove only files you recognize, and keep a backup before deleting work data.
3. Find the busy process. On Windows 11, open Task Manager with Ctrl + Shift + Esc and review the Processes list for high disk activity. On macOS, open Activity Monitor from Applications › Utilities and select the Disk view. If a backup, update, or sync is responsible, let it finish or adjust its schedule.
4. Separate local and online work. Save a test document locally, then compare saving it to a shared folder. If the local save is quick but the shared save stalls, check Wi-Fi or Ethernet and the sync service rather than replacing the drive.
5. Restart after updates finish. A pending update or stuck background task can keep the drive busy. Restart the computer after saving your work, then repeat the test before opening your usual workload.
6. Ask IT before changing managed settings. Work devices may use required encryption, backup, endpoint protection, or sync policies. Ask your administrator before disabling or changing those services.

When it may be a hardware problem

Suspect the drive more strongly if local files repeatedly take a long time to open or save, the computer freezes during simple file operations, or the same problem continues after a restart with background tasks idle. Clicking or grinding sounds from a mechanical hard drive are another warning sign. Solid-state drives are usually silent, so silence does not prove they are healthy.

Back up important files before running more tests if you notice repeated errors, missing files, or sudden worsening. A browser test cannot read drive health records or diagnose internal faults. Contact your device maker or workplace IT team for a proper health check. If the drive is failing, replacing it is safer than relying on repeated benchmark runs.

Why remote work can make a drive seem slow

Remote work often combines several kinds of activity: a browser call, shared documents, local apps, and background synchronization. A file can be written to the local drive and then uploaded, so a delay may come from storage, the network, or both. Try to compare like with like: a local file copy tests a different path than saving into a shared cloud folder.

Browser storage tests also use temporary data and cannot inspect every drive feature or certify that hardware is healthy. Use the result alongside real tasks and repeated observations, rather than treating one score as a diagnosis.