Back to blog

Image Optimisation for Websites: A Practical Guide

Bakery owner preparing website photos at computer

Image optimisation means sending visitors the smallest image file that still looks sharp at the size it is shown. You do it in four moves: resize the image to the space it fills, compress it, save it in a modern format such as WebP, and load it sensibly. Done properly, pages open faster, phones use less data, and Google’s own guidance says images often make up most of the bytes a page downloads, so they usually offer the biggest savings.

This guide is written for Irish business owners who run a site, or are about to launch one, and want straight answers: which dimensions, which file sizes, which format, and how to check your own pages.

Newbusinesswebsites
Build a Faster Business Website
NewBusinessWebsites.ie creates mobile-friendly websites for Irish businesses, with practical design and local SEO knowledge to support a stronger online presence.
Visit NewBusinessWebsites.ie

TL;DR

  • Resize first, compress second. An image should never be larger than the space it fills on screen, and a photo straight from a phone is usually far larger than any page needs.
  • Use WebP for most photos, with JPEG as the fallback. Keep PNG or SVG for logos, icons and graphics with sharp lines or transparency.
  • Aim for a hero image of roughly 150 KB and most other images well under 100 KB, using the size guide below.
  • Do not lazy-load the main image at the top of the page, but do lazy-load everything below the fold.
  • Add descriptive file names and alt text. They help accessibility and help search engines understand the image.

Table of Contents

Why images matter more than most business owners expect

A typical small business site is built around photos: the van, the team, finished jobs, the shopfront. Those photos are often the heaviest thing on the page. When they are oversized, a visitor on a mobile connection in rural Ireland waits longer, and some leave before the page appears.

Speed is also something Google measures. One of its Core Web Vitals is Largest Contentful Paint (LCP), the time it takes for the biggest visible element to appear, which on many business sites is the hero image. Google’s web.dev guidance says sites should aim for an LCP of 2.5 seconds or less, measured at the 75th percentile of page loads. If you want the wider picture, our plain guide to Core Web Vitals covers all three metrics without jargon.

Optimised images also help your pages in image search, and they make your site feel more professional. Nobody trusts a site where the top banner loads in slowly, line by line.

Step 1: Get the dimensions right

The most common mistake is uploading an image far larger than the space it occupies. Chrome’s guidance is clear that a page should never serve images larger than the version shown on screen, because the extra bytes only slow things down.

Step 1: Get the dimensions right

The rule of thumb from web.dev: an image shown in a 500 by 500 pixel container needs to be 500 by 500 pixels on a standard screen. On a high-density screen (device pixel ratio of 2) it should be 1000 by 1000, and at a ratio of 3 it should be 1500 by 1500. Most business sites do not need to go beyond 2x.

In practice, that gives you these working sizes. They are sensible starting points rather than official standards, and they sit in line with a published WordPress sizing guide that suggests a full-width hero of 1920 x 1080 pixels under 150 KB, a boxed hero of 1200 x 630 pixels under 100 KB, and a 150 x 150 pixel thumbnail under 15 KB.

Where the image sits Suggested dimensions (pixels) Target file size Best format
Full-width hero banner 1920 x 1080 Up to about 150 KB WebP (JPEG fallback)
Boxed hero or blog header 1200 x 630 Under about 100 KB WebP or JPEG
Content photo in a service page 800 to 1200 wide 50 to 100 KB WebP or JPEG
Team or service thumbnail 150 x 150 to 300 x 300 Under about 15 to 30 KB WebP or PNG
Logo About 250 x 100 Under about 15 KB SVG or PNG
Social sharing image 1200 x 630 Under about 100 KB JPEG or PNG

Two practical points. First, never scale a small image up: it gets blurry and the file does not get any better. Second, crop to the shape you need before you upload, so the browser is not carrying pixels that are hidden.

What about phones?

A 1920 pixel wide image is wasted on a phone that shows it at about 400 pixels wide. This is what responsive images solve: you provide several widths and the browser picks the best one. Chrome recommends using srcset and sizes for exactly this reason. Good website platforms generate these versions automatically. If yours does not, three widths (for example 480, 960 and 1600 pixels) cover most layouts.

Responsive image widths matched to screens

Step 2: Compress without ruining the picture

Compression comes in two kinds. Lossy compression throws away some detail the eye barely notices and works best on photographs. Lossless compression shrinks the file with no loss of data and suits formats such as PNG, WebP and AVIF in lossless mode. Lossy works less well on line art and text, where sharp edges show artefacts.

For JPEG photos, Google’s PageSpeed documentation recommends reducing quality to 85 if it was higher, because above that the file grows quickly while the visible improvement is small. For a simple starting point, MDN suggests compressing with MozJPEG at quality 75 and then trying WebP or AVIF.

A simple routine for a non-technical owner:

  1. Resize the photo to the dimensions in the table above.
  2. Export it as WebP, or JPEG at a quality of 75 to 85.
  3. Check the file size. If a content photo is still over 150 KB, lower the quality a little or crop it tighter.
  4. Look at it on a phone and on a laptop. If you cannot see a difference from the original, you are done.

There are plenty of free compression tools that run in your browser, and most website builders compress on upload. Treat any automatic setting as a starting point and still check the result on your key pages.

Step 3: Choose the right format

This is where most readers get stuck, so here is the short version.

WebP vs JPEG

WebP files are usually 25 to 35 per cent smaller than equivalent JPEG and PNG files, and WebP supports both lossy and lossless compression. It also supports transparency even when lossy, which JPEG cannot do. Chrome’s documentation confirms that WebP is supported by all major browsers, so for a business website in 2026 it is a safe default for photos.

Keep a JPEG fallback where your platform or an older system needs one. Email newsletters, some print workflows and certain upload forms still prefer JPEG.

What about AVIF?

AVIF is newer and often smaller again. web.dev notes tests showing savings of more than 50 per cent compared with JPEG in some cases, and Chrome says it is supported in the latest version of all major browsers. The catch is practical rather than technical: AVIF files are less convenient to open, edit and share on your computer. If you receive an AVIF and need to use it somewhere that does not accept it, you can convert AVIF files to PNG with a free online tool.

Quick format guide

Image type Use Why
Photographs WebP (or AVIF), JPEG fallback Smallest files at good quality
Logos and icons SVG, or PNG Stay sharp at any size
Screenshots with text PNG or lossless WebP Text stays crisp
Images needing a transparent background WebP or PNG JPEG cannot do transparency
Animations Short video or animated WebP Far smaller than GIF

The Nottinghamshire County Council guide, written for people who publish web content rather than developers, makes the same point: save images that need transparency or have sharp lines as PNG, and do not scale up small images.

Step 4: Load images in the right order

Good files still load slowly if the page asks for them badly. Three habits matter most.

Lazy-load below the fold. MDN recommends the loading=“lazy” attribute for images that are not visible on screen when the page opens. They load only as the visitor scrolls towards them, which saves data and speeds up the first view.

Never lazy-load the hero. The big image at the top is usually your LCP element. Delaying it works against you. Load it straight away, and if you or your developer are comfortable with it, give it a high fetch priority so the browser fetches it first.

Set width and height. Declaring dimensions in the page code reserves the space before the image arrives, so text does not jump around as the page loads. That jumping is what Cumulative Layout Shift measures.

If your site has many images, an image CDN (a network that serves files from a server near the visitor) can help further. Chrome’s guidance lists it alongside modern formats and responsive sizes as a way to cut download time.

Step 5: Name and describe your images

Optimisation is not only about weight. Google’s image guidance recommends using standard HTML image elements so crawlers can find your images, and writing useful alt text so that people using screen readers, and search engines, understand what is shown.

A few simple rules:

  • Name the file for what it shows: kitchen-extension-cork.webp beats IMG_4821.webp.
  • Write alt text that describes the image the way you would to someone on the phone: “Electrician fitting a new consumer unit in a Galway home”.
  • Leave alt text out of purely decorative images, and do not stuff it with keywords.
  • Put the image near the text it relates to. Context helps search engines understand it.

For tradespeople and local firms, real photos of your own work, with accurate names and alt text, help far more than stock images. They also support the local pages we describe in our guide to location page SEO.

How to check whether your images are optimised

You do not need to be a developer to audit your site. Try this 15-minute check:

  1. Run your homepage through PageSpeed Insights. Look for the image-related opportunities, such as properly sized images, next-gen formats and deferred offscreen images.
  2. Identify your LCP element. The report tells you which element it is. On most small business sites it is the hero image.
  3. Check file sizes. In your website’s media library, sort by size. Anything over 300 KB on a content page deserves a second look.
  4. Test on mobile. Open the site on your phone on mobile data, not Wi-Fi, and note how long the top of the page takes to appear.
  5. Check alt text. Open a few key pages and see whether images have meaningful descriptions.

This fits neatly into a regular routine. Our website maintenance checklist shows how to fold checks like these into 45 minutes.

Common mistakes we see

  • Uploading photos straight from a phone or camera. These are often several megabytes and thousands of pixels wide.
  • Using PNG for photographs. PNG is lossless, so photos saved this way are much bigger than they need to be.
  • Compressing too hard. Blurry or blocky images undermine trust as much as slow ones. Use the quality range above rather than the lowest setting.
  • Using images instead of text. A banner with your phone number baked into the picture cannot be read by search engines or screen readers. Keep key text as real text.
  • Forgetting old images. Redesigns and new pages often leave heavy files behind in the media library.
  • Ignoring the hero. One oversized hero image can outweigh the rest of the page put together.

Our perspective

Most of the sites we see for new Irish businesses are not slow because of anything exotic. They are slow because nobody told the owner that the 4 MB photo from their phone does not belong on a homepage.

We build websites to be fast, mobile-friendly and easy to use, and image handling is part of that thinking from the start: sensible dimensions, modern formats, and photos that show your real work. A site that loads quickly and looks credible does more for a plumber, a hairdresser or a start-up than any clever feature.

Our approach is to keep this jargon-free. You deal directly with the person building your site, you get a fixed quotation, and you do not need to learn what a device pixel ratio is. Add monthly website care on top, and the images you add later get looked after as well, rather than quietly bloating the site over the next two years.

If you take one thing from this guide, make it this: resize before you upload, and never lazy-load the first image people see.

niall

Need a site that is fast from day one?

If you are starting out, or your current site is slow and dated, we can build it properly from the start. Our Launch Website is €499 one-off, the Business Website is €799 one-off, and the Growth Website is from €1,295 one-off. Monthly care starts at €29 per month with Website Care. See what is included on our pricing page.

Newbusinesswebsites

Already have a site that needs a refresh? Our website redesign service for Irish businesses covers rebuilding slow, outdated pages, and our Core Web Vitals guide explains the speed measures behind it.

FAQ

What is the best image size for a website?

There is no single size, because it depends on where the image sits. A full-width hero is commonly 1920 x 1080 pixels at around 150 KB or less, a boxed header 1200 x 630 pixels, and a thumbnail 150 x 150 pixels. The principle is that the image should match the space it fills, with a larger version for high-density screens.

Is WebP better than JPEG?

For most website photos, yes. WebP files are usually 25 to 35 per cent smaller than comparable JPEGs, and WebP works in all major browsers. JPEG remains useful as a fallback and for email, print and upload forms that do not accept WebP.

How do I compress images for my website?

Resize the image to the size it will be displayed, then export it as WebP or as a JPEG at quality 75 to 85. Most website builders and free browser-based tools can do this in a few clicks. Compare the result with the original on a phone and a laptop before you publish.

Does image optimisation help SEO?

It helps in two ways. Faster pages support better Core Web Vitals scores, and descriptive file names and alt text help search engines understand your images. Google’s image guidance also says to use standard HTML image elements so its crawlers can find them.

Sources

WhatsApp