Typing a URL and pressing enter feels instant, but it sets off a short, specific chain of events. Understanding that chain once makes a lot of later topics — caching, performance, why a site is slow, what a CDN does — much easier to reason about.
1. Turning a name into an address
A URL like example.com isn't something computers can route traffic to directly — first, a system called DNS translates that human-readable name into a numeric address that identifies a specific server.
2. Opening a connection
Your browser opens a connection to that address, and — on virtually every modern site — negotiates an encrypted channel so that what's sent back and forth can't be easily read or tampered with along the way.
3. Requesting, and receiving, a document
The browser sends a request for a specific page, and the server responds with an HTML document: the raw structure and content of the page, before any styling or interactivity has been applied.
4. Building the page from the document
As the browser reads the HTML, it builds an internal model of the page's structure, and fetches any additional files that HTML references — CSS for styling, JavaScript for behavior, images and fonts. Each of these can also trigger the DNS-and-connection steps above if it lives on a different server.
5. Painting pixels, then handing over control
Once it has the structure and styling, the browser calculates the layout and paints it to the screen. JavaScript then runs, ready to respond to clicks, scrolling, and other interaction from that point on.
None of these steps require special tools to observe — a browser's built-in developer tools show DNS timing, connection setup, and every file requested, in the network panel. Watching a page you use daily load, step by step, is a quick way to make this concrete instead of abstract.