You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode HTTP: what your browser really asks a website, and the status code that answers first

What happens when you type a web address and press Enter

HTML, CSS and JavaScript: why one web page needs many requests

You open one web page. Your browser then asks the website again and again, for pictures, colors and scripts. Why does one page need so many requests?

  1. 1 One request went out, and one text came back. Yet the page you wait for has a photo of the Moon, colors of its own and a menu that opens when you tap.the one textthat came back?Moona menuthe page you wait for

    One request went out, and one text came back. Yet the page you wait for has a photo of the Moon, colors of its own and a menu that opens when you tap.

  2. 2 Your browser reads the text. Marks in angle brackets say what each part is: h1 for the main title, p for a paragraph. A text written this way is HTML, and it describes the page part by part.<h1>Moon</h1><p>The Moon is the only naturalsatellite of Earth.</p>your browserA title, a paragraph.The photo? The menu?

    Your browser reads the text. Marks in angle brackets say what each part is: h1 for the main title, p for a paragraph. A text written this way is HTML, and it describes the page part by part.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Rendering: how your browser turns HTML and CSS into the page you see

Share this comic

More comics