How to Run a Speed Test on a Synology NAS and Diagnose Slow Results

Running a speed test directly on a Synology NAS can show whether your broadband connection performs differently from a laptop or phone. This guide explains practical ways to test through Container Manager, Docker, or an SSH-based command-line tool, then analyzes common causes of inconsistent download, upload, and latency results. It covers NAS hardware load, container configuration, Ethernet links, router paths, Wi-Fi limitations, test-server selection, and ISP congestion. By comparing repeatable tests from the NAS and another wired device, you can determine where the bottleneck is and choose an appropriate optimization.

Published 2026-11-21 Last updated 2026-11-21 Category: Guides

What a Speed Test on a Synology NAS Actually Measures

A speed test run on a Synology NAS measures the connection between the NAS and a selected test server. It is useful for checking the broadband path used by services such as backups, remote access, media uploads, and cloud synchronization. The result includes download speed, upload speed, and latency, but it does not automatically measure the speed between the NAS and every client on your local network.

If the NAS is connected by Ethernet to the router, the result can provide a clearer view of the ISP, modem, router, and WAN path than a Wi-Fi test. However, the NAS CPU, storage activity, container settings, and network interface can also affect the result.

How to Run a Speed Test on Synology NAS

Use Container Manager or Docker

On DSM versions that provide Container Manager, open the package and search its registry for a maintained speed-test image. Review the image documentation, supported CPU architecture, update history, and required network mode before creating the container. Run the test from the container terminal or from the web interface provided by that image. Synology NAS models may use Intel, AMD, or ARM processors, so an image that works on one model may not work on another.

A browser-based option such as OpenSpeedTest can be hosted in a container, but the browser used to open the test still affects the measurement. For a NAS-side result, use the container's own command or interface where available, rather than assuming that a test opened on a laptop represents the NAS connection.

Use an SSH Command-Line Tool

Enable SSH only when needed, connect with an administrator account, and use a command-line speed-test tool that supports the NAS architecture and DSM environment. The official Ookla Speedtest CLI is one option, although package availability and installation steps vary by Synology model and DSM release. Verify the package source and license before installing third-party software.

Run several tests at different times and record the selected server, latency, download speed, upload speed, and whether the NAS was busy. A single result is not enough to identify a network fault.

Common Cause: NAS CPU or Storage Workload

A speed test can be slower when the NAS is processing video, indexing files, running a backup, rebuilding RAID, synchronizing cloud data, or hosting several containers. Encryption and compression can also consume CPU resources. This commonly produces lower upload speed or unstable results while the NAS is under load, even though another wired device reaches the expected broadband rate.

Check Resource Monitor during the test. Compare CPU utilization, memory pressure, disk activity, and network throughput. Repeat the test when scheduled tasks and heavy file transfers are stopped. If performance improves only when the NAS is idle, the limiting factor is local resource contention rather than the ISP alone.

Common Cause: Container Image, Network Mode, or Architecture

Different speed-test containers use different runtimes, libraries, and server-selection methods. An image built for another CPU architecture may run through emulation or may perform poorly. A container using a restricted bridge network can also behave differently from a process using the host network. Outdated images may contain inefficient dependencies or fail to support newer test protocols.

Check the container logs, confirm that the image supports the NAS processor, and compare host-network and bridge-network behavior only when the image documentation permits it. Keep one known-good test method for comparison instead of switching between many unverified images.

Common Cause: Ethernet Link Negotiation or Cabling

The NAS may be connected at 100 Mbps rather than 1 Gbps or faster because of a damaged cable, a limited switch port, an old router port, or incorrect negotiation. This creates a clear ceiling: a 100 Mbps link cannot deliver a full gigabit broadband result, regardless of the ISP plan.

Inspect the link speed shown by DSM, the router, or the managed switch. Use a suitable Ethernet cable, connect the NAS directly to a gigabit or multi-gigabit port when possible, and test without unnecessary powerline adapters. Also check whether the NAS model, switch, and router support the same link speed.

Common Cause: Router, Modem, or Network Path Processing

Routers can reduce speed when hardware acceleration is disabled or when features such as traffic inspection, parental controls, VPN routing, QoS, or bandwidth limits process every packet. A modem-router combination may also handle upload traffic differently from download traffic. Double NAT can add complexity, although it does not always reduce raw speed by itself.

Compare the NAS result with a wired computer connected to the same router. Review router CPU usage, QoS rules, VPN settings, and port negotiation. If every wired device shows the same limitation, investigate the router, modem, ONT, or ISP connection before changing NAS settings.

Common Cause: Wi-Fi Is Being Mistaken for NAS Performance

A Wi-Fi speed test from a phone or laptop measures a wireless link that is affected by distance, interference, channel width, client hardware, and neighboring networks. It is not a reliable baseline for a NAS connected by Ethernet. Conversely, if the NAS is connected through Wi-Fi or a wireless bridge, its result may reflect signal quality rather than the broadband service.

Use a wired computer and the wired NAS for a fair comparison. Test near the access point and on the appropriate 5 GHz or 6 GHz band when supported. Do not diagnose the ISP from a single Wi-Fi result.

Common Cause: Test Server Selection and ISP Congestion

Speed-test results depend on the distance, capacity, and current load of the selected server. An automatically selected server may be geographically close but temporarily busy. ISP congestion can also appear during evening hours, while international routing or peering problems may affect only certain destinations.

Repeat tests against more than one nearby server and compare results during off-peak and peak periods. A consistently low result across local servers points toward the access connection or local equipment. A low result on only one server suggests server load or routing rather than a general broadband failure.

How to Judge the Results and Improve Accuracy

  1. Establish a wired baseline: Test a computer and the Synology NAS through Ethernet on the same router.
  2. Control NAS workload: Pause backups, indexing, media processing, cloud synchronization, and large file transfers.
  3. Repeat the test: Run at least three tests at similar times and record latency, download, upload, and server details.
  4. Check the link: Confirm the NAS and switch negotiate at the expected Ethernet speed.
  5. Compare test methods: Use one maintained CLI or container method and avoid comparing incompatible tools without noting their differences.
  6. Isolate the fault: If the wired computer and NAS are both slow, inspect the router, modem, fiber or cable connection, and ISP. If only the NAS is slow, focus on its workload, architecture, container, or interface.

For a reliable diagnosis, treat the NAS test as one measurement in a controlled comparison. A lower result does not automatically mean the Synology NAS or ISP is defective; the pattern across devices, servers, times, and workloads identifies the likely cause.