Product images far larger than they need to be
A four-megabyte photograph is the slowest thing on a product page, and on a phone over cellular it is why the visitor leaves before seeing the price.
The symptom
The store feels fine on your laptop on office Wi-Fi. On a phone, on mobile data, the product page shows text and then a gray rectangle for two seconds before the photograph appears.
The cause is usually a camera file uploaded exactly as it came off the card, or a supplier’s press-quality image dropped straight into the library—4000 pixels wide and several megabytes, to be displayed in a 600-pixel box.
What it costs
On a product page the main photograph is almost always the largest element on screen, which makes it the thing Core Web Vitals measures as Largest Contentful Paint. Whatever that image weighs is what the visitor waits for before the page looks finished.
- Mobile visitors leave first. They are the majority of ecommerce traffic and the ones on the slowest connections, and they leave the earliest.
- It compounds on category pages. One heavy image is a slow product page; twenty-four of them in a category grid is a page that never settles.
- It costs bandwidth, on your hosting and on the visitor’s data plan.
Merchlint uses 500 KB as the threshold. That is high enough that a properly exported product photo passes comfortably, and low enough that an untouched camera file does not. The free plugin has no setting to change it.
How to check it yourself
Straight from the filesystem, which is the honest measurement:
find wp-content/uploads -type f \
\( -iname '*.jpg' -o -iname '*.jpeg' -o -iname '*.png' -o -iname '*.webp' \) \
-size +500k -printf '%s\t%p\n' | sort -rn | head -40
That lists the forty heaviest files with their sizes. On Windows without a shell, the same job is one line in WP-CLI:
wp eval 'foreach ( get_posts(["post_type"=>"attachment","post_mime_type"=>"image","posts_per_page"=>-1,"fields"=>"ids"]) as $id ) { $f = get_attached_file($id); if ( $f && file_exists($f) && filesize($f) > 512000 ) printf("%d\t%s\t%s\n", $id, size_format(filesize($f)), basename($f)); }'
How to fix it
- Resize before upload. Decide the largest size your theme ever displays, usually somewhere between 1200 and 2000 pixels on the long edge, and export to that. WordPress scales down only originals wider or taller than 2560 pixels, and even then it keeps the original file.
- Compress. On a product photo, JPEG at quality 80 usually looks the same as quality 100 and weighs a fraction as much.
- Serve modern formats. WebP or AVIF typically halves the transfer again. Any of the common image plugins will do this without you touching the originals.
- Do not delete the originals to save space if you sell prints or need zoom—the fix is to stop serving them, not to lose them.
When it’s a false alarm
There is one important one, and it deserves saying plainly.
Merchlint measures the file that was uploaded, not the file the visitor downloads. WordPress generates smaller variants and serves one of those; an optimization plugin may serve a WebP that never touches the original at all. So a 3 MB original can sit behind a page that transfers 90 KB, and this check will still report it.
That is a deliberate trade-off, not an oversight. The stored file is a fact the plugin can read without fetching anything, and the only pages it ever fetches are up to three of your own product pages, for a different check. Treat the finding as “this original is heavier than it needs to be”, which is worth knowing anyway for backups and migrations, rather than as “your page is slow”.
Other cases: images sold as the product (print files, digital downloads) and zoom imagery
that genuinely needs the resolution. The free plugin has no setting for the threshold, but a
developer can raise it with the merchlint_scan_settings filter (the d1_max_bytes key).
How Merchlint finds it
Merchlint reads the size on disk of the main image of every published product, and of each variation’s own image, and compares it with 500 KB. Gallery images are not checked. It reports the image rather than the product, because one photo often belongs to several products and is fixed once. The finding shows the image, its size, the threshold and one product that uses it.
Confidence: F—fact from the database and the filesystem. A byte count compared with a number.
Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com