Image files over 500 KB
image_file_heavyShort answer
These pages load image files larger than 500 KB, as reported by the server. Large files take longer to download, especially on mobile connections, and when the image is the largest element on screen it delays Largest Contentful Paint. 500 KB is Glimana’s own threshold to point out the heaviest files; Google has no fixed size limit.
Why it matters
Most oversized images are photos uploaded straight from a camera or phone and displayed much smaller than their real size. Resizing and compressing them usually cuts the file by 80–90% with no visible difference, which makes pages faster for every visitor.
How Glimana detects it
Glimana already checks every image URL it finds on your pages with a lightweight HEAD request (to find broken images). Since 1 November 2026 it also records the file size the server reports. The rule lists, per page, images over 500 KB that answered 200; if the server does not report a size, the image is not counted.
How to fix it
- Find the affected pages in Glimana. Open Issues › Image files over 500 KB. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Resize each image to the largest size it is actually displayed at (twice that for high-density screens is plenty), then compress it: WebP or AVIF at quality 75–85 is a good default. Serve several sizes with
srcsetso phones download a small version.Use an image optimisation plugin that resizes on upload and converts to WebP/AVIF, then run its bulk optimisation for existing images. Set a maximum upload size in the media settings so originals from cameras are scaled down.
Shopify serves resized images through its CDN when the theme uses
image_urlwith a width; check that the theme does not request the original size. Re-upload very large product photos at a sensible resolution.Add an image pipeline to your build or CDN (for example, an image CDN with automatic format and resize), and generate
srcsetvariants. Reject uploads above a size limit in your CMS. -
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. Image sizes are re-checked every 14 days; the task closes when no image on the page is above 500 KB.
How the fix is verified
The image check runs again within 14 days; the issue closes when the files are under 500 KB.