← Back to context

Comment by Dwedit

3 days ago

I looked at a CNN "lite" article, and it includes 560KB of stuff (lots and lots of CSS declarations) in addition to the actual 11KB of article content.

While still wasteful, CSS is one of those things you can do astronomically wrong before it starts being noticeable. Case in point here: inlining 560 kb of CSS with the page and just sending it with the entire HTML file each time is only ~61 kb of actual network transfer to load the article (due to brotli encoding).

For me in Firefox it only loads the article's HTML (50-70kb) and the favicon (7kb).

Are you sure it isn't some addon you have?

  • The articles HTML is ~60 kb compressed and ~10x that uncompressed, which accounts for both apparent sizes.

  • It could be the cookie banner appearing.

    • It is, the content loads first, then the js for the cookie banner, then the favicon. If the js fails to load (I blocked the request as a test) the page loads just fine, it isn't blocked by that.

The point is that it would still work if you block JS, CSS and graphics.

Check it out in lynx for example