One Wednesday, I watched a page spin so long I nearly sent a quote to the wrong client

Last Wednesday afternoon, I was in Hangzhou, demoing a quote page to a client. The page kept spinning, so I clicked “Confirm” twice and nearly submitted the order twice. The client wasn’t annoyed—I was the one with sweaty palms. Only later did I realize that slowness, freezing, and misclicks aren’t always just a bad connection; they can also depend on how a web page works.

The browser isn’t a black box—it just hides the complexity

Web Browser Engineering breaks down how browsers work: what the address bar, back button, cache, page rendering, and security boundaries each solve. That doesn’t mean every founder needs to build a browser. It means understanding why a page slows down or submits twice after a customer clicks. My friend A-Zhe, an indie developer in Chengdu, applied this thinking to his booking page: he reduced image sizes, combined scripts, and preserved button states. His customers waited about two seconds less. That wasn’t showing off—it meant one fewer lost consultation.

Replication cost: $0, about 2 hours, basic website-admin experience

I didn’t have to buy a book or hire an engineer. I opened the “page speed” and “preview” tools in the website builder I already use, put my slowest page through a testing tool, and recorded the numbers before and after the changes. Cost: $0. Time: about 2 hours. The technical barrier is knowing where to find “speed testing” or “page settings.” First step: create a test page with no real customer data, then compress the largest image on the homepage.

What I’d choose at each stage

If I were just starting out, I’d first make sure the page doesn’t misbehave and buttons don’t submit twice. I wouldn’t worry about speed testing yet; reliably receiving orders matters more. With 1–2 clients, I’d record one real customer journey every week and find the page where visitors wait longest. If I were scaling up, I’d have a technical teammate review caching, scripts, and the server, rather than spending time manually chasing slow pages. Not everyone needs this setup: if my customers close deals mainly by phone and the page rarely changes, I’d leave it alone and focus on delivery someone is willing to pay for.