To compress images on a WordPress affiliate website, resize them first, then use one image optimization plugin to reduce file size. Keep useful product detail clear, especially labels, screenshots, and comparison images that help visitors decide what to buy.
You don’t need several plugins working on the same files, and you don’t need to sacrifice quality for a better speed score. Start with the images on your busiest review pages, then work through the rest of your library.
There is a plugin on this site called Imagify that will take over if I forget to compress images on WordPress, but generally I do my resize and compression before upload with a free program called Paint.net which does a brilliant job.
Key takeaways for faster affiliate pages
Google’s Core Web Vitals guidance covers loading, responsiveness, and visual stability. Image compression mainly helps the loading side.
- Resize oversized uploads before compressing them, and keep product details readable on mobile.
- Compare plugin allowances carefully. Uploads, thumbnails, megabytes, and visits are different billing units.
- Back up your website before bulk optimization, then test real review pages and affiliate links afterward.
Resize images before uploading to WordPress
Match the dimensions to your page
Modern smartphone and camera photos can be much larger than your review page needs. Uploading those originals wastes storage and can leave visitors downloading unnecessary pixels.
WordPress.com recommends images around 1.5 to 2 times your content width. For a 600-pixel content area, its example recommends a 1,200-pixel-wide image.
Now, apply that to your actual layout. A small product thumbnail doesn’t need the same dimensions as a full-width comparison graphic. Keep a larger version only where visitors need to zoom in.
Before you compress images WordPress stores, use image resizing to match product images to their display dimensions while retaining the detail visitors need.
For an affiliate bridge page, one clear product image may do more useful work than a heavy gallery.
Understand what WordPress already does to compress images on WordPress
WordPress creates different image sizes in your media library and can supply responsive versions to browsers. These can work as adaptive images, letting browsers use a suitably sized rendition.
WordPress’s default large-image threshold is 2,560 pixels, so larger uploads are normally scaled. This automatic WordPress image optimization helps, but scaling dimensions alone doesn’t guarantee a lightweight file.
WordPress also applies compression when generating certain image versions, but a dedicated optimizer gives you more control.
Choose an appropriate image size when inserting media. Selecting “Full Size” everywhere can undo the benefit of having smaller versions available.
Choose compression and formats that keep detail clear
Use lossy compression carefully
Lossless compression preserves pixel-identical quality. It’s useful when every detail matters, although the savings can be smaller.
Lossy compression removes some image information for greater file-size reduction. At sensible settings, the difference can be hard to notice in product photos.
Screenshots need more care. Small text, software menus, pricing tables, and fine product markings can become blurry.
My recommendation is simple: start with moderate compression, then compare file size reduction with image quality at its actual display size. Keep an untouched original so you can try again without repeatedly compressing an already-compressed file.
Choose WebP or AVIF without forcing it
WebP and AVIF are next-gen formats that can deliver smaller files than older formats at comparable visual quality. WebP is a practical starting point, while AVIF is worth testing when your optimization setup supports it.
A WordPress WebP versus AVIF comparison explains the format choices in more detail.
Keep original JPG and PNG images available for recovery. Let your chosen delivery system handle converted versions and any required fallback.
WebP conversion changes the delivery format, but it doesn’t fix oversized dimensions. A huge WebP image can still be too heavy if its dimensions are wrong.
What published plugin tests actually show
WPAutoRobot’s October 5, 2025 comparison used a 1,275 KB landscape JPG measuring 2,700 ร 1,451 pixels.
These were its reported results, not results from testing on this website.
| Plugin | Reported result |
|---|---|
| ShortPixel | Reduced the JPG to 220 KB, an 83% saving |
| Optimole | Achieved a 77% reduction |
| EWWW Image Optimizer | Achieved an 18% reduction at default settings |
That plugin performed strongly on that file. But these percentages don’t predict what will happen to your screenshots, transparent graphics, or already-compressed merchant photos.
A reduction percentage only tells you something useful when you know the starting file, settings, and resulting quality.
The published figures may help you shortlist tools such as ShortPixel. Test your own product photos and screenshots before making a final choice.
Compare plugins billed by image
ShortPixel: understand the thumbnail credits
ShortPixel’s image optimization comparison lists 100 free credits per month. That’s a useful starting allowance for testing a small affiliate blog.
When comparing an image optimization plugin, check how it counts originals and thumbnails, not just its headline allowance.
Each original or thumbnail reduced by at least 5% uses one credit. One upload can therefore consume several credits.
There’s also a documented change to watch for. Older comparisons describe WebP and AVIF creation as free. ShortPixel’s credit guidance dated October 28, 2026, counts each converted image or thumbnail as an additional credit.
Install the plugin, connect your account, and test its compression settings on a small selection before starting a full-library job. If you’re comparing Smush, check its current credit and thumbnail rules rather than assuming its billing matches ShortPixel or TinyPNG.
TinyPNG: simple per-compression billing
TinyPNG, also called Tinify, offers 500 free compressions per calendar month through its WordPress integration.
That doesn’t necessarily mean 500 uploads. Generated thumbnails count separately, so a regular installation may get roughly 100 uploaded images from that allowance.
Its listed API rates are $0.009 per compression for the next 9,500, then $0.002 for the next 10,000 per month.
This makes thumbnail selection important. Optimize the sizes your theme uses rather than spending your allowance on unnecessary versions. Turn on automatic processing for new uploads once your sample results look good.
Compare plugins billed by upload size or traffic
Imagify: a megabyte-based free allowance
Imagify’s forever-free Starter plan includes 20 MB of optimization per month, described as roughly 200 images. It also has a 2 MB limit per image.
That estimate depends on file size. Large product photos use the allowance faster than small graphics, so resizing before upload helps twice: smaller files and less allowance consumed.
Imagify suits a beginner who prefers thinking in upload volume rather than thumbnail credits. Before using its current bulk workflow on older media, test representative images and inspect the results.
Optimole: an allowance based on visits
Optimole’s free plan covers up to 2,000 visits per month. Its Starter tier covers up to 48,000 visits.
The billing unit matters here. You’re choosing around traffic rather than simply counting how many images you upload.
That can make sense for an image-heavy affiliate site with modest traffic. A paid advertising campaign, however, can change your traffic requirements quickly.
Smush is another option to investigate. Check its current plan limits and billing unit rather than assuming it’s based on traffic or megabytes.
When choosing between these options, focus on the limit you’re most likely to reach: image credits, upload megabytes, or monthly visits. Buy around that need, rather than the longest feature list.
Bulk-optimize your media library safely
Already uploaded hundreds of images? You can optimize existing media without rebuilding every review.
Keep the process manageable, especially when those pages already receive traffic.
- Create a complete backup. Include the database, uploads, themes, plugins, and configuration. Back up original images, keep an independent offsite copy, and test a restore on a private staging site.
- Choose one optimization system. Avoid having multiple plugins compress the same files or apply competing format-conversion rules.
- Optimize a small sample first. Include a product photo, a screenshot, a transparent graphic, and an image from a comparison table.
- Run bulk optimization in batches. Use your plugin’s existing-media feature and account for your hosting capacity and server resources during large jobs. If Imagify’s current bulk tool offers batch controls, use manageable batches and inspect pages between runs. Preserve attachment records, filenames, and working image URLs rather than deleting and re-uploading files.
- Clear caches and inspect published pages. Open review pages, product boxes, comparison tables, and opt-in pages on desktop and mobile.
A plugin’s original-image backup is useful, but it doesn’t replace a complete WordPress backup. It won’t necessarily recover your comparison-table settings or affiliate redirects.
Don’t delete original files just because the compressed versions look fine immediately. Keep your recovery route available until you’ve tested the important pages.
Check image quality, page speed, and affiliate results
Inspect what buyers need to see
- Open the published page on your phone.
- Can you read the product label?
- Are software screenshots sharp enough?
- Does the comparison graphic still explain the difference?
Inspect images at their displayed size and check any zoomed version separately. Look for blurry lettering, blocky edges, and damaged transparent backgrounds.
Compression settings may also remove EXIF data. That can reduce file size and remove camera or location details, but preserve any information you need for attribution or your records.
Lazy-load images farther down the page. Keep the main above-the-fold image out of lazy loading when it’s needed immediately. If your optimizer offers CDN delivery, evaluate it separately from image compression.
Measure the page, not just the image
Use Google PageSpeed Insights before and after optimization to compare page load time. Test the same page several times and compare the overall pattern.
Elementor’s published test reduced one image from 693 KB to 165 KB. Its mobile score rose from 47 to 69, while LCP improved from 25.7 to 5.6 seconds.
That’s a useful improvement, but 5.6 seconds still exceeds the good LCP target of 2.5 seconds.
My affiliate landing page speed guide covers the wider mobile audit. If images are no longer the bottleneck, investigate scripts, redirects, and server delays.
Then track opt-ins, affiliate clicks, and cleared commissions. A better score alone isn’t a business result.
Frequently asked questions on how to compress images WordPress affiliate pages use.
Can a plugin compress merchant-hosted product images?
Usually, a media-library optimizer processes images stored in your WordPress installation. It won’t automatically change images served directly by a merchant or affiliate network.
Follow the network’s image-use rules. Don’t download and alter merchant images when the agreement requires its supplied delivery method.
Which plugin should a beginner choose first?
ShortPixel is a sensible first shortlist option because of its compression controls and strong result in the cited test. Imagify offers a straightforward upload-size allowance.
Choose TinyPNG when per-compression billing suits you, or consider Optimole when a visit-based allowance fits your traffic. Start with the free allowance and a small sample.
Keep product images fast and useful
Your affiliate images should help visitors understand the offer without making them wait. Resize first, use one optimizer, and protect the details that support a buying decision.
Start with one busy review page. Compare quality and loading performance before expanding to the full library, and keep a tested backup ready throughout. Good luck when you compress images WordPress affiliate pages and posts use.
Malcolm Keith 2026


