April 30, 2026
Loading… drama detected
Show HN: What happens when you load a webpage (Interactive)
This page explains why websites load slowly — and the comments instantly went feral
TLDR: A new interactive page shows, in simple visuals, all the hidden steps between typing a web address and seeing a site appear. Readers split hard: some praised it as an amazing teaching tool, while others blasted it as confusing jargon or even possible AI-made fluff.
A shiny new Show HN project tried to do something weirdly ambitious: show, step by step, what happens after you type a web address and hit enter. The interactive page breaks the journey into seven stages, from your browser checking if it already knows the site to the final moment the page actually appears. The big lesson is deliciously simple: the slowest part is often not “the internet,” but all the stuff your device has to do after the data arrives. In plain English, sending less junk makes sites feel faster.
But on Hacker News, the real fireworks were in the comments. One camp was absolutely smitten, with one user practically proposing marriage to the project, saying it made their elite bookmark list because it explains hard things so clearly “even a 5 yr old” could get it. That is basically a standing ovation in internet-comment language.
The other camp? Not impressed, and not shy about it. One commenter groaned that the whole thing was “jargon acronym soup,” saying it felt made for people who already know everything. Another zeroed in on the phrase “Press Play to scrub” like it was a crime scene, starting a tiny side-quest over whether the word “scrub” was being used wrong. And then came the spiciest accusation of all: AI slop. One skeptic said the design and wording felt suspiciously machine-made and dropped the brutal line, “If you can't be bothered to write it, why should anyone care to read it?” So yes, a page about website loading somehow turned into a referendum on teaching, taste, and whether polished explainers are genius or robot wallpaper.
Key Points
- •The article breaks webpage loading into seven phases and contrasts cold-path versus warm-path request timing.
- •Before network traffic begins, the browser parses the URL and checks connection reuse, HSTS policy, and service worker interception.
- •DNS resolution may be satisfied by multiple cache layers or require a recursive lookup through root, TLD, and authoritative servers.
- •A new TCP connection adds one round trip, while TLS 1.3 adds one round trip or potentially zero with session resumption.
- •The article states that rendering is often the largest time component on modern pages, and reducing bytes sent is the cheapest optimization.