Why Websites Keep Downloading the Same JavaScript

Open any modern website and check the network tab. You’ll see dozens of JavaScript files loading: React, a date library, a UI framework, web fonts, analytics scripts. Navigate to another site and the same thing happens again with many of the same packages. Your browser downloads React from scratch, even though it grabbed the exact same version thirty seconds ago on a different domain.

This is one of the web’s biggest hidden costs, and the numbers are striking.

The scale of redundant downloads

According to HTTP Archive’s 2025 Web Almanac, the median desktop page now transfers 2.2 MB of JavaScript. For the top 1,000 sites, that figure climbs to 3.4 MB. A significant portion of that payload consists of libraries that appear across thousands of websites: React (used on over 40% of the top 10,000 sites per W3Techs), jQuery (still present on 77%), and common utility libraries like Lodash and Moment.

Standard HTTP caching helps within a single site, but it doesn’t share resources across origins. Visit ten React sites and your browser downloads React ten times. Multiply that across fonts, polyfills, and CSS frameworks, and a typical browsing session wastes hundreds of megabytes on files the browser has already seen.

As web performance researcher Tammy Everts has pointed out, “We’ve optimized individual page loads extensively, but we’ve barely touched the redundancy between sites. That’s where the real waste lives.”

What this costs in practice

The cost isn’t just bandwidth. Every redundant download means additional DNS lookups, TLS handshakes, and parsing time. On mobile connections, where latency is higher and bandwidth is metered, the impact compounds. Google’s research shows that 53% of mobile users abandon a page that takes longer than three seconds to load. Redundant JavaScript is one of the biggest contributors to that delay.

At the infrastructure level, CDN providers serve petabytes of the same library files every day. That’s server capacity, network transit, and energy consumption spent delivering identical bytes to billions of browsers worldwide.

How Native URLs address this

Utopian Browser introduces Native URLs, a URL scheme that resolves common packages from the browser’s local store instead of the network. Instead of fetching https://cdn.jsdelivr.net/[email protected]/umd/react.production.min.js, a site can reference native:cdn/[email protected]/umd/react.production.min.js and get the same code instantly, with zero network overhead.

The mechanism is straightforward: Utopian ships with a store of widely-used JavaScript packages and Google Fonts. When a site uses a native:esm/, native:cdn/, or native:font/ URL, the browser resolves it locally. If the package is in the store, no network request is made. The developer changes one line of code, and every user with the browser benefits.

We’re still early. The store covers a curated set of the most common packages, and we’re expanding it based on real-world usage data. The savings depend on how many of a site’s dependencies happen to be in the store, but for sites that lean on popular frameworks and fonts, the reduction in transfer size is substantial.

Why this matters beyond speed

There’s a broader point worth making. The web was designed for a world where bandwidth was the constraint and compute was expensive. Today, the opposite is true for most of the developed world: devices are powerful but networks are shared, metered, and often unreliable.

But for a large portion of the planet, bandwidth is still the bottleneck. Over a billion people access the internet on connections where every kilobyte counts. Eliminating redundant downloads isn’t just a performance optimization for fast connections, it’s the difference between a page that loads and one that doesn’t.

And there’s a more speculative angle: the same architecture that works for bandwidth-constrained environments on Earth works even better in scenarios with extreme latency. Satellite internet, remote research stations, or someday, networks between planets. When you minimize what needs to travel over the wire, you make the web work in places it was never designed for.