Find the Large Images Slowing Your Site

Always the original. A 5 MB photo that WordPress auto-scaled to a 90 KB display copy is still reported as 5 MB, because that full file remains on your server and still gets served.

Straight from the results you can trash a file or send it to compression, so fixing PageSpeed's "properly size images" warning is a click away rather than a manual hunt.

Large image files inflate Largest Contentful Paint - a core Web Vitals metric - and slow the whole page. Trimming the heaviest files is one of the fastest ways to lift your score.

Yes. 1 MB is the default, but you can raise or lower it to suit your site - a photography portfolio and a documentation site have very different ideas of "too big".

Compress first. Most oversized files are simply unoptimised rather than unwanted, and compression usually solves the problem without you losing anything. Save deletion for files nothing on the site actually uses.

No. Each image's file size is recorded once and refreshed whenever the file changes, so the report reads stored values instead of measuring thousands of files on every page load.

No. It reports on WordPress attachments only, so theme assets and files uploaded outside the media library are left alone.