How Internet Speed Affects Your Training Apps and Virtual Races

(Many of the links in this article redirect to a specific reviewed product. Your purchase of these products through affiliate links helps to generate commission for Therunningadvisor.com, at no extra cost. Learn more)

You push off the start line of a virtual 5K on Zwift, your avatar surges forward, and then it freezes. The leaderboard stalls. Your competitors ghost ahead while you spin in digital limbo. Your internet plan is 200 Mbps. So what went wrong? The answer has almost nothing to do with how fast your connection downloads data, and everything to do with how quickly it responds. For runners who train with connected tech, understanding this distinction is the difference between a smooth session and a frustrating, performance-wrecking glitch.

Key Takeaway: For runners using GPS sync apps, virtual racing platforms, or live coaching streams, raw download speed is rarely the bottleneck. Latency, the time it takes data to travel back and forth, is what drives real-time performance. A lagging Zwift session or dropped coaching call is almost always a ping problem, not a bandwidth problem. Testing your connection’s responsiveness first, then checking your WiFi signal, will identify and fix most issues runners face.

Why Download Speed Is Not the Whole Story

Most people judge their internet connection by one number: megabits per second. Providers advertise it on billboards. Speed comparison sites lead with it. It feels like the definitive measure of connection quality. But for running apps that need constant, real-time communication, that number is genuinely misleading.

Download speed tells you how fast large files arrive on your device. Streaming a movie in 4K or downloading a software update, sure, that depends on bandwidth. But your GPS watch syncing a run, your avatar racing other athletes on a virtual platform, your coach watching your form over video call, these are fundamentally different tasks. They require the connection to send and receive small packets of data continuously, and they need to do it fast, in both directions.

This is where latency comes in. Latency is the time, measured in milliseconds, that it takes a signal to travel from your device to a server and back again. It is often called “ping.” A connection with 300 Mbps download speed but 120ms of latency will perform worse in a live Zwift race than a 50 Mbps connection with 8ms of latency. The first connection is fast but sluggish to respond. The second is slower in raw throughput but sharp and reactive.

What Latency Actually Does to Your Run

Think of it this way. Your cadence on a treadmill run gets logged by your watch every second. That data has to hit a server, get processed, and come back as a position update on your virtual course. If the round trip takes 10 milliseconds, everything feels real-time. If it takes 150 milliseconds, you start to notice micro-stutters. At 300 milliseconds or more, the experience breaks down completely. Your avatar drifts. Power readings fall out of sync. Other runners on the platform appear to teleport.

For coaching platforms that use live video, latency is even more brutal. A coach watching your running form over a video call needs audio and video to arrive in sync, and they need to give feedback you can act on immediately. A 200ms delay sounds trivial, but during a coaching cue mid-interval, it creates genuine confusion. The ping test measures exactly this, showing your connection’s response time in milliseconds so you know what you are actually working with before you blame the app.

According to research on network latency), the human brain begins to perceive communication delay at around 100 to 150 milliseconds, which explains why even moderate lag feels disruptive during real-time athletic training tools.

Jitter Makes It Worse

Latency has a companion problem that most runners never think about: jitter. Jitter is the variation in latency over time. If your ping bounces between 10ms and 80ms during a session, the connection is inconsistent even if the average looks acceptable. For real-time apps, inconsistency is often more damaging than a steady, higher latency. A Strava live segment feed that works for 20 minutes and then stutters for 30 seconds is more disorienting than one that runs a little slow throughout.

When you run a ping test, look at both the average and the variation. A tight, consistent number indicates a stable connection. A wide spread, even with a low average, signals problems that will show up during the exact moments you need the connection most.

How WiFi Kills a Good Connection

Your ISP may be delivering a perfectly low-latency signal to your home router, and you still end up with a ruined virtual race. The reason is almost always WiFi. Wireless signals are vulnerable to interference from walls, neighboring networks, household appliances, and your router’s own band congestion. A single thick wall between your treadmill and your router can add 30ms of latency. Running on the crowded 2.4 GHz band in a densely packed apartment building is like trying to have a phone call in a room full of people using the same frequency.

The 5 GHz band is faster and less congested, but it has shorter range. Placing your router in the room where you train, or directly connecting your device via ethernet, eliminates most of these variables. Running a WiFi speed test from your training space specifically, not from the room next to your router, gives you an honest picture of what your device is actually receiving at the point of use. Many runners are shocked to discover their connection drops by half or more between the router and the treadmill.

Strava Syncs and Live Leaderboards

Strava’s real-time segments and live leaderboard feeds are less demanding than full virtual racing, but they are not immune to latency problems. When you finish a segment and your watch tries to upload a GPS trace while simultaneously pulling down a leaderboard position, you are making multiple concurrent requests. A congested WiFi band makes this worse. Your router is juggling traffic from your watch, your phone, possibly a TV, a smart speaker, and other devices, all competing for the same wireless channel.

Band steering, which is your router’s ability to automatically assign devices to 2.4 GHz or 5 GHz, does not always make the right call. Manually assigning your training device to 5 GHz and keeping lower-priority devices on 2.4 GHz helps dramatically. Router placement matters too. Routers broadcast signal outward in roughly a sphere, which means placing one on the floor in a corner wastes a significant portion of its coverage upward and into walls.

Virtual Racing Platforms and Their Real Demands

Zwift and similar platforms have published their own minimum requirements, but these numbers are often framed around download speed, which, as we have established, is not the core issue. The platform is rendering a 3D environment, updating athlete positions in real time, and syncing your power or pace data continuously. The position updates and power readings are small packets sent back and forth very frequently. Bandwidth matters less than responsiveness and consistency.

This is also why VPNs can wreak havoc on virtual racing. A VPN routes your traffic through an additional server, adding a hop that increases latency measurably. If you use a VPN for other reasons, disabling it during training sessions on Zwift or similar platforms is worth the effort.

According to the Internet Engineering Task Force standards on real-time protocols, interactive applications like gaming and virtual training are specifically designed to prioritize low latency over high throughput, which is why consumer broadband marketing around speed can give runners a false sense of security.

Diagnosing Your Setup Before Race Day

There is a practical order of operations for diagnosing a struggling training connection. Start with latency. A number below 20ms is excellent for real-time apps. Between 20ms and 50ms is good. Above 100ms and you will feel it during live sessions. Jitter below 5ms is stable. Above 20ms and you will experience the kind of stuttering that breaks coaching calls and freezes virtual competitors.

After latency, check your WiFi signal quality specifically in your training room. If that number is significantly worse than what you measure next to your router, the problem is signal degradation. Solutions include a mesh WiFi node placed closer to your training area, a powerline adapter to run ethernet through your home’s electrical wiring, or a direct ethernet connection from your treadmill PC or tablet to the router.

Fast Connections That Still Frustrate Runners

It is worth naming this directly, because it trips up runners consistently. A 500 Mbps connection with poor router placement, band congestion, and 80ms of latency will perform worse for virtual racing than a 25 Mbps connection with a clean 5 GHz signal, a well-placed router, and 12ms latency. The numbers on your ISP bill do not translate directly into training app performance. The quality of your local network setup has at least as much influence on your experience as the tier of service you pay for.

This is frustrating to hear if you have been paying for premium speeds under the assumption that faster is always better. But it is also genuinely good news, because improving your local setup costs little or nothing. Moving a router, changing a band setting, or using a network cable instead of WiFi are free or inexpensive fixes that can transform a stuttering training session into a clean one.

Run the Tests, Then Fix the Right Thing

The most common mistake runners make is troubleshooting in the wrong order. They restart their router, reinstall the app, check their subscription tier, and contact the app’s support team, all before doing the one thing that would immediately point to the actual problem: measuring their connection.

Two measurements give you the full picture. The first is latency, tested from the device you actually train on, in the room where you actually train. The second is WiFi signal quality from that same location. These two numbers will tell you whether you have a latency problem, a signal problem, both, or neither.

Your Next Session Deserves a Better Connection

Virtual racing and connected training are only going to grow. More runners are tracking power on the treadmill, racing live against athletes across the world, and working with remote coaches over video. The technology is remarkable. The network demands are specific and often misunderstood. Now you know that the quality of your experience is driven far more by ping and signal consistency than by raw speed, you can stop chasing bandwidth tiers and start fixing the right things. Test first, diagnose accurately, and then make targeted improvements. Your next virtual race will thank you.