The Full Path of Opening a Website

You type example.com, press Enter, and a page appears in under a second. It feels like a single instant thing — one action, one result. It isn't. Behind that second is a chain of separate steps, each handled by a different part of the system, each one you've already met in the chapters before this one.

This page follows that chain end to end. Nothing here is new; it's the payoff of Part 2 — the moment where DNS, networks, the internet, servers, and databases stop being separate topics and snap together into one journey. By the end you should be able to narrate, in your own words, what happens between the keypress and the page.

Type nameDNS turns example.com into an address

→

Route across the internetpackets hop network to network

→

Server builds the pageback-end code + database

→

Browser renders itresponse returns, page appears

Step 1: You type the name, DNS finds the address

The journey starts the moment you finish typing example.com and press Enter. But example.com is a name built for humans to remember. The computers that move your request around don't use names — they use numeric addresses, the way the postal system uses street addresses rather than the names of the people living there.

So the first thing your browser does is a lookup. It asks DNS — the domain name system, the internet's address book from Chapter 7 — "what is the address for example.com?" DNS answers with the numeric address of the server that holds the site. Only now does your browser know where to send anything.

Step 2: The request travels across the internet

With the address in hand, your browser sends out its request. That request doesn't travel as one solid lump. It's broken into small pieces called packets, each labelled with the destination address, and each finding its own way across the network — the idea from Chapters 5 and 6.

Those packets hop from your home network to your internet provider, then across a chain of other networks, then on toward the building where the server lives. The server itself is just a computer that runs all the time, waiting for requests — possibly thousands of miles from you. The packets arrive there and are reassembled back into your original request.

Step 3: The server builds the page

Now the request has reached the server. What it carries is an HTTP request — the web's standard way of asking for a page, from Chapter 8. In plain terms it says: "please give me the page at this address."

The server doesn't usually have a finished page sitting ready. Instead it runs back-end code — a program living on the server — to build the page for this specific request. That code often needs data: your name, the latest articles, the price of an item. So it asks the database, the organized store of data from earlier in this chapter, and the database hands back exactly what was asked for.

With that data in hand, the back-end code assembles the finished page and hands it to the server to send back. This is the one step where real work happens for your particular visit — everything else is delivery.

Step 4: The response comes back and the browser renders it

The finished page now makes the return trip. It travels back across the internet the same way the request came — split into packets, hopping network to network — until it reaches your browser.

What arrives isn't a picture of a page. It's the raw materials: HTML, the structure of the page; CSS, the styling that says how it should look; and JavaScript, the code that makes it interactive. Your browser takes those three and assembles them into the page you actually see and click. That final assembly step is called rendering.

Picture the whole thing as a relay race. DNS runs the first leg and hands off the address. The internet's routers carry the request to the server. The server, with the database beside it, runs its leg and produces the page. The browser runs the final leg and turns the raw materials into something you can read. No single runner does the whole race — but the baton never stops moving, which is why the finish line arrives in under a second.