Learn: the web, apps and software projects, explained /
How the web works, end to end
You type an address, press Enter, and a page appears. In the second between, your browser looks up a name in a global directory, opens an encrypted channel to a machine that may be continents away, requests a document, and assembles it into what you see. Here's that journey, step by step — because every decision about your website's speed and reliability lives somewhere along it.
Step one: finding the server (DNS)
The browser first turns the domain into an IP address using DNS — a distributed directory that works like a chain of referrals: from the root, to the registry for .com, to your domain's own name servers, each answer cached along the way so repeat lookups cost almost nothing.
This is why DNS configuration is real engineering: a wrong record makes a site unreachable for some visitors and fine for others, which is the most confusing outage a business can have.
Step two: the secure connection (TLS)
With the address known, the browser and server perform a TLS handshake: they agree on encryption, the server presents its certificate, and the browser verifies it against authorities it trusts. Only then does any real data flow — encrypted both ways.
Then comes the actual conversation, in HTTP: the browser requests a path, the server answers with a status code and the document. Modern versions (HTTP/2, HTTP/3) multiplex many requests over one connection, which is a big part of why well-built sites feel instant.
Step three: rendering — and why speed is engineering
The first document is just the skeleton. The browser parses it, discovers styles, scripts, fonts, and images, fetches those too, and assembles the page — re-doing work whenever something arrives late or shifts the layout.
Every performance decision we make lives on this path: pages prerendered so the first response already contains real content, assets served from CDN locations near the visitor, fonts self-hosted, images sized honestly. Speed isn't a plugin — it's respecting each step of this journey.
FAQ
Why do some sites load instantly and others crawl?
The fast ones do less on the critical path: content already in the first response, fewer and smaller assets, servers and CDNs close to the visitor. The slow ones make the browser discover and wait for chains of resources. It's engineering, not luck.
What's a CDN and do I need one?
A content delivery network keeps copies of your site's assets in locations around the world so each visitor downloads from somewhere nearby. For any audience beyond one city, it's one of the cheapest meaningful speed and resilience upgrades.
Does any of this affect my search ranking?
Directly. Search engines measure real-user speed (Core Web Vitals) and use it in ranking, and slow pages lose visitors before they ever convert. The engineering in this journey is the technical half of SEO.