Image Compression and Modern Formats for Faster Small Business Sites
Speed matters more than ever for small business websites. Visitors on mobile connections abandon pages that load slowly, and search engines reward fast, well-optimised sites. One of the simplest wins is getting your images under control. This guide explains how image compression and modern formats such as WebP and AVIF can make your local business site noticeably faster.

Why Image Weight Slows Small Business Sites
Images are usually the heaviest assets on a page. A single uncompressed hero photo can weigh several megabytes, which is far too much for a phone on a weak signal. Every extra kilobyte delays the moment a customer sees your phone number, menu or booking button.
Traditional formats like JPEG and PNG were designed for a different era. They still work, but they rarely deliver the smallest possible file. Switching to modern formats and compressing responsibly can cut image weight dramatically without a visible drop in quality.
Choosing Between WebP and AVIF
WebP is widely supported and typically 25–35% smaller than an equivalent JPEG. AVIF goes further, often saving 50% or more, but encoding is slower and very old browsers may not display it. A practical approach is to serve AVIF where possible and fall back to WebP, then JPEG.
The table below summarises the trade-offs for a typical small business site.
| Format | Typical Saving | Browser Support |
|---|---|---|
| JPEG | Baseline | Universal |
| WebP | 25–35% | Excellent |
| AVIF | 50%+ | Good, growing |
For most local businesses, WebP alone is a safe first step. Add AVIF once your content pipeline supports it comfortably. You can also use the <picture> element to offer several sources and let the browser choose.
Sizing Images Correctly
Serving a 3000-pixel image inside a 600-pixel container wastes bandwidth. Always resize images to the largest size they will actually appear, then let CSS handle smaller screens. Use the srcset and sizes attributes so the browser downloads the most appropriate file.
Follow these steps when preparing images:
- Export at the final display dimensions, not camera resolution.
- Compress with a quality setting around 75–85%.
- Provide two or three widths for responsive delivery.
- Check the result on a real mobile device.
Keep a consistent naming convention too, so future updates stay manageable. If you ever change your design, correctly sized source images make the migration far easier.
Lazy-Loading Done Sensibly
Lazy-loading defers off-screen images until the visitor scrolls near them. This speeds up the initial render and reduces data usage. Modern browsers support the loading="lazy" attribute, so implementation is often a one-line change.
Do not lazy-load everything, though. Images above the fold, especially your logo and hero image, should load immediately to avoid layout shifts. A balanced rule is:
- Eager-load the hero and logo.
- Lazy-load gallery, team and blog images.
- Always set width and height attributes.
Fast sites feel trustworthy, and trust turns local visitors into paying customers.
Putting It Into Practice
Start by auditing your homepage with a tool like PageSpeed Insights. Identify the largest images and convert them to WebP first. Then resize anything oversized and add lazy-loading below the fold. These changes often take an afternoon but pay off for months.
If you would rather focus on running your business, a professional web design partner can handle compression, modern formats and performance tuning. Faster pages mean better rankings, lower bounce rates and more enquiries from your local area. Image optimisation is not a one-off task either; build it into your publishing routine so every new photo is compressed before it goes live.
