How to compress oversized images in WordPress

Oversized images are the single most common cause of slow WordPress pages. A full-size 2 MB JPEG scaled down by the browser still costs the visitor the full 2 MB. The fix is to compress existing images, serve appropriately sized versions, and let WordPress generate the right thumbnails, until no image above the fold is heavier than about 200 KB.

What causes this?

Page builders and themes often place the original upload instead of a generated size. Phone cameras produce 4 to 12 MB files, and authors upload them untouched. Sliders and hero sections are the worst offenders because they sit above the fold, where every byte delays the first thing a visitor sees. None of this looks wrong in the editor, because the editor scales images visually while the browser still downloads the full file.

How to check

Open any slow page, then in Chrome DevTools run the Network tab filtered to Img and reload. Sort by size. Anything above 300 KB rendering smaller than its natural dimensions is a target. Or run the free Local Audit, which lists every oversized image with its weight and rendered size.

< 100 KBPer image, healthy.

100–300 KBWorth compressing.

\> 300 KBAbove the fold, a real problem. Fix it.

How to fix it manually

1. Identify the heaviest above-the-fold images

With the Network tab or the audit.

1. Recompress them at quality 70 to 80

With Squoosh, ImageOptim, or your image plugin. Visual difference is nearly always invisible.

1. Replace the placed image with the correct generated size

Instead of Full Size in the editor.

1. Regenerate thumbnails if you changed registered sizes

Run wp media regenerate with WP-CLI.

1. Re-test the page

Confirm the largest image is under ~200 KB.

How BoltAudit does it

The audit runs all of the above for you and turns it into one reviewed action.

1Finds it automatically. The audit names each oversized image with its weight and where it renders.

2Preview the exact change. Which files will be compressed and to what target.

3Automatic backup, then apply. Originals are preserved, compressed versions are served, in one click.

4Roll back any time from Fix History.

Fix this on your site

Common questions

Will compression make my images look worse?

At quality 70 to 80, differences are practically invisible at web sizes. Originals are kept, so nothing is lost.

Should I compress or convert to WebP?

Both. Compress first, then serve WebP where supported. See the WebP fix.

What about images below the fold?

Lazy loading handles most of the cost. Above the fold is where weight hurts most.

How do I know it worked?

Re-run the audit. The image findings clear, and Fix History shows the measured change.