A large photo can look good in the editor and expensive to download to a phone. When a WordPress site is slow, the images are a first element to check, especially on the reception and the product pages. The goal is not to compress everything to the point of blurring photos. It is to send an image adapted to its place on the page.
Find the image that really bothers you
Open the slow URL on mobile, then use browser tools or a performance test to see the loaded resources. Note the weight and dimensions of the first large image, then those that follow. A cover displayed at 400 pixels wide should not necessarily be sent several thousand pixels wide. Also check if the page immediately loads images located very low down.
The Web Vitals metrics explained by web.dev help distinguish initial display, page stability and responsiveness. Keep the same URL and comparable testing conditions before and after the fix. A score obtained once does not demonstrate that all visitors have the same experience.
Prepare a file of the right size
Start from the intended display area. A main product photo requires enough detail to allow the material to be judged; a list thumbnail may be smaller. Export a suitable format, then visually check the text or important details. Modern formats can reduce weight, but quality and compatibility must be checked at the actual site.
Avoid stretching a small file to fill a large banner. If the source image is poorly cropped, rework the crop before compressing. On mobile, a horizontal photo may cut off the product; the solution is sometimes a different composition and not a higher compression rate. The customer still needs to understand the offer after optimization.
Check what WordPress actually serves
WordPress can produce different sizes of an uploaded image. However, the theme or a page builder may request a version that is too large. Inspect the actual downloaded image in the browser, not just its size in the media library. Test the welcome, an article and a product page; each model may use different settings.
If you use an optimization extension, make a backup and test a few pages before mass processing. Check transparencies, text embedded in diagrams, and sharing images. Automation that makes a diagram unreadable saves bytes in the wrong place.
Keep content accessible and stable
Add alternative text that describes the information conveyed by the image when it is useful for understanding. Reserve dimensions in the layout to avoid skipping during loading. Do not deliberately delay the main image visible upon opening the page; Lazy loading is best suited for images placed lower down.
On a product page, ask someone to find the color, size or detail they need after compression. If it has to zoom in without getting more information, you may have zoomed in too much. Performance serves the decision, not the other way around.
Measure then move on to the next brake
After correcting the priority images, repeat the test and check the contact or purchase path. If the page remains slow, then look at the extensions, cache, and server. Our article on WordPress cache and extensions organizes this second stage. The guide “Audit and correct your site” provides a broader method for classifying technical issues and verifying fixes.
Frequently asked questions
Should we compress all images on the site?
Start with the pages and images that carry the most weight in important journeys. Mass compression without visual control can damage useful resources.
Is WebP enough to make WordPress fast?
No. The displayed size, theme, scripts and server also matter. A modern file sent in excessive dimensions can remain heavy.
Can we keep very detailed photos?
Yes when the detail helps the purchase. Offer a size adapted to the thumbnail and a richer version when the user opens the photo.
