The Related Articles carousel at the bottom is responsible for a lot of that. In at least one of the tiles, it's backing an 82x45 thumbnail with a 2800x1556 PNG

The Related Articles carousel at the bottom is responsible for a lot of that. In at least one of the tiles, it's backing an 82x45 thumbnail with a 2800x1556 PNG. The PNG is 6 MB, which works out to over 1.5 KB per pixel. Annotated screenshot at https://twitter.com/callahad/status/989119555711782917 https://twitter.com/callahad/status/989119555711782917 What's worse, it's clear the CMS knows that the image is going to be displayed as a small thumbnail: the markup uses the picture tag and srcset attribute to provide alternative images, indicating that they'll be around 120 or 240 pixels wide, depending on device DPI. ...and yet, the actual file it serves is the same, full-resolution PNG in all cases. This is a problem that the CMS should be solving.