Images do more than decorate a small-business website: they show customers what you offer, build confidence and help explain details that words alone may not convey. But a large image can delay a page, while an image reduced too aggressively may look soft, blocky or poorly cropped. Effective website image optimisation is not simply making every file as small as possible. It means choosing an appropriate image, preparing it for the space it will occupy and delivering it in a way that preserves a good viewing experience.
This guide sets out a practical process for WordPress site owners. You’ll learn how to choose image dimensions and crops, compare common file formats, compress without guesswork and provide useful alternative text. It also covers responsive delivery and checks to make after uploading, because a carefully prepared original can still be displayed at the wrong size or slowed by the way a page is built. The right settings depend on the subject, layout, theme and tools in use, so treat examples as starting points and review images on real devices rather than relying on one universal file-size target.
Content
Start with the image’s purpose
Decide what the image needs to do
Before resizing or compressing an image, decide why it is on the page. An image might help a visitor recognise a product, understand a service, see how a process works or feel confident about who they are dealing with. If you cannot identify a useful role for it, consider removing it. A smaller file is still an unnecessary download if it does not help visitors.
Review the page from a visitor’s point of view. What question are they likely to have at this point, and does the image answer it? A clear photograph of the actual product may help someone distinguish between options; a generic decorative photograph may add little. For a service page, a relevant image could show the setting, equipment or kind of work involved. Choose images that support the page’s specific message rather than relying on visuals simply to fill space.
Check whether the image adds information that the surrounding text does not. If it shows a detail that matters, make sure that detail is easy to see and explained nearby. If the same point is already clear in the text, the image may be repetitive. Be especially cautious about putting important instructions, prices or other essential information only inside an image: visitors may have difficulty reading it, and it may not adapt well to different screens or accessibility needs.
Then consider whether this is the right image. Confirm that it is relevant to the page, current and appropriate for your business. A photo of an old product, outdated premises or a service you no longer offer can undermine otherwise accurate content. Check that you have permission to use the image, particularly if it came from a supplier, photographer or stock library. If the image is unclear, misleading or poorly matched to the subject, replacing it is usually more useful than trying to optimise it.
A simple content review can help. For each image, note the page it appears on, what it communicates and whether that information is useful to the visitor. Decide whether to keep, replace or remove it before making technical changes. If you keep it, choose the version that best conveys the subject; don’t crop out a defining feature or reduce detail that visitors need to assess what they are seeing. This gives later optimisation decisions a clear purpose: preserving the image’s useful qualities while making its file more suitable for the website.
Match dimensions and crop
Size for the space, not the camera
Before resizing an image, check how it will appear in the page template. Look at its maximum displayed width on a desktop screen and how that changes on mobile. A photo shown in a narrow article column does not usually need the same pixel dimensions as a full-width banner. Use your browser’s preview or the WordPress editor to inspect the layout, and check the theme’s documentation if you need to confirm the intended image area.
Pixel dimensions describe the image file, not the size it will occupy on screen. If an image is displayed at about 800 pixels wide, a version close to that width may be suitable, depending on how the site serves images and the screens you need to support. Avoid uploading a very large camera original for a small thumbnail: it may contain far more pixels than the page needs. At the same time, do not make the file smaller than its display area, as the browser may have to enlarge it and the result can look soft. Keep an unedited original separately if you may need to create a larger or differently cropped version later.
Consider high-density screens as well as the layout. Some implementations use a larger image source for sharper display on devices with more pixels per CSS pixel. WordPress can generate image sizes, but which variants are created and served depends on settings, the theme and how the image is placed. Do not assume that uploading one oversized file will automatically give every visitor an appropriately sized version. Check the image source and appearance on the live page, particularly if the site uses custom templates or page-building tools.
Crop around the subject
Choose a crop that fits the shape of the space: for example, a wide landscape for a banner or a square crop for a card. Keep the subject’s important details inside the area that will remain visible, with a little breathing room around faces, products or text embedded in the scene. A centred subject may work across layouts, but it is not always the best choice. If the subject sits to one side, check that the mobile crop does not cut it off or leave an awkward amount of empty space.
Hypothetical: If a page displays a photo at about 800 pixels wide, prepare an appropriately sized version and check how the crop looks on mobile. If the desktop layout uses a wide crop but the mobile layout needs a taller image, test whether the same file can be cropped acceptably at both sizes. When it cannot, make separate versions for those placements if your WordPress setup lets you select or serve them reliably. This is often more useful than forcing one crop to suit every screen.
For repeated placements, such as product cards or staff profiles, use consistent dimensions and aspect ratios so the page looks orderly. Crop before uploading when you need precise control, or use WordPress’s image-cropping tools where available; then preview the result in its actual template. Check faces, product edges, logos and any meaningful background details. A crop that looks tidy in the media library can behave differently in a narrow column, so review both desktop and mobile views before publishing.
Choose a suitable format
Choose a format that suits the image
Choose a file format according to what the image contains, whether it needs transparency and how your website will process and deliver it. There is no single best format for every image. A practical choice should preserve the detail visitors need without creating an unnecessarily large file or a maintenance problem for your WordPress site.
JPEG is a common choice for photographs and other images with many colours or gradual changes in tone. It uses lossy compression, so some image information is discarded to reduce file size. It does not support transparency, and repeated editing and saving can make quality loss more noticeable. Keep a high-quality original where you can, and export a suitably compressed copy for the website rather than repeatedly recompressing the same JPEG.
PNG is useful when an image needs a transparent background, or when sharp edges, flat colours and small details matter. It is also often suitable for interface screenshots, diagrams and simple illustrations. PNG uses lossless compression, which preserves the image data, but photographs saved as PNG can be much larger than an equivalent JPEG or modern format. Don’t choose PNG automatically just because it is described as higher quality; use it when its qualities are needed.
WebP can handle photographs as well as graphics, and supports transparency. It offers both lossy and lossless compression, so it can be a useful option for reducing file weight while retaining the appearance required for the image. AVIF also supports transparency and can compress a range of image types efficiently. However, file size and visual quality depend on the source image and export settings. Test the actual files rather than assuming either format will always be smaller or look better.
Before adopting WebP or AVIF, check your WordPress installation and image-processing setup. WordPress support depends on its version and the server’s available image-processing libraries; a format that can be uploaded is not necessarily one your setup can resize or convert into all the required image variants. Check your hosting documentation or ask your host or developer, then test uploading an image, generating the sizes used by your theme and viewing it on the public site. Also confirm whether any optimisation plugin or content delivery service changes formats or serves a fallback. Don’t assume that installing a plugin automatically makes every visitor’s browser or every part of your site compatible.
For a small business site, make format decisions at the image level rather than converting the entire media library without checking it. Keep JPEG for suitable photos, use PNG where transparency or crisp graphic detail is important, and consider WebP or AVIF where your workflow reliably supports them. After uploading, inspect the image on a real page, including its mobile layout, and check that it displays correctly. If a newer format causes trouble in a theme, plugin or browser, use a format your setup can serve consistently or configure a tested fallback. Revisit the choice when you change hosting, WordPress versions or image-processing tools.
Compress with care
Use a controlled, reversible test
Once an image has the right dimensions and format, reduce its file weight in small, deliberate steps. Keep an untouched copy of the original outside the website’s media library, then make a compressed version to compare. This gives you a reliable reference and lets you start again if the result looks poor. Avoid changing dimensions, format and compression settings all at once: if the image degrades, you will not know which change caused it.
Use an export tool or image editor that lets you control compression, or review the settings of any WordPress image optimisation tool before applying them. Some tools offer a quality slider; others use named presets or compress images automatically. The controls and results differ, so do not assume a particular setting will suit every photograph, illustration or screenshot. Begin with a conservative setting, save the new file and compare its file size with the original. If the reduction is modest, try a slightly stronger setting and compare again rather than jumping straight to maximum compression.
Judge the image at the size visitors will see it on the page, as well as close up. At its display size, check whether the subject still looks clear and colours remain natural. Then zoom in to inspect fine detail, edges and any areas with subtle gradients, such as skies or shadows. Look for blocky patches, banding, blurred textures, halos around edges or colour shifts. These are signs that compression may have gone too far, even when the smaller file looks acceptable at a glance.
Pay particular attention to images that contain text, sharp lines, icons or diagrams. Compression can soften letter edges, make small labels difficult to read or introduce distracting marks around high-contrast details. If those features matter, compare a less-compressed export or consider whether a format suited to crisp edges would preserve the information more clearly. Do not treat file size as the only measure of success: an image that downloads quickly but no longer communicates its content is not a useful improvement.
For each image, keep the smallest version that still looks good in its intended context. Your best setting for a large photographic banner may not work for a product image or a detailed screenshot, so test representative images rather than relying on one preset for everything. Record the export settings that work for recurring image types; this makes future uploads more consistent without turning the setting into a rule that ignores the image itself.
If compression happens through WordPress, check the image visitors actually receive after saving or uploading it, not just the file you prepared beforehand. A plugin or image service may create or serve a separate compressed version. Preview the page on desktop and mobile, and inspect images with important detail before applying a bulk change to existing media. Keep originals or a dependable backup where possible, and change one setting at a time. A measured comparison helps you find a sensible balance between lower file weight and visible quality without making a hard-to-reverse change across the whole site.
Support access and responsive delivery
Make images accessible and fit the screen
Optimising a file is only part of the job. The image also needs to be described appropriately, displayed at its intended size and delivered in a version that suits the visitor’s screen. Check these details in the WordPress editor and on the published page: the settings you enter do not always show exactly how the theme or other site tools will render an image.
Write alt text that communicates the image’s purpose in its context. For an informative image, describe the relevant subject or action rather than listing every visible detail. If the image is purely decorative, use empty alt text so assistive technology can skip it. Avoid repeating nearby headings, adding “image of” by default, or stuffing in search terms. In WordPress, add or review the alt text in the media details or image block, then consider whether the surrounding text already explains the image. A caption and alt text serve different purposes: captions are visible to readers, while alt text provides a text alternative when needed.
Set the image’s display dimensions deliberately. In the block editor, choose an appropriate image size or set the displayed width where available; avoid enlarging a small source image beyond a clear result. Retain the correct proportions unless the layout intentionally crops the image. Width and height information in the rendered image helps browsers reserve space while the file loads, reducing unexpected page movement. Check that the image remains legible and the subject is not awkwardly cropped at narrow and wide viewport sizes.
Check responsive variants and loading behaviour
WordPress can create several image sizes when an image is uploaded, and commonly includes responsive image information such as srcset and sizes in the page markup. The browser uses that information to select a candidate based on the layout and screen. This is not automatic proof that the right file will be selected: the theme, block settings, custom code and optimisation tools can affect the markup and available variants. If a design repeatedly displays an image in a specific, smaller area, check whether an appropriate intermediate size is available rather than making every visitor download the largest original.
Loading behaviour matters too. Lazy loading can defer images that are further down the page until they are closer to view, while an image visible immediately—especially the main page image—should not be unnecessarily delayed. WordPress and themes may apply loading attributes automatically, so inspect the final page rather than assuming a setting has taken effect. Avoid marking many images as high priority; reserve eager loading or priority treatment for an image that genuinely needs to appear promptly. Test pages with long content as well as short ones, because an image near the top of one layout may sit below the fold in another.
After publishing, review the page at desktop and mobile widths. Use your browser’s developer tools to inspect the image element and network request: check the selected file URL, its pixel dimensions and file size, and whether the browser receives responsive candidates. Also look for missing alt text, stretched images, layout shifts or a large original being downloaded for a small display area. If a cache, content delivery network or image optimisation service is involved, test the live page after its cache has refreshed; it may alter delivery, but its behaviour depends on your setup. Correct the image size settings, theme configuration or optimisation rules where needed, then recheck the result.
Conclusion: keep images in balance
Conclusion: keep images in balance
Make image checks part of your regular publishing workflow, rather than a one-off tidy-up. Before adding an image, confirm its purpose and prepare a version suited to the space where it will appear. Choose a format and compression level that keep important detail clear without adding unnecessary file weight. Inspect the image at its displayed size, including on a mobile screen, before publishing.
Then add alt text that describes the image’s useful information or function; leave it empty when the image is purely decorative. Check that WordPress is displaying suitable image sizes for the page and that loading behaviour is appropriate, especially for images near the top of the page. After changing a page or theme, revisit key pages on desktop and mobile to catch awkward crops, missing descriptions or slow-loading images. When replacing images, review older versions and remove files that are no longer needed, taking care not to break links. A short check at each update helps keep clarity, accessibility and page speed in balance as your website grows.
Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.


