That's a job for a computer, not a human. It's a waste of an editor's time to dwell on such details, just as it's a waste of a newspaper editor's time to worry about the ink in the printing machines.
Also, you just admitted that your own place of work serves large images. Let's not throw blame around that we're not willing to take ourselves.
> you just admitted that your own place of work serves large images. Let's not throw blame around that we're not willing to take ourselves.
Yes, it happens at my place of work, and that is where my generalization came from. I intended to indicate that even when taking steps to mitigate the issue, it still crops up because it's a hard problem to fix. Eventually, work gets delegated to people that don't know everything they should. It is not a big deal as long as people are learning from it.
It happens when we assign web tasks to interns "and non-webdev staff" without proper education/training. So if you follow Toyota's "five whys" rule, it is not the interns' fault at all.
I wrote an image API at my place of work to take a file by name and accept dimensions in the query string. It resizes the image, caches the file on disk, at and serves the smaller file. However, it's tough to integrate that API with every little WYSIWYG editor we have, so sometimes we still serve up large files in this way.
Usually, intentional retina-quality images have plenty of telltale signs (like the @2x naming convention).