Network Performance Concepts — Bandwidth, Latency and Throughput. Interactive infographic.

Network Performance Concepts

Three ideas that confuse everyone. One toilet that doesn't.

Bandwidth, Latency & Throughput: What's the Difference?

Play each animation in order — ① then ② then ③ — to build understanding one step at a time.

Play each concept in order
Toilet schematic ▲ Latency ■ Bandwidth (pipe width) ● Throughput
①Latency
Waiting time before anything arrives. Like the pause before the flush.
②Bandwidth
Max data the link carries at once. Like the drain width.
③Throughput
Real data delivered after slowdowns. Always ≤ bandwidth.

The analogy

Build the picture
Toilet analogy ① Latency ② Bandwidth ③ Throughput

① Latency ▲

Push the handle — nothing moves yet. That pause is latency. Waiting time, not speed.

In networks: time before the first bit arrives (ms). A bigger pipe won't fix this.

② Bandwidth ■

Wider drain = more flows at once. Narrow pipe = slow drain, however hard you flush.

In networks: max data the link carries (bits/sec). The ceiling, not a guarantee.

③ Throughput ●

How much actually clears before backing up. Even the widest drain delivers less on a bad day.

In networks: real data delivered. Slowed by errors and re-sent packets. Always ≤ bandwidth.

The network reality

See it in action
① Latency — the delay before anything starts
Before any data flows, client and server complete a three-step handshake:
  1. SYN — Client sends "I want to connect" to the server.
  2. SYN-ACK — Server replies "OK — I'm ready" back to the client.
  3. ACK — Client confirms "Let's go!" — connection established.

Every one of those trips takes time. That accumulated wait is latency. A wider pipe can't speed this up.

Latency zone — TCP three-way handshake every trip takes time Client Server ① "I want to connect" ② "OK — I'm ready" ③ "Let's go!" ✓ Now data can finally flow
ⓘ
SYN — client initiates
connection request
ⓘ
SYN-ACK — server
acknowledges & confirms
ⓘ
ACK — client confirms.
Handshake complete.
② Bandwidth — the width of the road
The animation shows a full-duplex connection — two lanes running simultaneously:
  1. Top lane (→) — Data packets traveling from client to server. This is your download or upload payload.
  2. Bottom lane (←) — ACK packets (acknowledgments) returning from server to client, confirming each packet was received.

Bandwidth is the total capacity of the pipe — both lanes combined. It's the ceiling, not a guarantee. Having a 1 Gbps link doesn't mean you're always delivering 1 Gbps.

Bandwidth zone ← max capacity (bits/sec) → Client Server data packets → ← receipts (ACKs)
③ Throughput — what actually gets through
Each bar shows the actual data delivered in a given moment. Notice two things:
  1. The bars never reach the ceiling. The dashed blue line is your bandwidth — the maximum possible. Throughput always falls short because of packet loss, retransmissions, congestion, and protocol overhead.
  2. The bars vary. Throughput fluctuates constantly. A network with 100 Mbps bandwidth might only deliver 60–80 Mbps in practice — and less when traffic spikes.

Throughput is the number that actually matters for user experience. Bandwidth is what you pay for. Throughput is what you get.

Throughput zone high low bandwidth ceiling over time →

① Latency ▲

Three messages fly back and forth before a single byte of data flows — that round trip is latency.

Like the pause before the flush. RTT = Round Trip Time.

② Bandwidth ■

Two lanes run at once — data going out, ACKs coming back. Both directions: full-duplex.

Like drain width — the ceiling, not the guarantee.

③ Throughput ●

The bars never reach the ceiling. Traffic jams and re-sent data always cut into delivery.

Like what actually clears the bowl — always less than the pipe could carry.