Step 1 — Your Browser Parses the Address
The moment you press Enter, your browser reads the URL you typed and breaks it into parts. A URL like https://www.example.com/about tells the browser three things: the protocol to use (https), the domain name (www.example.com), and the specific path or page you want (/about).
The browser checks whether it already has a cached version of the page — a saved copy from a previous visit. If a fresh, valid copy exists locally, it may display that immediately. If not, it moves to the next step. To understand more about caching and when it helps or hinders you, see what happens when you clear your cache.
Step 2 — The DNS Lookup Finds the Server's Address
Domain names like example.com are designed for humans. Computers, however, communicate using numerical IP addresses (e.g., 93.184.216.34). To bridge this gap, your browser contacts a DNS (Domain Name System) resolver — typically operated by your internet service provider — which looks up the IP address associated with the domain you typed.
This lookup often completes in tens of milliseconds. Your device may also have recently resolved the same domain and stored the answer locally in a DNS cache, skipping the external query entirely.
DNS Caching Speeds Things Up
Your device, your router, and your internet service provider all keep temporary records of recent DNS lookups. When you visit a site you've accessed before, the IP address may already be stored nearby — skipping the full lookup process entirely. This is one reason returning to a familiar site often feels faster than visiting a new one.
Our field guide to IP addresses, DNS, and domain names explains these concepts in greater depth if you want to go further.
Step 3 — Establishing a Connection With the Server
Now that your browser knows the server's IP address, it opens a connection using a process called the TCP handshake. Your browser sends a signal to the server, the server acknowledges it, and your browser confirms — three brief exchanges that establish a reliable line of communication before any data is sent.
If the site uses HTTPS (indicated by the padlock icon in your browser), an additional step called the TLS handshake takes place. This negotiates encryption so that everything exchanged between your browser and the server is scrambled and unreadable to anyone who might intercept it.
~50ms
Typical DNS resolution time
DNS lookups commonly complete in 20–120 milliseconds depending on resolver proximity and caching, according to general internet performance research.
40%
Users who abandon a site after 3 seconds
Studies on web performance have consistently found that a significant share of visitors leave pages that take more than three seconds to load.
Step 4 — The Server Responds and the Page Loads
Your browser sends an HTTP request asking the server for the specific page. The server processes this, then sends back an HTTP response containing the page's HTML — the structural skeleton of the webpage.
The browser reads that HTML and discovers it needs additional resources: CSS files (which control visual styling), JavaScript files (which power interactivity), and images. It fetches each of these, often in parallel, assembling everything into the visual page you see.
How fast all of this feels depends partly on your connection's latency — the time it takes for signals to travel back and forth. Download speed, upload speed, and latency each play a distinct role in the experience, and understanding the difference can help you diagnose slow browsing.
Look for the Padlock Before Sharing Data
Before entering a password, payment detail, or any personal information on a website, check that the address begins with https:// and that your browser shows a padlock icon. The 'S' stands for Secure, meaning the TLS encryption layer is active. Avoid submitting sensitive information on sites that show a warning or use plain http://.
Frequently Asked Questions
The core network steps — DNS lookup, server connection, and initial response — typically complete in well under a second on a reliable connection. The total page load time depends on the site's complexity, your connection speed, and how many resources the page needs to fetch.
DNS (Domain Name System) translates the human-readable domain name you type — like example.com — into a numerical IP address that computers use to locate the correct server. Think of it as looking up a name in a contact list to find the phone number. See our <a href="/internet-mobile/internet-basics/ip-addresses-dns-and-domain-names-a-field-guide-for-non-techies">plain-English guide to DNS and IP addresses</a> for more detail.
HTTPS encrypts the data traveling between your browser and the web server, making it much harder for third parties to intercept or tamper with the information. Sites without HTTPS send data in plain text, which poses a privacy risk — especially on public Wi-Fi.
A browser cache is a local storage area on your device where your browser saves copies of images, scripts, and other files from websites you've visited. On repeat visits, your browser can load those saved files instead of downloading them again, making pages appear faster.
Yes — the speed and reliability of each step depends on your connection. Fiber connections generally complete these steps faster than cable or DSL, largely due to lower latency and higher bandwidth. See our overview of <a href="/internet-mobile/internet-basics/broadband-fiber-cable-and-dsl-the-differences-that-actually-change-your-experience">broadband, fiber, cable, and DSL</a> for more context.
The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.