Everyone wants a fast website. Until they have to remove something from it.

Frontend performance in a real-world company isn't just about Lighthouse scores, lazy loading, and smaller bundles. It involves a series of negotiations between development, design, content editors, marketing, and product teams—because every kilobyte, animation, or external script exists for a reason.

Drawing on specific examples from Sazka’s transformation into Allwyn and the ongoing development of the website, we will show what we discovered when the gaming site’s new redesign started crashing on iPhones, why a modern build can’t salvage a poor product decision, and how we distinguish between work that must happen immediately and work that can wait. The goal isn't the fastest blank page; the goal is the fastest version of the product that still fulfills its purpose.