How the Web Works

What Is a Browser?

A browser is the app you use to navigate the web. Chrome, Safari, Firefox, and Edge are all browsers. Every time you visit a website, watch a YouTube video, or Google something, you're doing it through a browser.

The browser's job is to take an address you type in, go fetch the files that make up that page, and display them as something you can read, click, and interact with. It's part messenger, part translator, part artist.

You open a browser, type youtube.com, and press Enter. Less than a second later, a page full of videos appears. That feels like magic — but it's actually a chain of very specific events, each one faster than you can blink.

Step 1: The Browser Reads the URL

A URL (Uniform Resource Locator) is the address in the bar at the top of your browser. It has a few parts:

https://www.youtube.com/watch?v=abc123
  │        │               │
  │        │               └── the specific page you want
  │        └── the domain name (the website's name)
  └── the protocol (how to talk to the server)

Your browser understands URLs, but the internet does not understand names like youtube.com. The internet understands numbers.

Every device on the internet — every phone, laptop, server, and router — has a unique number called an IP address. It looks like this: 142.250.185.78.

So before anything else, the browser has to translate the name into a number.

Step 2: The DNS Lookup — The Internet's Contacts List

To look up the IP address, your browser asks a special server called a DNS server (Domain Name System).

DNS is like your phone's contacts. You search for "Mom" — the app finds the actual number 604-xxx-xxxx and dials it. You never had to memorise the number; the contacts list did it for you.

DNS lookups happen so fast (a few milliseconds) that you never notice them.

Step 3: The Request — Sending a Letter in Thousands of Pieces

Now the browser knows the IP address. It sends a request — a message that says: "Hello, I'd like your homepage please."

But the internet doesn't send whole messages at once. It breaks every message into tiny chunks called packets.

Imagine you need to mail your friend a 500-page book, but the post office only accepts envelopes with 1 page each. You split the book into 500 numbered envelopes (1/500, 2/500, …) and send them separately. Your friend reassembles them at the other end.

The internet does this with everything — your request, the webpage, the video, all of it.

Step 4: The Journey — Glass Fibres Under the Ocean

Those packets travel through a network of devices called routers. Each router receives a packet and makes a split-second decision: "Which direction brings this closer to its destination?" Then it passes the packet to the next router.

The long-distance links between routers are fibre-optic cables — bundles of glass as thin as a human hair that carry pulses of light. Most of these run underground or along the ocean floor.

Here's a map to see all of the underwater cable maps that connects the world.

Your packets might pass through 15–20 different routers on their way to the server. The whole trip often takes less than 50 milliseconds — about half the time it takes to blink.

Step 5: The Server — A Kitchen That Never Closes

Eventually your packets reach their destination: a server.

A server is just a computer — but one that is:

• On 24 hours a day, 7 days a week
• Powerful enough to handle thousands of requests at once
• Stored in a giant building called a data centre

Analogy: A server is like a restaurant kitchen. Your request is the order ticket. The kitchen prepares the meal — in this case, the HTML, CSS, images, and other files that make up the webpage — and sends it back out.

Step 6: The Response — Packets Coming Home

The server sends its response back the same way your request went out: broken into packets, passed through routers, and reassembled at the other end.

The packets might take a completely different route on the way back — the internet automatically finds the fastest available path. When they all arrive, your computer puts them back in order and you have a complete HTML file.

Step 7: Rendering — The Browser Draws the Page

Now the browser reads the HTML file from top to bottom. As it finds links to images, CSS, and JavaScript, it fires off extra requests for each one. When everything arrives, the browser renders the page — it calculates where every element should go and draws it on your screen.

The Full Journey

You press Enter
       ↓
DNS translates the domain name → IP address
       ↓
Browser sends an HTTP request (split into packets)
       ↓
Packets travel through routers and undersea cables
       ↓
Server receives the request and builds a response
       ↓
Response packets travel back (possibly a different route)
       ↓
Browser reassembles packets into HTML
       ↓
Browser requests CSS, images, JS → renders the page
       ↓
You see a webpage — in under a second

What This Means for You as a Web Developer

Understanding this pipeline makes you a better developer:

• Every file is a request. Each image, font, and JavaScript file your page loads is a separate round-trip to the server. Fewer, smaller files = a faster site.
• Servers can go down. When a website is "unavailable," the server usually isn't responding — like calling a restaurant that's closed. Your request got there; nobody picked up.
• Distance adds time. A server in the same city responds in ~5 ms. A server on the other side of the world might take ~200 ms. This is why large companies like Netflix store copies of popular videos on servers close to their users.
• HTTPS matters. The s in https:// means the packets are encrypted — scrambled so that anyone who intercepts them along the way can't read them. Always use HTTPS for sites that handle user data.

More Fun Facts