Exploring the Hidden Journey: How Your Computer Accesses a Website

Exploring the Hidden Journey: How Your Computer Accesses a Website
Photo by Matt Howard / Unsplash

When you type a URL in your browser and hit enter, a remarkable chain of events begins. It's not just about a website magically appearing on your screen — behind the scenes, there's a fascinating journey your data takes, passing through multiple layers of technology, all happening within fractions of a second. If you’ve used How Did I Get Here? to visualize this process, you already have an idea of the complexity. Let's dive deeper and break it down in a simple way, touching on some additional points you may not have considered yet.

The First Step: DNS Lookup

When you enter a website's URL, like example.com, your browser doesn’t immediately know where to find it. It first needs to translate that human-readable domain into an IP address, a unique string of numbers that represents the server where the website lives. This is where the DNS (Domain Name System) comes in.

Think of DNS as the phonebook of the internet. Your computer asks a DNS server, "Where is example.com?" The server responds with the IP address, allowing your browser to locate the website’s server.

Key Point: Without DNS, you'd have to memorize the IP address of every site you visit — an impossible task for most of us.

The TCP Handshake

Once your browser has the IP address, it establishes a connection with the website’s server. This involves something called a TCP (Transmission Control Protocol) handshake, a three-step process:

  1. Your computer sends a request to the server.
  2. The server acknowledges that request and responds.
  3. Your computer acknowledges the response, and the connection is established.

This handshake ensures that both your computer and the server are ready to communicate and exchange data reliably.

Secure Connections: HTTPS and SSL/TLS

If you’re accessing a site via HTTPS (which is standard for most modern websites), an additional security layer comes into play: SSL/TLS encryption. This ensures that the data exchanged between your browser and the server is encrypted, protecting it from eavesdroppers or attackers.

When you see that little padlock icon in your browser, it's a signal that your connection is secure, thanks to the SSL/TLS protocol. Behind the scenes, this adds a few more steps to the process, as your browser and the server agree on encryption keys to use.

Requesting the Webpage

Now that the connection is established, your browser sends a GET request to the server, asking for the content of the webpage. The server then processes this request and starts sending data back to your browser. This is where things get exciting.

Web servers don’t just send everything at once. The content is often broken up into multiple files — HTML, CSS, JavaScript, and images — which are sent over piece by piece. This is why, if you’re on a slow connection, some parts of a website might load before others.

Rendering the Page

Once the browser receives the data, it doesn’t just display it as raw code. It has to render the HTML, CSS, and JavaScript into a human-readable webpage. The HTML provides the structure, the CSS handles the style, and the JavaScript makes it interactive.

Your browser performs a ton of work here — it builds a DOM (Document Object Model) tree from the HTML, applies the CSS rules, and runs the JavaScript code. This is what turns a plain text file into the polished website you see.

Caching and Content Delivery Networks (CDNs)

Have you ever noticed that websites sometimes load faster the second time you visit them? That’s thanks to caching. Your browser stores copies of parts of the website (like images or CSS files) on your computer, so it doesn’t have to download them again next time.

Additionally, many websites use Content Delivery Networks (CDNs), which are servers located around the world that store copies of website content. When you access a website, the CDN delivers the data from the server closest to you, speeding up the process.

Additional Layers: Firewalls and Load Balancers

Behind the scenes, websites often rely on firewalls to protect against malicious traffic and load balancers to distribute incoming requests across multiple servers, ensuring that no single server gets overwhelmed. These layers are invisible to the end user, but they play a crucial role in keeping websites secure and functional, especially when handling large amounts of traffic.

The Journey Ends — Or Does It?

Once your browser has all the data and has rendered the webpage, you can start interacting with it. But the journey doesn’t end there. Every click, form submission, or new page you visit starts this process all over again, albeit with some steps optimized, such as caching.

So next time you open a website, remember the intricate dance happening behind the scenes. From DNS lookups to TCP handshakes, encryption protocols, and server responses, your data embarks on a lightning-fast journey across the internet, all in the blink of an eye.

Missing Piece: Many times we overlook latency — the time it takes for your data to travel to the server and back. Factors like physical distance between you and the server, the quality of your internet connection, and network congestion can impact this. For global websites, using CDNs helps reduce this latency by serving content from the closest server.

In conclusion, what seems like a simple action — typing in a web address and hitting enter — is actually a highly complex and coordinated process involving multiple technologies. Understanding these layers not only gives you more insight into the web but also helps you appreciate the invisible machinery that powers your everyday browsing.

Interesting right? Try How Did I Get Here? below.

How Did I Get Here?
A cool-as-shit dynamic traceroute powered by custom software, married with an informative article about how the BGP routing protocol works and guides the shape of the Internet.

Support Us

Subscribe to Buka Corner

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
[email protected]
Subscribe