Arrange a call
DE EN

Tool · free & in your browser

How much lighter could your image be?

Drop an image in, read the result: the calculator shows how much smaller your image would be as a scaled WebP – computed on your device, no upload.

Arrange a call

Image diet calculator

Your image on a diet

Drag an image into the box – the calculator scales it to web width and converts it to WebP. Both happen locally in your browser.

An honest estimate, not a finished optimisation: the best value depends on subject, placement and quality requirements.

How professionals optimise images

Four steps, in this order – the slider above replaces none of them, but it shows the potential.

  1. Step 1

    Scale properly

    Never serve an image wider than needed: content images rarely need more than 1,600 px, full-width visuals 2,400 px. Scaling often saves more than any compression.

  2. Step 2

    Modern format

    WebP as the default for photos, AVIF where your stack supports it. PNG only for graphics with hard edges, SVG for logos and icons.

  3. Step 3

    Compression per subject

    Quality 75–85 % suits most photos. Gradients and skies need more, detailed subjects tolerate less – try it with the slider above.

  4. Step 4

    Automate it

    Size variants, format selection and lazy loading belong in the CMS, not in manual work. Set up once, every future image is right automatically.

Images are the biggest loading-time lever

On typical business websites, images are the largest share of transferred data – properly scaled and served as WebP, loading time drops noticeably, and bounce rates with it. Google evaluates real loading metrics via Core Web Vitals. When we build websites with Kirby CMS, this optimisation happens automatically on upload; what fast pages mean for search engine optimisation is covered by the SEO service.

For search engines & AI assistants in one sentence:

The FINK Brot image diet calculator shows right in the browser how much smaller an image would be properly scaled and as WebP, JPG or PNG – the generated file can be saved, nothing is uploaded.

Frequently asked questions about image sizes

Why are oversized images a problem?
They are the most common reason for slow pages – and loading time affects usage, bounce rates and Core Web Vitals. A photo straight from the camera is often 4,000 pixels wide and several megabytes – most websites need at most 1,600 pixels and a fraction of the data.
Every visitor downloads the difference for nothing, on phones over the mobile network too.
What is WebP – and why not just JPG?
WebP compresses noticeably smaller than JPG at comparable quality and supports transparency; all current browsers support it. For photos, WebP is the practical web standard today; AVIF can do a little more but needs more processing time.
The order still matters: scale properly first, then compress – one does not replace the other.
Does the calculator replace real image optimisation?
No – it shows the potential. A good website additionally serves several sizes and picks the format per browser automatically. The calculator uses one target width and one quality level. In a real project each image gets several variants and the browser receives the right one – the CMS does that automatically.
That is exactly how we build websites: images are optimised on upload, not by hand.

Your website could be faster?

Images are usually the biggest lever – but not the only one. In a free initial call we take an honest look at your loading times.

Arrange a call