Voice agent latency: how to tell if it’s the model or the network
Summary
A guide on distinguishing whether latency in voice agents stems from the model or the network, helping developers identify bottlenecks.
Similar Articles
6 months running a production voice agent for service businesses. The latency math is way harder than the demos suggest.
After 6 months running a voice AI agent for service businesses, the author reveals that real-world latency is bimodal (median ~800ms, p95 ~2.4s) and this p95 determines user perception. Issues like VAD misfires, function call degradation with long prompts, and TTS quality matter more than LLM choice, with multilingual support adding significant costs.
Your voice agent probably isn't slow because of the LLM.
A developer debunks the common belief that LLM latency is the primary cause of slow voice agents, explaining that delays often stem from earlier stages like audio capture, VAD, and STT. They recommend logging specific latency metrics and testing various STT/TTS providers and orchestration frameworks to diagnose issues.
Scaling voice agents breaks in a different place at each layer — here's the one that usually caps you first
This article discusses the challenges of scaling voice agents, noting that failures occur at different layers, and identifies the most common bottleneck that limits performance first.
Latency matters more than model selection when building AI tutoring systems
A practitioner argues that speech start latency—not model selection—is the critical factor in AI tutoring systems, recommending targets under 1 second for speech start and highlighting streaming TTS as the highest-leverage optimization. The post outlines a full pipeline from ASR through TTS and avatar sync, identifying where latency compounds most.
Our voice agent's p99 was 280ms. Competitor's was 450ms. Users said ours felt slower. We measured why.
A voice agent team found that despite lower end-to-end latency (280ms vs competitor's 450ms), users perceived it as slower due to poor barge-in interrupt rate (380ms vs 60ms). They identified three fixes—memory pinning, VAD threshold tuning, and smaller TTS chunks—that improved barge-in rate from 41% to 89% at 100ms, making users feel it's faster.