Skip to main content

Optimizing Website Images: A Practical Guide for Small Businesses

Choose sensible sizes, serve responsive images and load the page's most important visual promptly.

Updated 6 min readMarkdown

A useful photograph can show the quality of a product, explain a service or help a visitor recognise the people behind a business. The same photograph can also become an unnecessarily large download when the website serves the original camera file everywhere.

Image optimisation is a series of decisions: what the picture contributes, how large it appears, which file the browser receives and when it starts loading.

Here is a practical workflow for a small business website. The filenames and layout below are illustrative; they are not measurements from a client project.

1. Give each image a job

Before changing file formats, decide what visitors should learn from the image.

On a hypothetical flooring company's website, a close-up of a finished floor might help someone judge the material. A team photograph might belong on the About page. Repeating a large decorative banner above every section adds little to either task.

Start with the homepage, one service page and one project page. List the images on each and ask:

  • Does this picture answer a question that matters here?
  • Is the important detail still visible on a phone?
  • Could a smaller crop communicate the same thing?

If the page's purpose is unclear, first review the guide to structuring a small business website. Image choices are easier when each page has a clear role.

2. Reduce dimensions and file weight deliberately

Pixel dimensions and file size are different. A 300-pixel-wide display does not automatically turn a large source file into a small download.

Keep the original separately. Export appropriately sized versions, compare JPEG, WebP or AVIF where your publishing system supports them, and inspect the results at the intended display size. Compression should preserve details that customers need to see.

There is no useful universal rule that every image must be below the same number of kilobytes. A small thumbnail and a detailed portfolio photograph have different jobs. The web.dev image performance guide explains the underlying format and sizing choices.

3. Let the browser choose a suitable version

srcset lists available image files. sizes describes the expected display width. The browser uses that information alongside factors such as screen density to choose a candidate; the markup does not generate the files.

Suppose a project photo appears further down a page. Its container has 16-pixel side margins on small screens and stops growing at 960 CSS pixels. Create three files with the same 3:2 crop: 480 × 320, 960 × 640 and 1920 × 1280.

<img
  src="/images/floor-project-960.webp"
  srcset="/images/floor-project-480.webp 480w,
          /images/floor-project-960.webp 960w,
          /images/floor-project-1920.webp 1920w"
  sizes="(min-width: 992px) 960px, calc(100vw - 32px)"
  width="1920"
  height="1280"
  loading="lazy"
  alt="Oak flooring fitted around the doorway of a bright living room"
  style="display: block; width: 100%; max-width: 960px; height: auto;"
>

Replace the example paths with real files and adapt the alt text to the actual photograph. The 480w, 960w and 1920w values must match those files' intrinsic widths.

This sizes value is only appropriate for the stated layout. A narrow sidebar or a two-column section needs its own values. See MDN's responsive images guide for the selection model.

4. Reserve space before the image arrives

The width and height attributes in the example establish a 3:2 aspect ratio. The responsive CSS allows the image to shrink while keeping that shape. Reserving space helps prevent the content below it from jumping as the image loads.

Use the real proportions of the image. If you intentionally crop a card into a different shape, reserve that shape in the layout and check that important details remain visible.

MDN's image element reference describes how image dimensions help avoid layout shifts.

5. Load the most important image promptly

The example uses loading="lazy" because the photograph is below the initial viewport. Do not apply that attribute indiscriminately to every image.

If an image is the page's Largest Contentful Paint (LCP) element, avoid lazy loading it. Consider fetchpriority="high" for that important image after checking the page. It is a browser hint, not a guarantee, and assigning high priority to many images defeats the purpose.

The LCP element can differ between mobile and desktop layouts. Inspect both before changing priorities. Google's LCP optimisation guidance explains why delaying the main image can undermine other improvements.

6. Write alt text for the image's purpose

For an informative photograph, describe the useful information it adds in this context. Avoid turning the description into a list of services and cities.

A purely decorative image can use alt="". An image that provides the meaning of a link or button needs an alternative that explains its destination or action. A complex diagram may need a fuller explanation in nearby text.

Use the W3C alt text decision tree when the correct treatment is unclear.

7. Test the delivered page, then the enquiry journey

An export folder does not tell you what a visitor actually downloads. Check the published or staging page after the changes:

  • In browser developer tools, inspect the image request URL, transferred size and dimensions.
  • Test a narrow viewport and a desktop layout with the same cache and network settings when comparing versions.
  • Inspect sharpness, crop and any text inside the image at its normal display size.
  • Watch for movement around images during loading.
  • Repeat performance measurements; a single faster run is weak evidence.
  • Confirm that key photos still load and that image links work.

Keep a short change log: page, image, previous file, replacement file and observation. For example: “Service page project photo: replaced the single original with three responsive versions; checked mobile crop and loading.” Add measured numbers only after testing.

Then complete the visitor's task. Follow the service link and send a test enquiry using the contact form checklist. Image performance is useful when the rest of the journey works too.

Salestudia is a digital marketing agency based in Idstein, Germany, working with businesses across Germany. Our website development services bring page structure, mobile presentation and the path to an enquiry into the same project.

About the author

  • I work on SEO, website structure, content and AI-assisted workflows at Salestudia, a digital marketing agency based in Idstein, Germany. Here I share practical guides on web development, Shopify, technical SEO and analytics for small businesses.

No comments yet. Be the first to comment.

More from this blog