Speed & Delay

Two complaints, one word. "The internet is slow — my movie keeps buffering." "The internet is slow — my game reacts late." Same word, slow; two completely different diseases. This finale hands you the two numbers that tell them apart — and with them, the ability to diagnose half of all household internet grief from the couch.

Bandwidth: the width of the road

Bandwidth is how much data can flow per second — how many packets fit through the pipe at once. Picture a road: bandwidth is the number of lanes. Six lanes move more parcels per minute than one lane, no matter how the trucks are driven.

You've seen its units on every internet ad: Mbps, megabits per second — millions of last unit's bits, each second. (Say it "megabits." And yes, bits, not the "bytes" file sizes use — a byte is eight bits, a gap salespeople rarely rush to clarify.) A hundred Mbps moves a phone-photo's worth of bits in well under a second; a 4K movie stream wants a steady 25 or so all to itself.

Bandwidth problems look like starvation at volume: buffering wheels mid-movie, downloads crawling, everything worsening the moment a second TV lights up. The road has too few lanes for the evening's trucks.

Latency: the length of the road

Latency is how long one trip takes — one packet, you to the server, measured in milliseconds (ms). Same road picture: latency is the road's length. And here's the sentence to tattoo somewhere: adding lanes does not shorten the road. A thousand trucks can depart per minute and the first one still takes an hour to arrive if the destination is an hour away.

Latency is ruled by distance (a server across an ocean is dozens of milliseconds away at best — light itself needs the time), by every router stop en route, and — the one you control — by a struggling Wi-Fi link re-sending packets through walls, which taxes every single trip.

Latency problems look like lag at moments: the video call where you talk over each other, the game where your perfectly aimed move lands late, the page that pauses oddly before anything appears. Small parcels, arriving tardy.

Reading the symptoms like a pro

Now run the clinic:

• Movie buffers, downloads crawl, worse when the household piles on → bandwidth. More lanes help: a better plan, or fewer simultaneous streams.
• Game laggy, calls awkward — while a movie in the next room streams flawlessly → latency. More lanes would change nothing (the movie's fine because buffering hides latency and games can't). Shorten the road: wire the console, pick the nearer server, free the struggling Wi-Fi.
• Everything bad, always → both, and lesson 3's three tariffs (distance, walls, shared air) are the first suspects before any phone call to the provider.

That's the whole unit in your hands now: bits on carriers, chopped into packets, delivered locally by the clerk, sent worldwide through the door — and two numbers governing how it all feels. The Wires, complete.

What we glossed over is the label on every parcel: that "destination address" doing all the quiet work. What is an address, who issues yours, and how does a parcel cross twenty networks to a machine it's never met? Unit 2 unfolds the map. See you there.