Why the remote tap lands late, and which of the five causes is yours

Delay in a remote session is never one thing. Five separate steps sit between your finger and the result appearing, and the fix is different for each — which is why "get better internet" so often changes nothing.

What the delay is made of

Under about 100 ms end to end feels responsive and you stop noticing within a minute. Around 200 ms is workable but visibly delayed. Past 300 ms, precise tapping becomes guesswork because you are aiming at a picture of where things were.

Reading the symptom

Picture is sharp, everything responds late. Network round-trip. Distance and relaying dominate; no setting on either phone recovers it. If the two devices are in different countries, the floor is physical.

Picture goes blocky when anything moves. Bandwidth. The encoder is being asked for more than the uplink can carry and it drops quality to keep up. The sharing phone's upload is the constraint — see what a session costs in data.

Smooth but consistently a beat behind. Buffering and frame rate. A low capture rate adds a fixed delay before a change can even be seen.

Fine, then periodic freezes. Packet loss or Wi-Fi interference rather than latency. These need opposite fixes: latency wants a shorter path, loss wants a more reliable one.

The picture is live but taps do nothing at all. Not latency. The control permission is missing on the other end — see the accessibility permission.

What actually helps

1. Put the sharing phone on good Wi-Fi, close to the router. The upload side is where jitter and loss hurt, and a weak signal costs both latency and battery.
2. Lower the resolution before lowering the frame rate. Halving resolution cuts the data roughly fourfold and stays smooth; halving frame rate makes it feel worse for the same saving.
3. Close what else is uploading on the sharing phone — photo backup especially.
4. Prefer a direct connection to a relayed one. If both sides are on restrictive networks, traffic goes through a server and picks up an extra leg. Switching one side to mobile data or a different Wi-Fi sometimes allows a direct path.
5. Reduce what is moving on screen. A live wallpaper or an animation means constant change to encode and transmit for no informational value.

What no app can fix

Distance is a floor. Light in fibre covers roughly 200 km per millisecond and real routes are longer than straight lines, so a session between continents has a round-trip well over 100 ms before anything is encoded.

And some tasks do not fit a remote session at any latency. Reading a screen, changing a setting, filling a form and finding a menu are all comfortable at 150 ms. Playing a game, drawing, or anything needing hand-eye precision is not, and the answer there is to do it on the device rather than to tune the connection.

More guides