A Remote Desktop session that lags, stutters or smears when you scroll is frustrating, and for traders it can be costly. RDP speed depends on three things: the network path between you and the server, the client settings, and the server’s resources. Work through them in that order.

1. Measure the network first

From your computer:

ping -n 30 your-server-ip
pathping your-server-ip

(On macOS or Linux, use ping and mtr.) See ping, traceroute and mtr.

Round-trip latency RDP experience
< 50 ms Feels local
50–120 ms Fine for most work
120–200 ms Noticeable typing and scrolling lag
> 200 ms or packet loss Frustrating; fix the route or location

Packet loss hurts more than latency. Even 1–2% causes stutter.

If latency is high, a closer VPS location helps more than any setting. For users in mainland China, routes such as CN2 GIA (Tokyo) or CN2+BGP (Hong Kong) make a large difference. See choosing a VPS location, Japan VPS, and Hong Kong VPS. Network test IPs are listed on each region’s VPS page, so you can test before you buy.

2. Tune the client

Windows Remote Desktop Connection (mstsc) → Show Options:

  • Display: a lower resolution, and colour depth “High Color (16 bit)” on slow links.
  • Experience: choose the connection speed manually (for example “Low-speed broadband”), and untick desktop background, font smoothing, desktop composition, window drag contents, menu and window animation, and visual styles.
  • Local resources: don’t redirect printers, drives or devices you don’t need.
  • Persistent bitmap caching: keep it on.

The same options exist in the macOS Windows App and mobile clients. See RDP from a Mac.

Multiple monitors and 4K displays multiply the data sent. Use one monitor, or a lower scaling, on weak links.

3. Make sure UDP transport works

Modern RDP uses UDP (port 3389/udp by default) alongside TCP, for better performance over lossy or high-latency links. Make sure UDP is allowed in Windows Firewall, and in any network firewall:

Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Select-Object DisplayName, Enabled

If you changed the RDP port, open the new port for both TCP and UDP. See change the RDP port.

In the session, the connection-quality icon shows whether UDP is in use.

4. Server-side tweaks

  • Turn off visual effects: System Properties → Advanced → Performance → “Adjust for best performance”.
  • Set a plain desktop background.
  • Close or disable unnecessary startup apps and tray tools.
  • Keep graphics simple in trading terminals (fewer charts and indicators redrawing constantly).

5. Check the server’s resources

If the network is fine, but the session is still slow, the server may be overloaded:

  • Task Manager → Performance: CPU near 100%, or memory nearly full?
  • Windows Update or Defender scans running?
  • Too little RAM for Windows plus your apps (plan 4 GB+ for comfortable desktop use).

See Windows Server performance tuning and when to upgrade your VPS.

6. Black screens and freezes

A black screen or frozen session is usually a different problem (display driver, session state, or a hung process). See RDP black screen fix.

Quick reference

Cause Fix
High latency Closer location / better route
Packet loss Different network or route; test with mtr
Heavy visuals Lower colour depth, disable effects
UDP blocked Allow 3389/udp (or your custom port)
Server overloaded Check Task Manager; tune or upgrade

Related: Windows VPS trading latency and RDP connection errors.

  • RDP
  • Windows Server
  • Performance