AI agents · OpenClaw · self-hosting · automation

Quick Answer

How to Reduce LLM Latency in 2026: 9 Fixes That Work

Published:

The short answer

Latency in an LLM app is mostly the time spent generating output tokens, so the biggest wins come from generating fewer of them and generating them faster. OpenAI’s latency guide puts numbers on it: halve the output and you roughly halve the latency; halve the prompt and you save only 1–5%. In order of payoff, as of October 13, 2026:

#FixTypical effectCost
1Shorter outputs (length limits, terse formats)~linear: −50% tokens ≈ −50% timeFree
2Stream the responseFirst words in well under a secondFree
3Lower reasoning effortRemoves hidden thinking tokensUsually cheaper
4Smaller or faster modelSeveral-fold faster outputUsually cheaper
5Prompt cachingFaster processing of long repeated prefixesCheaper
6Parallel callsTotal time = slowest call, not the sumFree
7Fewer round tripsCombine sequential steps into one callFree
8Fast inference provider~500–3,000 tokens/s on open modelsVaries
9Paid speed tiersUp to 2.5x (Anthropic) or 6x (OpenAI Ultrafast)2x–6x price

Measure the right two numbers

Track time to first token (TTFT) and output tokens per second separately. TTFT is what users feel in chat; tokens per second decides how long a full answer or an agent step takes. A slow TTFT points at queueing, long uncached prompts or reasoning; slow throughput points at model size or provider.

The fixes in detail

1. Generate fewer tokens. Ask for concise answers, return compact JSON with short keys, and set max_tokens. OpenAI’s guide calls output generation “almost always the highest latency step.”

2. Stream. Streaming does not shorten generation, but users start reading at the first token. It is the cheapest perceived-latency fix there is.

3. Lower reasoning effort. Reasoning models think before they answer. Claude Opus 5.5 defaults to medium effort; GPT-6 Sol runs from none to max. For classification, extraction and short replies, the lowest effort level that passes your evals removes most of the delay.

4. Use a smaller model. OpenAI notes that smaller models are usually faster and cheaper and can match larger ones with better prompts, few-shot examples or fine-tuning. Route easy requests to models such as Claude Haiku 5.5 or GPT-6 Luna (both $0.10/$0.50 per million tokens) and reserve frontier models for hard ones.

5. Cache the prompt prefix. Anthropic’s prompt caching lets requests resume from a cached prefix, which “significantly reduces processing time and costs.” Put tools, system prompt and reference documents first and the user’s message last. Our prompt caching explainer covers the pricing.

6. Parallelize. Independent steps — retrieving from three sources, checking three policies — should run at once.

7. Make fewer requests. A chain of five sequential calls pays five round trips and five TTFTs. Where quality allows, ask for several outputs in one structured response.

8. Use a fast provider for open models. Groq serves gpt-oss-120b at about 500 tokens per second for $0.15 input, $0.075 cached and $0.60 output per million tokens, with a 131,072-token context. Cerebras serves the same model at about 3,000 tokens per second for $0.35/$0.75. Compare them in best providers for real-time inference.

9. Pay for speed only where it matters. Anthropic’s fast mode for Claude Opus 5.5 is $8/$40 per million tokens (standard $4/$20) for up to 2.5x speed. OpenAI’s Fast mode costs 2x the standard rate, and Ultrafast 6x — GPT-6 Astra Ultrafast is $60/$300 for up to 300 tokens per second. Full rates are on our current API prices page.

Two more things to check

  • Region. Calling an endpoint on another continent adds a network round trip to every request; pick a region near users, and see EU-hosted options if you also need data residency.
  • Do you need an LLM at all? OpenAI’s last principle is “don’t default to an LLM”: hard-coded responses, cached answers to frequent questions and classic search are faster than any model.

Last verified: October 13, 2026.

Sources