Synology Network Speed Test: Causes of Slow NAS Transfers

What a Synology Network Speed Test Actually Measures

A Synology network speed test may measure different parts of the connection depending on the tool and test location. An internet test measures the path between a client and an external test server, including the ISP, modem, router, and wider network. A local NAS transfer measures the path between the computer, router or switch, Synology NAS, storage volume, and file-sharing protocol. These results should not be expected to match.

For a useful baseline, record download, upload, and latency on a wired client, then compare them with a transfer between that client and the Synology NAS. You can also use Speedtest.im to check the internet connection separately from local NAS performance.

Common Causes of Slow Synology Network Speed

Wi-Fi Signal Quality and Interference

Wi-Fi is a common cause of inconsistent Synology transfer speeds. Distance, walls, neighboring networks, wireless channel congestion, and client power-saving behavior can reduce throughput or increase latency. A wireless link may show a high theoretical rate while delivering much less real-world performance because of protocol overhead and retransmissions.

Gigabit or Multi-Gigabit Link Negotiation Problems

A damaged cable, unsuitable switch port, or faulty adapter can make an Ethernet connection negotiate at 100 Mbps instead of 1 Gbps or higher. This creates a clear speed ceiling that affects both uploads and downloads. Check the negotiated link speed in DSM, on the computer, and on the router or switch rather than relying only on the cable label.

Router, Switch, or VLAN Configuration

Network topology can limit performance when traffic passes through an overloaded router, an older switch, a mesh wireless backhaul, or a misconfigured VLAN. A NAS and client on different network segments may experience additional routing, firewall inspection, or access-control overhead. Testing both devices on the same switch can help determine whether the wider network is responsible.

NAS CPU, Memory, or Background Workloads

The Synology NAS may be busy with indexing, antivirus scanning, snapshots, backups, media conversion, virtual machines, or package updates. These tasks can consume CPU, memory, and system resources while files are being transferred. DSM Resource Monitor can show whether CPU, memory, network, or disk utilization rises during the test.

Hard Drive or Storage Pool Limitations

Storage performance can restrict network speed even when the network link is fast. Fragmented data, heavily used hard drives, RAID calculations, disk health problems, a nearly full volume, or concurrent file operations can reduce sustained read and write rates. Small files are especially affected because each file creates additional metadata and seek activity.

SMB Settings and File Characteristics

SMB encryption, signing, authentication overhead, permissions checks, and protocol compatibility can reduce transfer performance. A folder containing thousands of small files will usually transfer more slowly than one large test file. Comparing a large sequential file with a small-file folder helps separate protocol and storage behavior from raw network throughput.

Client Software and Security Scanning

The computer performing the test can become the bottleneck. Endpoint security software, file indexing, browser-based file managers, outdated network drivers, and slow client storage may reduce measured results. A test from a second wired device can show whether the limitation is specific to the original computer.

How to Diagnose the Limiting Component

1. Separate internet and local testing: Run an external speed test for the ISP connection, then copy files between the client and Synology NAS on the local network.
2. Confirm the physical link: Check that the client, switch, and NAS negotiate at the expected Ethernet speed. Replace suspect cables and test a different port.
3. Use a wired baseline: Disable Wi-Fi on the test client and connect it directly to the same router or switch as the NAS when possible.
4. Test with a large file: Use a single file large enough to produce a sustained transfer. Repeat with a folder of small files to identify storage and metadata overhead.
5. Monitor DSM resources: Watch CPU, memory, disk utilization, volume activity, and network throughput during the transfer.
6. Compare with iperf3: An iperf3 test between a client and the NAS can measure network capacity without depending on disk speed or SMB file operations.

Why Internet Speed and NAS Speed Can Differ

A fast fiber or cable broadband connection does not prove that local NAS transfers will be equally fast. Internet traffic may use a nearby test server and a different route, while NAS traffic depends on the local switch, Wi-Fi conditions, storage system, and file-sharing protocol. The reverse can also occur: a fast local network may coexist with a slower ISP plan or high internet latency.

For meaningful comparisons, keep the test device, connection type, time of day, and test method consistent. Record download, upload, and latency separately instead of treating one speed number as a complete diagnosis.

Practical Ways to Improve Synology Network Speed

• Use wired Ethernet for the NAS and any client that needs consistent transfer performance.
• Replace damaged cables and verify that every network device supports the intended link speed.
• Move the NAS and wireless access point away from interference and improve Wi-Fi coverage where wired access is not practical.
• Connect the NAS and primary client to the same capable switch when the network design allows it.
• Schedule indexing, backups, snapshots, antivirus scans, and other intensive tasks outside transfer windows.
• Review SMB encryption and signing requirements, changing them only when the security impact is understood.
• Keep DSM, network drivers, router firmware, and switch firmware current.
• Check disk health, storage pool status, volume capacity, and abnormal drive activity before changing network hardware.

When a Hardware Upgrade Is Justified

Upgrade the network first when link negotiation, iperf3, and wired tests show that the current Ethernet or switch capacity is the bottleneck. Consider faster NAS interfaces, a compatible switch, or a multi-gigabit adapter only when both the client and the storage system can sustain the additional throughput.

If iperf3 is fast but file transfers remain slow, a network upgrade is unlikely to solve the problem. Investigate disks, RAID behavior, SMB configuration, client storage, CPU usage, and small-file workload characteristics before spending on new equipment.

Recommended Test Sequence

Start with an external internet test, followed by a wired local transfer and a link-speed check. Then run iperf3, monitor DSM resources, and compare large-file and small-file results. This sequence identifies whether the constraint is the ISP, Wi-Fi, Ethernet, network equipment, NAS processing, storage, or the file-sharing workload. Repeat the test after each change so that improvements can be attributed to a specific adjustment.