The 512KB Club: The Web’s Quiet Rebellion Against Bloat

The 512KB Club is a public directory that mainly focuses on lightweight websites whose entire homepage, images and all, loads under 512 kilobytes of page weight, without doing any compression. It’s a small corner of the small web pushing back against web bloat, where a single news homepage can weigh several megabytes without reading a headline.

The main thing is, nearly half of that typical weight is JavaScript, which raises an obvious question: why are modern websites so bloated?

What the 512KB Club Actually Is

The 512KB Club sorts member sites into three tiers.

• Green Team: under 100KB
• Orange Team: under 250KB
• Blue Team: under 512KB

Members display a small badge showing their team, a visible piece of web minimalism as identity. It feels like 88×31 web buttons and blinkie graphics, where a tiny image shows who you are.

Developer Kev Quirk started the project. It’s now widely open source on Codeberg and SourceHut, where you can just submit a pull request to add your site.

Why 512KB?

The reality is, the 512KB limit isn’t a universal definition of a fast website. It’s a constraint. That’s what makes the 512KB club interesting. Instead of asking how much a modern homepage can get away with loading, it asks what a useful website can accomplish within the circle.

Every Image, font, script, animation, and external resource has to justify its place. The goal is not to make the website as small as possible. It’s to prove that a real website can remain useful, attractive, and personal without becoming unnecessarily heavy.

The Problem It’s Reacting To

The club’s homepage says this openly: the internet has become a bloated mess. Huge JavaScript libraries and unnecessary frameworks are the norm now, even for simple pages, and it’s a big part of why lightweight websites matter.

The New York Times comparison isn’t a throwaway line. The research shows that the club links to an actual-size report showing the paper’s homepage running into multiple megabytes, with JavaScript making up roughly half of it.

This shows a clear example of how website size affects performance. More weight means slower loading on weak connections, more data on mobile plans, and more energy used across every data server.

How a Site Actually Joins

Joining is manual and a little old-fashioned. Site owners check the homepage’s total uncompressed size (There are multiple tools to scan). The best one I thought was Firefox’s network tab or Cloudflare Radar scan. It is one of the simplest web performance metrics to check yourself.

A maintainer reviews it before it goes live. Interesting thing: not every tiny site qualifies. The FAQ clearly shows that a page with just a paragraph and a few links doesn’t count, even at 2KB. The goal is proving a real, useful fast website can be this light, not for the smallest possible file.

What Trimming a Site Down Looks Like

Developer Calvin Barker documented his attempt to get his personal Next.js site under 512KB, but the site started at around 600KB.

Then he noticed that his biggest single win came from dropping a custom web font for the operating system’s default fonts. That saved around 50KB and shows how much lightweight design comes down to small, unglamorous choices.

Converting his photo from JPEG to WebP barely helped, and converting to AVIF (a newer image format) cut it from over 200KB down to roughly 70KB.

He also spotted a new trap. Build tools like Next.js report compressed file sizes in their logs. Tools like Cloudflare Radar report uncompressed sizes, the number the club actually measures. Later, he said it cost him an hour of debugging a problem that didn’t exist.

Why It Matters Now

The 512KB Club started in an era of bloated JavaScript frameworks. In modern AI-assisted site builders, which can develop polished-looking heavy websites just as easily as a human developer can, but none of them checks what they leave behind.

The club’s ideology is that manually proving a homepage doesn’t need that weight is a useful counterweight. It’s one more sign of the instincts behind the personal homepage era: building something small, legible, and entirely your own never really went away. They found a new way to keep score.