Google's 'Never-Slow Mode' Prototype Aimed to Police Web Bloat

Google engineers once envisioned a version of Chrome that refused to let websites degrade the user experience. In 2019, the company proposed an experimental feature known as "Never-Slow Mode," a radical approach to browser performance that would have shifted the burden of speed from the user's hardware to the website's developers.

The feature was introduced via a Chromium Gerrit change (commit 1265506) and could be activated using the flag `--enable-features=NeverSlowMode`. Rather than simply attempting to render every asset a site requested, Never-Slow Mode was designed to enforce strict performance budgets. The browser would have automatically blocked stylesheets, fonts, images, and scripts that exceeded predefined size limits to ensure the interface remained responsive. According to Android Police, these proposed limits included a maximum size of 1MiB per image, a total image budget of 2MiB, and a total script budget of 500KiB.

The War on Web Bloat

This proposal arrived as web applications became increasingly "heavy," often bogged down by bloated assets and overly complex scripts. For years, the industry standard has been for browsers to do their best to handle whatever a developer sends their way, regardless of how inefficient the code is. Never-Slow Mode was conceptualized as a hard ceiling on resource consumption, effectively forcing developers to optimize their sites if they wanted their content to actually appear for users.

A Shift in Browser Philosophy

The significance of the proposal lay in its philosophy: the browser would move from a passive renderer to an active police officer of site performance. Had it been implemented, it could have fundamentally changed the incentives of web development, prioritizing a lean, performance-first approach. However, this efficiency came with a significant trade-off. Google ultimately decided not to ship the feature to the general public due to concerns that such aggressive blocking would break the visual and functional integrity of many modern websites, rendering them unusable.

The Legacy of the Prototype

While Never-Slow Mode never reached the stable release of Chrome, it highlights the ongoing tension between rich web functionality and raw speed. The project remains a point of interest for performance advocates who argue that the modern web has become too bloated. For now, the responsibility for speed remains with the developer's discretion rather than a browser-enforced mandate, leaving users to deal with the load times of unoptimized sites.