# Latency (/academy/latency)



Latency is the beat between the click and the thing happening.

Not how much data you get. Not how fat the pipe is. The wait. Measured in milliseconds. Felt in the shoulders.

You tap Submit. Nothing. Then the page. That hang is travel time, queue time, think time. A [trace](/academy/trace) says which. Users will not read your essay about cold starts. They will bounce.

**Travel vs work**

Distance is physics. A [server](/academy/server) on another continent is a longer walk than one next door. A [CDN](/academy/cdn) or [edge](/academy/edge) shortens the walk. A [cache](/academy/cache) skips a trip you already paid for.

Work is the pause you chose. A model doing [inference](/academy/inference) takes a beat because it is actually thinking. That beat is not a [bug](/academy/bug). An extra `await` on a [database](/academy/database) you did not need *is*.

You can have a wide pipe and still feel laggy. Bandwidth is how much. Latency is how long until anything moves.

**What a hackathon audience feels**

The first byte has to move or the UI has to lie kindly — a skeleton, a "working" state, anything but a frozen button. [Async](/academy/async) keeps the room alive while the kitchen cooks. Sync stands at the stove and ignores the door.

When an [agent](/academy/agent) "optimizes," ask it to name the wait: network, query, or model. "Make it faster" is weather. "The Polar hop is 1.2s" is a Saturday.

**What this unlocks**

"It's slow" becomes a place. Shrink the walk, skip a trip, or put a face on the pause. Instant is a feeling. Latency is the clock behind it.