Your photographs should show the product, not keep the visitor waiting. We assess and optimise how WordPress prepares and serves images, with an agreed page sample, quality criteria and a way to reverse changes.
This service is for teams with oversized mobile downloads, unexpectedly heavy WebP files, blurry product images or a main image that arrives late. The brief can cover a small group of templates or a larger catalogue after the delivery rules have been tested.
Request an image optimisation assessment ↗
Start with what the browser actually downloads
We inspect representative pages and image requests at the agreed viewport sizes. The review distinguishes the original asset, generated variants, the image selected by the browser, transferred bytes, visible dimensions and the point at which the request starts.
A smaller file in the Media Library does not establish that visitors receive it. A template, builder or delivery layer may still request another version. The initial output identifies the relevant source and the proposed correction before a batch conversion is commissioned.
What can be included in the work
- Formats and quality: compare suitable versions on a representative image sample and agree the visual result with the team.
- Responsive delivery: review generated sizes,
srcset,sizesand the actual resource selected on mobile and desktop. - Product presentation: check listing thumbnails, galleries and zoom where they are in scope.
- Loading behaviour: investigate when the important image is requested and whether loading rules delay it.
- Replacement and deployment: preserve originals, map affected references and define cache updates and recovery.
The proposal states which templates, image types, languages and delivery systems are included. CDN configuration, custom builder work, catalogue regeneration and changes to a third-party image service are separate dependencies to identify, not assumptions hidden inside a conversion fee.
Keep enough detail for the buying decision
Compression acceptance needs real examples. A fabric texture, a technical label, a room photograph and a transparent logo may need different treatment. We agree the representative set and compare the result at its intended display size, including relevant gallery and zoom behaviour.
If the source is already too small or damaged, the correct next step may be a better source asset. The engagement should identify that limitation rather than keep processing a file that cannot supply the missing detail.
A controlled first batch before changing the catalogue
For a shop with many product photographs, start with a representative set of products and templates. Preserve the originals and record the intended replacements. Check the delivered resource and the visual result before extending the same rules to more items.
Agree who approves quality and who can publish. A new format or size should not silently break an image URL, change a product crop or remove information the customer needs. A catalogue-wide batch requires its own scope, storage allowance and recovery plan.
What you receive at handover
- The pages, templates and image sample reviewed.
- The issue found and the delivery or asset change applied.
- Comparable request observations before and after, under recorded test conditions.
- Visual checks, including the product detail and layouts agreed in scope.
- A record of preserved originals, replacement references and how to reverse the change.
- Remaining dependencies and recommendations for the publishing team.
Image transfer, the arrival of the main content and whole-page performance describe different things. We record which measurement the change addresses. A smaller image does not by itself demonstrate a particular PageSpeed score, ranking increase or sales result.
Which images should you send for an assessment?
Send two or three public page URLs, the device or viewport where the issue appears and the visible problem. If the site uses an image CDN, builder or conversion plugin, name it. Do not include passwords or private customer information in the initial request.
For a quote, we also need an approximate catalogue size, the templates involved and who can approve the image quality. The assessment establishes whether the main work lies in the assets, the template or their delivery.
Useful guidance before commissioning
Our guides explain why WebP can be larger than JPEG and how to check full-size mobile image delivery. Google’s image guidance covers discovery and responsive markup; web.dev explains responsive image delivery. These are technical foundations to review alongside the site’s actual behaviour.
For a wider store problem, see WooCommerce performance work. To start with the images, send the affected pages and request a scoped proposal.
Choosing between AVIF and WebP?
Before converting a whole library, use our guide to AVIF vs WebP for WordPress in 2027 to agree a representative sample, check hosting support and verify the file actually served on mobile.