Good reminder: performance problems often start before your site even begins to load. 🧠 Oleh Khomenko breaks down the hidden delays that eat time between click and first byte – from redirect chains to protocol and caching decisions. A solid read for teams that want faster products, not just prettier dashboards: https://lnkd.in/eyqyU467
How much time does your site waste before it even starts loading? I checked. The answer was embarrassing. I audited a production page that lost 800ms just to a redirect chain – invisible unless you check the waterfall. That's just one of the things hiding before the first byte: 🔁 http → https → www → /en/ – three hops, up to 600ms gone before HTML even starts loading. ⏳ While your server spends 200-500ms generating HTML, the browser just sits idle. 103 Early Hints says "start downloading CSS and fonts now" before the response is ready. ⚡ HTTP/3 (QUIC) merges transport and TLS into a single handshake – 1 round trip instead of 3. On mobile, that alone cuts hundreds of ms. 🤔 no-cache doesn't mean "don't cache." It means "cache it but revalidate every time." The actual "don't cache" is no-store. 💀 Cache-Control: max-age on HTML sounds smart until you deploy. Users get stale HTML pointing to JS/CSS that no longer exist. White screen. The full article walks through the entire chain – from click to first byte – step by step: what the browser does, where time is lost, and how to fix each stage. 👇 Link in the first comment