What happens when you type a website address

Less than a second, many steps

Typing a website address and pressing Enter feels like one simple action. Behind the scenes, your device performs a series of carefully coordinated steps with computers that may be on the other side of the planet. Understanding them helps explain why some websites feel instant and others feel slow.

Step 1: DNS finds the address

Computers do not understand names like scaleb.com. They need a numeric IP address. The Domain Name System works like the internet's phone book, translating human friendly names into these addresses.

Your browser first checks its own memory, then your operating system, then your router. If none of them know the answer, a DNS resolver asks the root servers, then the servers for .com and finally the servers responsible for the domain itself. The answer is cached along the way so the next lookup is much faster.

Step 2: opening a connection

With the IP address in hand, your browser opens a connection to the web server. Using TCP, the two computers exchange a short handshake to agree that they are ready to talk. Newer websites often use HTTP/3, which runs over a faster protocol called QUIC and reduces this delay even further.

Step 3: the secure handshake

For any HTTPS website, the next step is a TLS handshake. The server sends its certificate to prove it really is the website you asked for. Your browser checks that the certificate was issued by a trusted authority and has not expired.

Both sides then agree on encryption keys. From this point on, everything sent between you and the website is encrypted, so nobody on the network can read or change it.

Step 4: request and response

Now the browser finally sends an HTTP request asking for the page. The server might return a ready made file from a cache, or it might run code, query a database and build the page on the spot. It replies with a status code such as 200 for success or 404 for not found, along with the HTML.

That HTML usually points to more files: stylesheets, JavaScript, images and fonts. The browser requests all of these as well, often many at the same time.

Step 5: rendering the page

The browser reads the HTML and CSS to build a model of the page, calculates where every element should go and paints the pixels on your screen. JavaScript then runs to make buttons, menus and forms interactive.

• Fast DNS and a CDN shorten the first steps.
• HTTP/2 and HTTP/3 make connections more efficient.
• Smaller files and less JavaScript speed up rendering.

Every step is a chance to be faster

When a website feels slow, the delay can hide in any of these steps. A good development team measures each stage and improves the weakest link, whether that means better hosting, caching, smaller images or lighter code.