The Evolution of the Web and the Weight of Images

The first web page in history, published by Tim Berners-Lee in August 1991 from CERN, didn't contain a single image. It was plain text with underlined links, explaining what this project called the "World Wide Web" was. Thirty-odd years later, an average e-commerce product page loads more than two megabytes in images alone. This is the story of how we got from one to the other — and of why, for anyone running a website today, image weight remains the single variable most likely to wreck a site's speed.

1991-1995: a web built for 2,400-baud modems

The first graphical browsers — Mosaic in 1993, then Netscape Navigator in 1994 — did let you embed images, but the technical context imposed brutal discipline. A typical home modem in 1994 transmitted at 14.4 or 28.8 kbps. A single 100 KB JPG — tiny by today's standards — could take nearly a minute to load at that speed. The result: websites of the era used images sparingly, almost always as 256-color GIFs (lighter than a JPG for simple graphics), and any real photograph was cropped and aggressively compressed. The "pixelated" look we now associate with the '90s wasn't a design choice — it was the only option bandwidth allowed.

1995-2005: broadband arrives, and images stop being a luxury

The arrival of DSL and cable internet in homes changed the rules. By the early 2000s, an average home connection already handled hundreds of kbps or more, and websites started being treated as visual catalogs, not just linked documents. Amazon, eBay, and the first online stores quickly understood that a product photo sold better than a description — and pages began filling up with images without anyone worrying too much about their weight, because broadband seemed to solve everything. That optimism created a habit that's still hard to shake: uploading the photo exactly as it comes out of the camera or phone, uncompressed, because "there's no dial-up to worry about anymore."

2007-2015: mobile changes everything (again)

The iPhone, in 2007, and the wave of smartphones that followed, revived the same problem from the '90s but in reverse: connections became limited again (3G, mobile data with per-megabyte charges) right when websites had grown accustomed to weighing several megabytes on fixed broadband. The industry's response was responsive design (the term was coined by Ethan Marcotte in 2010) — the same website adapting to any screen — and, more slowly, the idea of serving images at different sizes depending on the device, instead of sending the same desktop photo to a mobile screen that neither needs it nor can display it in full.

2015-today: Google starts measuring speed, and suddenly it matters

The most decisive shift of the last decade wasn't technical, it was about incentives: Google started using load speed as a ranking factor, and in 2021 formalized this with Core Web Vitals — concrete metrics like LCP (Largest Contentful Paint, how long it takes for the largest visible element to render, almost always an image) that directly affect SEO. Overnight, compressing an image well stopped being "good practice" and became something with a measurable impact on how much traffic a website receives. That's why tools like this one exist: it's not a design trend, it's that image weight became a business metric.

Image trends in 2026

With that historical backdrop, here's what's happening right now, in 2026, in how images are used on the web:

• AVIF and WebP as the standard, not the exception. A few years ago, serving these formats meant carefully checking browser compatibility. Today support is practically universal, and the question is no longer "can I use WebP?" but "why am I still serving JPG by default?"
• Less generic stock photography, more AI-generated or AI-retouched content. Not because it's cheaper (though it is), but because it fits better with brands that want a look of their own instead of the same smiling-people-in-an-office photo everyone else uses.
• Vertical formats by default. Consumption is now mostly mobile, and image design — for social, for banners, for thumbnails — is planned vertical-first (9:16, 4:5) and only adapted to horizontal afterward, the reverse of how it was done a decade ago.
• Native lazy loading as the default. HTML's own loading="lazy" attribute, with no libraries needed, has become the norm for avoiding loading images the user never actually scrolls to.
• Constant pressure to reduce weight, not add resolution. Screens keep improving (higher pixel density, more HDR), but the real trend in web production runs counter to what you might expect: export more compressed, not less, because the cost of transferring data and the impact on Core Web Vitals outweigh the marginal visual gain of a slightly sharper file.