facebook pixel
6May 2026

How to optimise images for web: boost speed and quality

Web developer reviewing website images at desk


TL;DR:

  • Slow-loading images significantly reduce user patience, conversion rates, and search rankings.
  • Combining format choice, resizing, and compression in a repeatable workflow optimizes website speed and quality.

Slow-loading images are quietly costing you customers. Every extra second it takes for your page to render chips away at user patience, conversion rates, and your standing in search results. The good news is that image optimisation is the highest-impact performance lever available to most SME web teams, and it doesn’t require a developer on retainer. This guide walks you through the exact steps to shrink file sizes, choose the right formats, and serve sharp visuals to every device, without sacrificing the quality your brand deserves.

Table of Contents

Key Takeaways

Point Details
Target file size and display Optimise images to match their exact display size to avoid wasted bandwidth and slow loading.
Choose optimal formats Use modern formats like WebP for most images and reserve PNG for when you need transparency.
Balance compression and quality Pick a compression level where further reductions barely affect visual quality but save on load speed.
Automate and repeat Integrate image optimisation into your publishing pipeline, not just as a one-off task.

Understanding image optimisation: what and why

Image optimisation means reducing the file size of your images while keeping them looking sharp enough for your audience. It sounds simple, but in practice it involves several decisions: the format you choose, the dimensions you export, and how aggressively you compress each file. Get even one of these wrong and you’re leaving real performance gains on the table.

Why does this matter so much for your site specifically? Because images can exceed 75% of total page weight, making them the single biggest drag on load speed. That directly affects your bounce rate, your SEO performance, and ultimately your revenue. Google’s Core Web Vitals, particularly Largest Contentful Paint (LCP), are heavily influenced by how quickly your hero image or product photo loads. A slow LCP score can push your site down in search rankings before a visitor even sees your content.

The three major levers you control are:

  • Format: The container that holds your image data. Modern formats like WebP and AVIF are far more efficient than older JPEG or PNG files.
  • Dimensions: The pixel width and height of your image. Serving a 3,000px wide image in a 600px container is pure waste.
  • Compression: The degree to which image data is reduced. Too little and files stay bloated; too much and quality degrades visibly.

For truly effective results, combine all three optimisations rather than relying on just one. Changing format alone, or compressing without resizing, often underdelivers. Here’s how these three levers interact across common image types:

Image type Recommended format Typical compression quality Resize to display dimensions?
Hero banners WebP or AVIF 75 to 85% Yes, critical
Product photos WebP 70 to 80% Yes
Logos and icons SVG or PNG Lossless Match display size
Background textures WebP 60 to 75% Yes
Photography with text WebP or AVIF 75 to 85% Yes

Common pitfalls include uploading straight from a camera at full resolution, sticking with PNG for photographs (where JPEG or WebP is far more efficient), and over-compressing until images look pixelated. Each of these is easy to avoid once you know what to look for, and addressing them will deliver measurable website speed improvements almost immediately.

What you need before starting: checklist for SME teams

Before you start resizing and compressing, make sure you have the right tools and assets in place. The best optimisation workflow is one you can repeat consistently, not a frantic one-off scramble before a site launch.

Here’s a practical checklist to run through:

  • Original, high-resolution source files: Always work from your originals, not from already-compressed exports. Re-compressing a compressed file degrades quality faster than most people expect.
  • Image editing software: Adobe Photoshop, Affinity Photo, or the free alternative GIMP all allow precise control over format, dimensions, and compression. For batch processing, tools like ImageOptim (Mac), Squoosh (browser-based), or Sharp (Node.js library for developers) are excellent.
  • CMS plugins: If you use WordPress, plugins like ShortPixel or Imagify automate much of this process on upload. Many modern CMS platforms include built-in optimisation, so check your settings before adding a plugin.
  • Knowledge of srcset and the picture element: These HTML features allow you to serve different image sizes to different devices. A smartphone doesn’t need a 1,400px wide image; serving it one wastes the user’s data and slows their experience.
  • A CDN (Content Delivery Network): Serving images from a CDN geographically close to your user reduces latency significantly. Cloudflare, Fastly, and AWS CloudFront are popular choices.

A practical approach for SME teams is to adopt responsive delivery using HTML’s "srcsetandsizesattributes (or the` element) so each device downloads an appropriately sized image, with modern format fallbacks in place for older browsers.

Understanding when to use each format is equally important:

Format Best use case Transparency support Browser support
JPEG Photos, complex imagery No Universal
PNG Logos, graphics needing transparency Yes Universal
WebP Photos and graphics, modern sites Yes Near-universal
AVIF Highest compression, future-proof Yes Growing rapidly
SVG Icons, logos, illustrations Yes Universal

Pro Tip: Before touching a single image, do a quick audit of your current site using PageSpeed Insights. It will flag specific images that are oversized or in outdated formats, giving you an instant priority list rather than a guessing game. This audit can also feed directly into any website redesign strategies you’re planning, since image performance is closely tied to brand visual identity decisions about hero layouts and page structure.

How to optimise images: step-by-step process

Now you’re ready to jump into the optimisation itself. Here’s how to do it, step by step, with SME-oriented tips at each stage.

  1. Choose the right format. For most web imagery in 2026, WebP is your default. WebP substantially reduces file size compared to JPEG and PNG at comparable visual quality. If your audience uses cutting-edge browsers and you want the absolute best compression, AVIF goes even further. Reserve PNG strictly for images that need lossless quality or complex transparency (such as logos on varied backgrounds). Use SVG for any scalable graphics, logos, or icons.

  2. Resize to actual display dimensions. This is one of the most commonly overlooked steps. Serving images larger than their display size wastes bandwidth and slows page loads without any visible benefit to the user. If your blog post column is 780px wide, export your image at 780px (and at 1,560px for retina screens, which you’ll serve via srcset). Don’t rely on CSS to scale images down; that still forces the browser to download the full file first.

  3. Compress at the sweet spot. Export quality around 75 to 85% for WebP delivers excellent results for photographs. Raising quality toward maximum often yields no visible improvement but meaningfully inflates file size. Use Squoosh or your image editor’s export preview to compare the before and after at various quality levels. Stop reducing quality as soon as you can visually detect degradation on a normal-sized screen.

  4. Implement srcset and sizes in your HTML. This tells the browser which image to download based on the user’s screen. Here’s a simplified example of the pattern:

<img src="hero-780w.webp" srcset="hero-780w.webp 780w, hero-1560w.webp 1560w" sizes="(max-width: 800px) 780px, 1560px" alt="Descriptive alt text here">

This single addition can eliminate a large proportion of wasted bandwidth on mobile devices, which often make up the majority of your site traffic.

  1. Add format fallbacks for older browsers. Use the <picture> element to serve AVIF to browsers that support it, WebP to those that don’t, and JPEG as a final fallback. This ensures no user sees a broken image, regardless of their browser version.

  2. Write descriptive alt text for every image. Alt text serves two purposes: it helps screen readers describe images to visually impaired users, and it signals relevance to search engines. This is a key part of SEO image best practices and can meaningfully improve your image search visibility. Never leave alt text blank on meaningful images. Keep it concise, accurate, and relevant to the page content.

Pro Tip: Improving your image workflow is also directly tied to improving conversions. Faster-loading pages with high-quality images consistently outperform slow, bloated ones in A/B tests, especially on mobile.

Testing, verification, and common pitfalls

Infographic showing step-by-step image optimisation workflow

Once you’ve optimised your images, how do you confirm it worked? Here’s how to test, verify, and avoid rolling back your improvements by accident.

Start with a before-and-after comparison. Record your key page’s load time, LCP score, and total page weight before you make changes, then re-test after. Use these tools:

Analyst comparing before and after website load times

Tool What it measures Best used for
Google PageSpeed Insights Core Web Vitals, image-specific flags Quick audits, before/after checks
Chrome DevTools Network tab Individual file sizes, load timing Diagnosing specific slow images
WebPageTest Full waterfall, CDN validation Deeper, multi-location testing
Lighthouse (built into Chrome) LCP, CLS, overall performance score Comprehensive site health review

Watch carefully for these common pitfalls after optimisation:

  • Blurry images on high-resolution screens. If you’ve only provided a 1x image and a retina user visits your site, the browser will scale it up and it will look soft. Always include 2x variants via srcset.
  • Missing fallback formats. If you’ve switched everything to AVIF without a WebP or JPEG fallback, older browsers may display nothing. Test across browser versions, not just your own.
  • Broken or missing alt text. If your CMS replaces images during a bulk operation, check that alt text has been preserved. This is both an SEO and image workflow concern and an accessibility legal requirement in many jurisdictions.
  • CMS re-uploading at original size. Some CMS platforms revert images to their original dimensions on update. Set your CMS to use only the optimised versions, or lock down upload settings.

Building a repeatable process is where the real long-term gains live. Moving from one-off optimisation to a repeatable pipeline that includes resizing, converting, generating device variants, and serving through a CDN with caching means your gains compound over time rather than eroding as new content is published.

One-and-done image optimisation is a myth: what really works

Here’s an uncomfortable truth we’ve seen play out with countless SME sites: a team spends an afternoon optimising every image on the site, sees a satisfying jump in PageSpeed scores, and then watches those scores quietly slide back down over the next three months as new blog posts, product shots, and banner updates go live with unoptimised files. The one-off approach solves yesterday’s problem, not tomorrow’s.

The most effective teams treat image optimisation the same way they treat backups or software updates: as routine hygiene, not a heroic intervention. Building a repeatable pipeline that automatically resizes, converts, and caches images as part of your publishing workflow is the real differentiator. Tools like Cloudinary, Imgix, or even a well-configured CDN with on-the-fly transformations can handle this automatically, so your editors and content managers never have to think about it.

What does this look like in practice? It means setting your CMS to enforce maximum upload dimensions. It means running a batch optimisation script as part of your deployment process. It means using consistent redesign strategies that account for image performance from the outset, rather than bolting it on afterwards. It means making image optimisation a checkbox in your content publishing checklist, not a project that lives on the backlog.

We’d argue this workflow shift is more valuable than any individual technical tweak. A site with average compression but a robust, automated pipeline will outperform a perfectly optimised site where no one has a process, six months down the line. That’s the mindset shift that separates sites that sustain strong performance from those that yo-yo between audits.

Take your site further with expert web optimisation

Image optimisation is powerful, but it’s one piece of a broader performance puzzle. For SME teams managing complex sites, e-commerce catalogues, or fast-growing content libraries, sustaining these gains at scale is genuinely challenging without the right infrastructure and expertise.

https://www.brainiacmedia.net/contactus/

Brainiac Media’s web development agency team works with SMEs and growing businesses to build performance into every layer of your site, from image delivery pipelines to core architecture. Our website development solutions include responsive design, CDN integration, and ongoing technical support so your site stays fast as your content grows. And if you want to tie web performance into a broader growth strategy, our digital marketing support team can connect the dots between speed, SEO, and conversion. Get in touch for a free consultation and let’s build something that performs.

Frequently asked questions

What is the best image format for websites in 2026?

Use WebP for most imagery, as it reduces file size versus JPEG at comparable quality, and provide a JPEG fallback for older browsers. Reserve PNG only for transparency or lossless requirements.

How can I tell if my images are too big for web?

Run your page through PageSpeed Insights or Chrome DevTools; if images exceed their display size, they’re costing you bandwidth and load time without any visual benefit to the user.

Does optimising images affect SEO?

Yes, significantly. Faster pages score better in Core Web Vitals assessments, and search engines reward speed. Always retain meaningful alt text on every image for accessibility and image search visibility.

How often should I check my site images for optimisation?

Review after every major content update or site change, and ideally move to a repeatable pipeline so checks happen automatically as part of your publishing workflow.

Is compressing images more important than resizing?

Neither should be skipped. Doing only one often underdelivers; combining resizing, format conversion, and compression gives you the compounding savings that make a measurable difference to page load speed.

You'd be Mad to Miss This!
FREE Website & SEO Audit
Claim Yours

Find out how you can get more visitors to your website and boost sales and conversions.