Some observations and testing suggestions.
Behind the scenes, network devices are often / sometimes busy negotiating with each other over who is who, what they'll do (indications of what services each device is running, etc.), who is the boss (egs.: SMB [Local | Domain] Master Browser) re some priority / protocol(s), and more.
If there is a / are Windows OS device(s) on your network, it / they can tend to bicker a lot over who will be the boss . . . especially when SMB network activity is involved (egs. again: SMB [Local | Domain] Master Browser).
If you do not have any Windows OS devices on your network, then consider NOT enabling SMB/CIFS on your NAS device. In other words, keep the amount of protocols running, to a miniumum of what your Mac OS device(s) need, such as AFP. Also consider not using FTP/SFTP connections to your NAS device. IOW, if you're using only Apple devices, stick with AFP.
I'm looking at the Synology NAS knowledge base, their help article:
Help Articles > Control Panel > File Sharing > File Services > Win/Mac/NFS - DiskStation Manager
There is a lot of good info there.
First, it may help you to Disable Opportunistic Locking. (In Samba language, in the smb.conf file, you'd adjust/create the "oplocks" setting(s).)
If you Disable Opportunistic Locking, then be sure to also disable "Transport encryption mode" --- the Synology NAS KB article states:
Transport encryption mode: When SMB 3 is enabled, Windows File Service will add transport encryption to strengthen file transmission security.
Disable: No transport encryption will be applied.
Auto: Transport encryption will only be applied to clients supporting this feature.
Force: Transport encryption will always be applied. This will cause clients that do not support transport encryption to be unable to use Windows File Service.
Apple's SMB 3 implementation in the later Mac OS (egs. El Capitan) is no doubt for security. But, the two settings, when ENABLED:
Opportunistic Locking
Transport encryption mode
might be causing performance problems. Disabling these two features, would be a temporary fix until Apple and/or NAS developers iron out the difficulties.
There is a third setting in the Synology NAS KB article that you might consider: making the Synology NAS device your network's Local Master Browser. You might test your connection and data backup / copying performance, with that feature enabled / disabled.
The Synology NAS KB article says:
Enable Local Master Browser: When multiple Windows computers exist within the same subnet, they will negotiate and elect one computer as a "local master browser." The local master browser maintains lists of the other computers within the subnet and their shared resources, and shares these lists with the other computers. This option allows the Synology NAS to assume the role of local master browser.
Adding to that:
Note: Enabling this function disables hard disk hibernation and activates the guest account without a password.
Overall, you'd be testing / tuning the NAS device, in order to improve data backup / copying performance, while you accept the risks of testing and any temporary fix.
I'm guessing that Apple "improved" some SMB 3 feature --- yet another security consideration now comes with attendant restrictions --- and that is why the connection and data backup / copying performance has become more troublesome.
Some tips re connecting:
In the Finder, use Command + k keys - to produce a Connect to Server window.
When connecting to an SMB serving NAS device, use its network IP address (make sure that the NAS device has a fixed IP address on your network).
The share on the NAS device - make sure that its name is 8 characters or less, and all capital letters - for example "SHARENAS".
Make sure that your network users who connect to the NAS device, are registered in the NAS device, with usernames that have NO SPACES. For example, if your Mac's user account shortname is "johndoe", then use that and 'as is', meaning all lower-case characters. Do not set up users in the NAS device, such as "John Doe" or "Elizabeth Doe".
The reasons behind all that, is/are, that it helps sometimes to stick with old Samba Server / SMB / NETBIOS conventions.
Now, in the Connect to Server window, let's say your network NAS device's IP address is 192.168.3.2, and its network share is named "SHARENAS" --- type:
smb://192.168.3.2/SHARENAS
and click the Connect button.
Other settings in that Synology NAS KB article . . .
"Veto files" - I'd disable that.
"Apply default UNIX permissions" - I'd disable that, and test.
"Clear SMB cache" - I'd routinely click that, in order to clear caches.
"Enable SMB 2 with Large MTU" - You might not want that. Which reminds me, that elsewhere on your Mac, in System Preferences > Network . . . you can set the MTU value for your network location setup; try 1424 (default has been 1500 - but it can lead to some failures to get complete packets from A to B in a manner of speaking; this setting (value of 1424) has helped with AFP over/thru VPN connections).
"Enable SMB 3" - The Synology NAS KB article states: "SMB 3 supports AES-based file encryption transmission, thus improving the security of peer-to-peer file transfers." You might try testing without that enabled.
-