DNSHTTPTLSBrowser Renderingmiddle level

From URL to Rendered Page

the question

What happens after you type a URL into a browser and press Enter? Walk me through the request from the address bar to pixels on the screen.

what they're testing: The interviewer is probing whether you can connect networking, server behavior, and browser rendering into one accurate end-to-end model.

a strong answer

Pressing Enter starts a navigation. The browser parses the URL and checks whether a usable cached response can satisfy it. If the network is needed, the browser asks a DNS resolver for the hostname's address records. A recursive resolver may answer from cache or query other DNS servers.

The browser may reuse an existing connection or establish a new one. HTTP/1.1 and HTTP/2 usually run over TCP, with TLS added for HTTPS. HTTP/3 runs over QUIC, which uses UDP and incorporates TLS 1.3. The browser sends an HTTP request with a method, target, and fields. Intermediaries may route it before an origin server returns a status, fields, and a body. A redirect causes another request.

When the response is HTML, the browser parses incoming bytes into the DOM and discovers external stylesheets, scripts, images, and fonts. Those resources may require more requests. CSS is parsed into the CSSOM; the browser uses it with the DOM to build a render tree, performs layout, and paints. A classic script without async or defer can pause HTML parsing, while stylesheets can delay rendering. JavaScript and late-arriving resources can keep changing the page after the first paint.

Where people slip

the tempting wrong answer, and what's actually true

DNS sends the full URL to the web server and returns the page.
DNS resolves the hostname to resource records such as IP addresses; HTTP is what requests the page.
The browser always opens a TCP connection before sending an HTTPS request.
The browser can reuse an existing connection. For a new connection, HTTP/1.1 and HTTP/2 usually use TCP, while HTTP/3 uses QUIC over UDP.
A single HTTP request downloads the complete page and all of its assets.
The HTML can contain inline content, but external stylesheets, scripts, images, and fonts need their own fetches; those fetches may be satisfied from cache.
The browser waits for every asset to finish downloading before it renders anything.
The browser can parse and render incrementally before every asset arrives. Stylesheets can delay rendering, and classic scripts without `async` or `defer` can pause HTML parsing.

If they push further

Where can caching short-circuit this flow?

Separate DNS caching, connection reuse, and HTTP response caching, then explain that freshness rules determine whether a cached response is reused or revalidated.

What does the TLS handshake establish?

For normal HTTPS, explain how the client verifies the server's identity, the peers negotiate cryptographic parameters, and the handshake derives traffic keys that protect application data.

Where would you look if the page feels slow?

Break the latency into DNS, connection setup, server response time, content transfer, and rendering, then use browser network and performance traces to locate the delay.

Sources

Now answer it yourself.

Reading a strong answer is easy. Producing one under pressure is the skill the interview tests. Gapmap grades your answer against the same bar an interviewer would.

was this useful?

beta

The interviewer part is in the works.

The diagnostic, personal maps, and AI mock interviews are being finished right now. The notes stay free either way. Leave an email and you'll get the first-cohort invite, plus a month of Pro when it opens.