What Happens When You Press Enter
It feels instant. You type an address, hit Enter, and a page appears. But in that half-second, your computer quietly runs a relay race across the world — finding a machine you've never met, agreeing on a private language, asking for a document, and painting it onto your screen. Here's the whole journey, one leg at a time.
First, the browser reads the address
A URL like https://example.com/pricing isn't one thing — it's a set of
instructions. The https part says which language to speak, example.com is
who to talk to, and /pricing is what to ask them for. Your browser splits
the address into these pieces before it does anything else. It also checks its
own cache first: if you visited the page seconds ago, it may already have the
answer and skip most of the trip entirely.
Turning a name into a number with DNS
Computers don't find each other by name; they find each other by number — an IP
address like 93.184.216.34. So the browser's first real task is a lookup:
what number belongs to example.com? This is the job of DNS, the
internet's phone book. Your machine asks a DNS resolver, which, if it doesn't
already know, walks up a chain of servers until one can answer. The result comes
back and gets cached, so the next visit is faster. Without this step, your
request would have a message but no address to send it to.
Opening a connection
Now the browser knows where to send its request, but it still needs a reliable
line to send it over. It opens a TCP connection to the server — a short
back-and-forth handshake where both sides agree they're ready to talk and can
confirm nothing gets lost along the way. If the address started with https,
one more step happens here: a TLS handshake sets up encryption, so
everything that follows is private and can't be read or altered in transit. Only
once the line is open and secured does the real conversation begin.
Asking for the page
With a connection in place, the browser sends an HTTP request — essentially a
politely formatted note that says "GET me the /pricing page," along with
details like which browser you're using and what formats you can accept. The
server reads the note, figures out what you asked for, and sends back an HTTP
response: a status code (the famous 200 OK, or 404 if the page doesn't
exist) plus the actual content — usually an HTML document describing the page.
Building the page you see
The HTML that arrives is just a description, not a finished picture. The browser reads it top to bottom and builds a model of the page's structure. As it reads, it discovers references to other files it still needs — stylesheets that say how things should look, images, and JavaScript that makes the page interactive — and fires off more requests for each. Once enough has arrived, the browser lays everything out, paints the pixels, and runs any scripts. The page you asked for finally appears.
Why it's worth knowing
None of these steps is exotic on its own — a lookup, a handshake, a request, a render — but chaining them together is what makes the web work. Knowing the sequence turns vague problems into specific ones: a "slow site" might be slow DNS, a distant server, a heavy pile of images, or scripts that block the paint. Each stage is a place you can measure and, sometimes, fix.
The takeaway
Typing a URL kicks off a tidy relay: read the address, look up the number, open a secure line, ask for the page, and draw it. It happens thousands of times a day without you noticing — which is the whole point of a system designed to disappear.
This explainer was made with LineLapse — type a topic, get a hand-drawn video. Make your own →