Pull up a website – any website – and something quietly extraordinary happens before the first pixel appears. Most people assume the internet just… sends your request somewhere and gets an answer back. One message out, one message in. Clean. Simple. Not even slightly true.
Closer to a Magic Trick
What actually happens is closer to a magic trick. Your phone takes whatever you asked for, chops it into dozens of small numbered parcels, and fires them off into the internet to find their own way to the other end. Not together. Separately. Each one potentially bouncing off different servers, crossing different countries, taking entirely different paths. One packet might swing through Frankfurt. Another might go via Amsterdam. A third might nip round by New York because that route happened to be faster that particular second. They travel as strangers and arrive as a document.

Reassembly at the Far End
The reassembly at the far end is the part that should honestly seem weirder than it does. Each packet carries a sequence number – a little tag that says "I'm piece 14 of 47," for instance – so the receiving machine can collect them as they trickle in and arrange them back into the correct order, regardless of which one turned up first. It's not magic. Just accountancy. Very fast, very patient accountancy.
What If One Goes Missing?
But what if one goes missing? This happens more than you'd think. A packet gets delayed, dropped by a busy router, lost somewhere in a cable under the Atlantic. The receiving machine waits, notices the gap in the sequence, and sends a quiet message back: "Oi. I'm missing number 23. Send it again." The other end does, and the assembled document fills in its hole.
This is roughly half of what TCP – the Transmission Control Protocol – does. It's the part of the internet that worries. The handshake at the very start of a connection (your device says hello, the server says hello back, your device confirms it heard the hello) is TCP making absolutely sure both parties are present and paying attention before any of the interesting stuff begins.
For something closer to this explained in its own distinctive way, The Longest Game Of Chinese Whispers In The World is worth a few minutes of your time.
Why the internet does not keep a line open
The older way of carrying a conversation was circuit switching, which is how traditional telephone calls worked. The network reserved one continuous path from end to end for the whole call, whether anyone was speaking or not. Packet switching throws that idea out. Nothing is reserved. Each parcel, usually no more than a few thousand bytes, is handed from router to router, and each router picks the next hop based on what the network looks like at that moment, steering round links that are busy or broken.

Every one of the dozen or more routers along the way only sees the individual packets of a message, with the address on the front of each packet determining where the packet is sent. The packet switching method was conceived in the early 1960s by Paul Baran, a staff member at the RAND Corporation in the United States, who wanted a communications network that could survive severe damage. Independently, a researcher at Britain’s National Physical Laboratory, Donald Davies, had arrived at the same method and coined the term packet. Today, no single organisation is responsible for the routing of Internet communications. Rather, all machines on the Internet use an agreed set of rules for routing information, known as TCP/IP.

Why does a single page load make many requests?
The genuinely strange thing to sit with is scale. A single webpage can involve dozens of separate servers – one for the text, one for each image, one for the adverts, one for the fonts – which means you're running hundreds of simultaneous little conversations. All chopped into packets. All negotiating their own routes. All reassembling quietly in parallel. Your phone is managing the equivalent of a very complicated postal system, entirely invisibly, in the time it takes you to blink.
Nobody designed this to seem magical. It was designed to be – to survive outages, reroute around damage, keep going when pieces of the network disappeared. The magic is just what that looks like when you finally notice it.
Questions this raises
- What is a DNS lookup?
- What slows down page loading most?
- How can a site load faster?




