Web Performance
8 posts tagged #web-performance
8 posts on Web Performance, spread across Production AI Engineering (1) — most read: “Debug HTTP/3 QUIC in Production: 8-Step Playbook” and “Next.js App Router vs Pages Router 2026: Which to Use?”.
Frontend and Mobile Debug HTTP/3 QUIC in Production: 8-Step Playbook
A Wireshark-free workflow to prove HTTP/3 is actually negotiated, diagnose silent fallback to HTTP/2, and measure real perf impact using DevTools, curl, and logs.
Frontend and Mobile Next.js App Router vs Pages Router 2026: Which to Use?
I'd pick the App Router for any greenfield production app in 2026 — its RSC model cuts client JS meaningfully. I'd stick with Pages Router only if I'm maintaining 50k+ lines of existing code and can't justify a migration sprint.
Frontend and Mobile TanStack Start vs Next.js: Server Components Compared
TanStack Start and Next.js both support React Server Components, but their philosophies couldn't be more different. Here's which one to pick for your next project.
Technology Hotwire vs Next.js: Can Server HTML End SPA Bloat?
I built the same app with Hotwire and Next.js. The JavaScript payload difference was staggering — and it changed how I think about frontend architecture defaults.
Cloud and DevOps Bunny vs Cloudflare in 2026: Why Developers Are Switching
Cloudflare's free tier is generous, but it comes with strings. Here's why indie developers and startups are switching to Bunny.net for predictable pricing, real support, and fewer existential risks.
Frontend and Mobile Native Browser APIs That Replace JavaScript Libraries
9 native browser APIs now handle transitions, popovers, i18n, and more — here's why your JavaScript dependencies are becoming dead weight.
Frontend and Mobile CSS DOOM: How CSS 3D Transforms Render DOOM Without WebGL
A technical breakdown of how CSS perspective, preserve-3d, and clever DOM manipulation can render a DOOM-style 3D world — no canvas, no WebGL, just divs.
Frontend and Mobile JavaScript Bloat: 3 Architectural Root Causes and Fixes
Most JavaScript bloat advice stops at tree-shaking and code-splitting. The real problem is architectural: client-side rendering, zombie polyfills, and third-party script sprawl are the three pillars you need to tear down.
Keep exploring
Close to this topic, not on this page.
