What Image Size Should You Use on a Business Website?

By Dave TanguayPublished Updated Editorial draft

Quick Answer

The right website image size depends on its rendered width, crop, screen density and role on the page. Prepare suitable dimensions and responsive variants, then compare compression and visual quality. Give a prominent loading image different treatment from images farther down the page. There is no single pixel width or kilobyte limit that suits every business website image.

An image can look small on a phone while the browser downloads a much larger source file. Another can have a small file size but look blurred or crop out the part a visitor needs to see. Review the displayed result and the delivered resource together.

Keep a good-quality original for future crops and exports. Prepare delivery files for their intended use, then check the actual page rather than assuming that an upload setting controls every image on the site.

Start with the rendered size and crop

Find the space the image occupies at the site’s main layouts. A full-width banner, an article illustration and a product thumbnail have different requirements. Record the displayed width, intended proportions and any mobile crop.

For an illustrative example, suppose an article image occupies a 720 CSS pixel column on desktop. A 720-pixel-wide candidate may suit a display at one device pixel per CSS pixel, while a higher-density display may benefit from a larger candidate. A narrow phone layout may need a smaller delivered version. These example dimensions describe a layout decision, not a universal export rule.

Choose the crop deliberately. A landscape photograph may work in a wide banner but lose its subject in a square card. Sometimes a different crop of the same source is useful; sometimes a different image communicates more clearly. Preview faces, products, labels and other meaningful details at the smallest display size.

Set image dimensions or an appropriate aspect ratio in the layout so space can be reserved before the file arrives. Avoid baking essential page copy into a picture. Use an HTML heading or caption for text that visitors need to read.

How do responsive image sizes work?

Responsive image delivery gives the browser candidate files and information about how the image will be displayed. With width-based markup, srcset identifies available image widths and sizes describes the expected display slot. The browser considers those hints and conditions such as pixel density when choosing a resource.

MDN’s responsive-images guide explains resolution switching and art direction. Resolution switching supplies different sizes of the same composition. Art direction supplies a different crop or composition for a layout, commonly through the picture element.

Several files in a media library do not establish that the browser receives useful responsive markup. A custom template, a background image or an inaccurate sizes value can change what is downloaded. Inspect the delivered page to see which candidate the browser selected.

Choose a format and compare compression

Try an appropriate modern format such as WebP or AVIF for photographic and illustrated assets, while checking the delivery system and browsers you support. SVG can suit carefully prepared vector artwork. Keep a format that preserves the detail or transparency the image needs.

Export comparable versions and inspect them at the size visitors will see. Check edges, small product details, gradients and any text that must remain in a genuine screenshot. Lossy compression can save bytes while introducing visible artifacts; lossless encoding can preserve detail at a different file cost.

The web.dev image-performance guidance recommends balancing visual quality and file size for the actual image. A fixed quality-slider value will not produce the same result for a detailed photograph and a flat illustration. MDN’s image-format guide describes format capabilities and delivery considerations.

Set a practical performance budget from the page’s needs and measurements. An important product detail may justify a different file size from a decorative thumbnail. Re-export an unnecessarily large source before adding another optimization plugin.

Treat the main loading image carefully

A prominent image can be the page’s Largest Contentful Paint, or LCP, element. Identify the actual element in a performance test; the largest-looking image is not guaranteed to be the measured one.

Google’s LCP optimization guidance advises against lazy-loading the LCP image because that delays its request. Ensure the browser can discover the important image early. A developer may use a suitable fetch-priority hint where the measured page benefits.

Images farther down the page may be suitable for lazy loading. Check that they appear as visitors reach them, that reserved space prevents disruptive movement, and that the loading behavior works in the implemented template. Marking every image high priority can make resources compete instead of clarifying which one needs attention.

For a broader investigation, our website speed and Core Web Vitals guide separates resource delivery from other causes of slow pages.

What should you check in WordPress?

WordPress can generate image sizes and responsive markup for media-library images. Its responsive-images documentation explains that behavior. The actual result depends on the image, available generated files, theme, builder and any optimization or delivery layer.

Review the rendered img element, its candidate URLs and the selected resource. Confirm that those files exist and that the displayed image keeps its intended proportions. CSS background images require their own delivery review; they do not automatically behave like a normal responsive image element.

Test after changing a theme or builder layout. A wider image column may need different candidates or display-size hints. Regenerating thumbnails or changing optimization settings should be a planned maintenance task, with a backup and checks for affected pages.

A practical image review checklist

  1. Identify the image’s purpose and the information it must preserve.
  2. Measure its display slot and review the crop at desktop and mobile layouts.
  3. Prepare suitable candidate dimensions from a good-quality source.
  4. Compare format, compression, visible detail and file bytes.
  5. Check the selected resource, dimensions and loading attributes in the browser.
  6. Test a representative mobile condition and confirm that images appear without disruptive shifts.
  7. Write alt text according to the image’s purpose. The W3C alt decision tree helps distinguish meaningful images from those that need empty alt text because they are purely decorative in context.

If the image remains large because it contains dense explanatory text, consider placing that explanation in the article instead. Visitors can then read, resize and search the information without depending on a picture.

Key Takeaways

  • Match dimensions and crops to the real display slot.
  • Responsive candidates and accurate display-size hints help the browser choose a resource.
  • Compare compression by inspecting quality and bytes together.
  • Do not lazy-load the measured LCP image.
  • Verify what the browser downloads after WordPress or layout changes.

Frequently Asked Questions

What pixel width should every website image use?

There is no single width for every image. Start with its rendered slot, crop and expected display density, then supply appropriate candidates and check the selected resource on the page.

Should every image be under a fixed kilobyte limit?

A useful budget depends on the image’s purpose, detail, format and the rest of the page. Compare visible quality and measured delivery cost rather than treating one file-size threshold as an SEO requirement.

Will converting an image to WebP fix a slow page?

It may reduce that image’s transfer size, depending on the source and encoding. Slow delivery, render-blocking resources, scripts and other page conditions can still affect performance.

Should I lazy-load my featured image?

Check its role in the actual layout. If it is the LCP image, lazy loading can delay the page’s main content. A featured image positioned well below the initial view may need different treatment.

A website audit or speed and performance review can identify which images are contributing to a page’s loading work and which template changes deserve attention.

Archives