skip to main content
estimated reading time: 3 minutes

If you build websites, you really should be testing pages using tools like the one Pingdom offers, if only to see just how bloated your pages are in production and where the bloat is coming from.

In the case of a blog post from last year, the page weighs in at 601KB total. That might be respectable by current standards, given the website obesity crisis. I suspect that anybody stuck on dialup or using a metered mobile data connection would still find 601KB for a blog post unacceptable.

Where does the bloat come from? It comes from a YouTube embed. See for yourself.

We’re looking at a total page size of 601.77 KB, of which only 6.27 KB comes from By way of comparison, this page weighs in at around 6.5KB.

Where’s the rest of it coming from? Here’s the breakdown.

Domain Percent Size 87.4 % 525.82 KB 4.8 % 29.10 KB 3.3 % 19.88 KB 2.5 % 15.31 KB 1.0 % 6.27 KB 0.9 % 5.38 KB

Most of the data is coming from, and it’s nothing but JavaScript. That’s right. Google, a megacorporation that supposedly hires the best and brightest developers on earth, needs to shove over 500KB of JavaScript down the pipe just to display a still from a video and a play button.

One hopes that this gets cached so that multiple embeds on a page or on a site can reuse it, but I doubt it. I don’t think anybody at Google cares that much, or remembers what it was like to surf the web on a 56K dialup connection.

This is why YouTube must be destroyed. Preferably along with the rest of Alphabet, including Google. In the meantime, we need a better way to include multimedia content.

Middle Ground?

Somebody on the Fediverse suggested another way:

The middle ground we found at #Friendica is to put the Youtube embed behind a click. If you don’t click, nothing is loaded.

If you have other suggestions, try replying to my toot on Mastodon