🚀 The Simple Version
Your browser asks the internet's phonebook (DNS) for the address of the website, knocks on that address's door, and asks for the page. The website hands back HTML, CSS, and JavaScript, and your browser assembles it into what you see.
Step 1: DNS Lookup
You typed "google.com" — but computers talk in numbers (IP addresses), not names. DNS (Domain Name System) is the phonebook that converts "google.com" into something like 142.250..194.68.
Step 2: The Handshake
Your browser opens a connection to that IP address using TCP, and if it's HTTPS (the lock icon), it also does a quick security handshake to agree on encryption — so nobody snooping on the network can read your data.
Step 3: The Request
Your browser sends an HTTP request: basically "GET me the homepage." The server processes it — maybe querying a database, running some logic — and sends back a response: status code + HTML.
Step 4: Rendering
The browser reads the HTML top to bottom, fetches any CSS/JS/images it references, and paints pixels on your screen. JavaScript can then keep updating the page without a full reload — which is how modern apps feel instant.
Why Knowing This Helps You Debug
Next time something "doesn't load," you can actually narrow it down: Is DNS failing? Is the server down? Is the request timing out? Is it a rendering/JS bug? That mental checklist alone will save you hours of random Googling.