Why Image Optimization Is Critical
Images are the single biggest factor affecting a website's loading time. According to HTTP Archive, images account for an average of 50% of total page weight β and on image-heavy sites like portfolios, e-commerce, or real estate, that figure can reach up to 75%.
This has a direct impact on your business:
- 53% of users abandon a mobile page that takes longer than 3 seconds to load (Google study)
- Every additional second of loading time reduces the conversion rate by 7% (Akamai)
- Google uses Core Web Vitals β particularly LCP (Largest Contentful Paint) β as a ranking factor
- Slow pages have a higher bounce rate and lower time on site
In our daily work as a web design agency in Vienna, we see the same pattern time and again: companies invest thousands of euros in a beautiful design but upload 5 MB images straight from the camera. The result: a stunning website that nobody sees because it loads too slowly.
The Numbers Speak for Themselves
| Metric | Without Optimization | With Optimization | Improvement |
|---|---|---|---|
| Page Weight | 8β15 MB | 1β3 MB | 70β80% |
| Load Time (3G) | 12β25 seconds | 3β5 seconds | 60β75% |
| LCP Score | > 4 s (poor) | < 2.5 s (good) | Core Web Vital passed |
| Bounce Rate | 45β65% | 20β35% | 25β40% less |
| PageSpeed Score | 30β50 | 85β100 | Significant improvement |
If you test your website with our website design tool, you will quickly see whether images are a problem. In most cases, image optimization is the fastest path to better Core Web Vitals β often the PageSpeed Score can be improved by 20β40 points through image optimization alone.
Performance and SEO Are Interconnected
Google officially introduced Core Web Vitals as a ranking factor in 2021. This means: slow images cost you not only visitors but also search engine rankings. The LCP value in particular is often determined by a large hero image or banner. If that image is not optimized, your entire page fails the LCP test.
Read more in our detailed guide on optimizing Core Web Vitals.
Image Formats Compared: WebP, AVIF, PNG, JPG, SVG
Choosing the right image format is the first and most important step in image optimization. Each format has its strengths and weaknesses β and the right use case.
JPEG (JPG) β The Classic
JPEG has been the standard format for photos on the web for over 30 years. It uses lossy compression β meaning minimal details are lost with each save.
Advantages:
- Universal browser support (100%)
- Good compression for photos
- Small file size at acceptable quality
Disadvantages:
- No transparency
- Quality loss with repeated saves
- Not ideal for text, graphics, or sharp edges
- Larger than WebP at the same quality
Best Practice: Set JPEG quality to 75β85%. The difference from 100% is barely noticeable to the naked eye, but file size drops by 50β70%.
PNG β For Transparency and Graphics
PNG uses lossless compression and supports transparency (alpha channel). This makes it ideal for logos, icons, and graphics with text.
Advantages:
- Lossless quality
- Transparency (alpha channel)
- Ideal for graphics, screenshots, text
Disadvantages:
- Significantly larger files than JPEG or WebP for photos
- No animation (APNG exists for that)
Best Practice: Use PNG only for graphics with transparency or sharp edges. For photos, PNG is almost always the wrong choice.
WebP β The Modern Standard
WebP was developed by Google and offers 25β35% smaller files than JPEG at comparable quality. It supports both lossy and lossless compression as well as transparency.
Advantages:
- Significantly smaller files than JPEG and PNG
- Transparency support
- Lossy and lossless compression
- 97% browser support (as of 2026)
Disadvantages:
- Older Safari versions (< 16) do not support WebP
- Quality loss at very low quality levels is more visible than with JPEG
Best Practice: Use WebP as the default format for all photos and complex graphics. Offer JPEG as a fallback in the picture element.
AVIF β The Future
AVIF is the newest image format and is based on the AV1 video codec. It offers up to 50% better compression than JPEG and significantly outperforms WebP as well.
Advantages:
- Best compression of all current formats
- HDR and wide color gamut support
- Transparency and animation
- 92% browser support (as of 2026)
Disadvantages:
- Longer encoding time (CPU-intensive)
- Not yet universal support
- Maximum image size is limited with some encoders
Best Practice: Use AVIF as the first choice in the picture element, WebP as fallback, JPEG as the last fallback.
SVG β For Vector Graphics
SVG is a vector-based format that scales infinitely without quality loss. Perfect for logos, icons, illustrations, and diagrams.
Advantages:
- Infinite scalability
- Extremely small file sizes for simple graphics
- CSS-animatable and manipulable via JavaScript
- Text-based β ideal for SEO
Disadvantages:
- Not suitable for photos
- Complex SVGs can become very large
- Security risks with user uploads (embedded JavaScript)
The Comprehensive Comparison Table
| Format | Compression | Transparency | Animation | Browser Support | Ideal For |
|---|---|---|---|---|---|
| JPEG | Lossy | No | No | 100% | Photos (legacy) |
| PNG | Lossless | Yes | No (APNG) | 100% | Graphics with transparency |
| WebP | Both | Yes | Yes | 97% | Photos and graphics (standard) |
| AVIF | Both | Yes | Yes | 92% | Photos (best quality per size) |
| SVG | Vector | Yes | CSS/SMIL | 100% | Logos, icons, illustrations |
| GIF | Lossless (256 colors) | Yes (1-bit) | Yes | 100% | Simple animations (avoid) |
GoldenWing's recommendation: Use the picture element with AVIF, WebP, and JPEG as a fallback chain. This way, all users automatically receive the best possible variant.
Implementing Responsive Images Correctly
Loading a 4K hero image on a smartphone is a waste of resources. Responsive images ensure that each device only receives the appropriate image size.
The srcset Attribute
With srcset, you define different image sizes, and the browser automatically selects the appropriate one:
<img
src="hero-800.webp"
srcset="hero-400.webp 400w,
hero-800.webp 800w,
hero-1200.webp 1200w,
hero-1600.webp 1600w"
sizes="(max-width: 600px) 100vw,
(max-width: 1200px) 50vw,
33vw"
alt="Modern web design portfolio on various devices"
loading="lazy"
/>
Explanation:
- srcset lists the available image widths
- sizes tells the browser how wide the image will be in the layout
- The browser automatically calculates which image size is optimal (taking pixel density into account)
The picture Element for Format Fallbacks
The picture element combines format selection with responsive sizes:
<picture>
<source type="image/avif"
srcset="hero-400.avif 400w, hero-800.avif 800w, hero-1200.avif 1200w"
sizes="(max-width: 768px) 100vw, 50vw" />
<source type="image/webp"
srcset="hero-400.webp 400w, hero-800.webp 800w, hero-1200.webp 1200w"
sizes="(max-width: 768px) 100vw, 50vw" />
<img src="hero-800.jpg" alt="Responsive web design project"
width="1200" height="630" loading="lazy" decoding="async" />
</picture>
We use this pattern in all web design projects to ensure maximum performance with the best image quality. A fundamental understanding of responsive design is essential here.
Which Image Sizes to Generate?
For most websites, we recommend the following breakpoints:
| Usage | Image Widths | Suitable For |
|---|---|---|
| Thumbnails | 150, 300 px | Preview images, card views |
| Content images | 400, 800, 1200 px | Blog images, products |
| Hero/Banner | 800, 1200, 1600, 2000 px | Full-width header images |
| Background | 1200, 1920, 2560 px | Fullscreen backgrounds |
Tip: Do not generate more than 4β5 variants per image. Each additional variant costs storage space and build time but yields diminishing returns.
Lazy Loading: Load Images Only When Needed
Lazy loading delays the loading of images until they become visible in the viewport. This drastically reduces initial load time, especially on long pages with many images.
Native Lazy Loading (The Simple Solution)
Since 2020, all modern browsers support native lazy loading via the loading attribute:
<!-- Images below the viewport -->
<img src="image.webp" loading="lazy" alt="Description" width="800" height="450" />
<!-- Hero image: Do NOT lazy load! -->
<img src="hero.webp" loading="eager" fetchpriority="high" alt="Hero" width="1600" height="900" />
Important Rules:
- Above-the-fold images always use loading="eager" or no loading attribute at all
- LCP image should additionally have fetchpriority="high"
- Always specify width and height to prevent layout shifts (CLS)
- No lazy loading libraries needed anymore β the native solution is sufficient
Intersection Observer (For Special Cases)
When you need more control (e.g., for background images or video posters), use the Intersection Observer:
const observer = new IntersectionObserver((entries) => {
entries.forEach(entry => {
if (entry.isIntersecting) {
const img = entry.target;
img.src = img.dataset.src;
observer.unobserve(img);
}
});
}, { rootMargin: '200px' });
document.querySelectorAll('img[data-src]').forEach(img => observer.observe(img));
The rootMargin of 200px ensures that images are loaded 200 pixels before they become visible β so the user never sees an empty image.
Placeholder Strategies
While an image is loading, no empty space should appear. The best strategies:
- Blur-Up (LQIP): A tiny, blurred preview image (under 1 KB) that is replaced by the sharp image once loaded. The Next.js Image Component does this automatically.
- Dominant Color: The background color of the image as a placeholder. Fast to compute, visually pleasant.
- Skeleton Loading: Animated gray placeholder shapes. Modern and familiar from social media apps.
At GoldenWing, we use Blur-Up with Next.js Image, which provides the ideal combination of performance and UX. This is a core component of our web app development.
Image CDN: Cloudflare, imgix, Cloudinary
A Content Delivery Network (CDN) stores your images on servers worldwide and delivers them from the nearest location. For images, there are specialized CDNs that additionally offer automatic optimization.
Cloudflare Polish and Image Resizing
Cloudflare is already in use as a CDN for many websites. Image optimization is available as an additional feature:
- Polish: Automatic compression of all images (lossless or lossy)
- WebP conversion: Automatic for supported browsers
- Image Resizing: On-the-fly image resizing via URL parameters
- Price: Included in the Pro plan ($20/month)
Advantage: No code changes needed β Cloudflare optimizes all images automatically.
Cloudinary β The All-Rounder
Cloudinary offers the most comprehensive image transformations of all providers:
- Automatic format detection (f_auto delivers AVIF/WebP/JPEG depending on browser)
- Automatic quality (q_auto selects optimal quality)
- Responsive breakpoints are automatically generated
- AI-based cropping (g_auto detects the subject)
Price: Free tier with 25 credits/month, then from $89/month.
imgix β For Enterprise
imgix is the premium provider for image-heavy websites:
- Extremely fast processing
- Over 100 URL parameters for transformations
- Automatic format detection
- Excellent documentation
Price: From $100/month, calculated per origin image.
Which CDN Is Right for You?
| Criterion | Cloudflare | Cloudinary | imgix |
|---|---|---|---|
| Price (entry) | $20/month | $0 (free tier) | $100/month |
| Automatic formats | Yes (WebP) | Yes (AVIF, WebP) | Yes (AVIF, WebP) |
| Transformations | Limited | 100+ | 100+ |
| Simplicity | Very simple | Medium | Medium |
| Ideal for | Small/medium sites | All sizes | Enterprise |
For most of our clients, we recommend Cloudflare as CDN plus Next.js Image Optimization for responsive images. Only for very image-heavy projects (e-commerce, photography) do we use Cloudinary.
Alt Text SEO Optimization
Alt texts are doubly important: they make images accessible for screen readers and help search engines understand the image content. Yet they are neglected on most websites.
What Google Says About Alt Texts
Google uses alt texts to:
- Understand the content of the image
- Index images in Google Image Search
- Better grasp the context of the page
- Select featured snippets with images
Rules for Perfect Alt Texts
- Describe what is visible in the image β not what you wish were there
- Integrate keywords naturally β no keyword stuffing
- Keep to 80β125 characters β precise but complete
- No filler phrases like "Image of..." or "Photo shows..." β screen readers already announce "image"
- Decorative images receive an empty alt="" (do not omit the alt attribute entirely!)
Good vs. Bad Alt Texts
| Bad | Good |
|---|---|
| "" (missing) | alt="" (for decorative images) |
| "image1.jpg" | "Responsive web design on laptop and smartphone" |
| "Web design Vienna agency web design prices" | "Team meeting at GoldenWing Vienna for website planning" |
| "Image of a website" | "E-commerce website for fashion shop with product filters and shopping cart" |
Good alt texts are an integral part of our SEO content strategy. We optimize them as part of every web design project.
Alt Text Audit: How to Find Missing Alt Texts
Use one of these tools to check your website for missing or empty alt texts:
- Google Lighthouse: Shows missing alt texts directly in the accessibility audit
- Screaming Frog: Crawls all images and lists missing alt texts
- WAVE Browser Extension: Visual accessibility check directly in the browser
Core Web Vitals and Images
The Core Web Vitals are Google's metrics for user experience. Images directly affect two of the three metrics.
LCP (Largest Contentful Paint) β The Most Common Problem Area
LCP measures how long the largest visible element takes to load. In over 70% of cases, this is an image (hero image, banner, product photo).
LCP Optimization for Images:
- Preload the LCP image with a link tag in the head
- No lazy loading for the LCP image
- Set fetchpriority="high" on the LCP image
- Minimize image size: Use WebP/AVIF, set quality to 75β85%
- Use a CDN: Load images from the nearest server
- Inline critical CSS: Avoid render-blocking stylesheets before the LCP image
CLS (Cumulative Layout Shift) β Jumping Layouts
CLS measures how much elements shift during loading. Images without defined dimensions are the most common cause.
CLS Optimization for Images:
- Always specify width and height (or aspect-ratio via CSS)
- CSS aspect-ratio as a modern alternative: aspect-ratio: 16/9
- Use placeholders (LQIP, dominant color) to reserve space
- Do not insert images retroactively that shift the content
Ideal CWV Values
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP | < 2.5 s | 2.5β4 s | > 4 s |
| CLS | < 0.1 | 0.1β0.25 | > 0.25 |
| INP | < 200 ms | 200β500 ms | > 500 ms |
Read the complete guide: Optimizing Core Web Vitals.
Batch Optimization for Large Websites
For websites with hundreds or thousands of images, manual optimization is not an option. Here you need automated processes.
Command-Line Tools
Sharp (Node.js): The fastest image processing tool for Node.js:
const sharp = require('sharp');
const glob = require('glob');
const files = glob.sync('images/**/*.{jpg,jpeg,png}');
for (const file of files) {
const outputWebp = file.replace(/\.(jpg|jpeg|png)$/, '.webp');
await sharp(file)
.resize(1600, null, { withoutEnlargement: true })
.webp({ quality: 80 })
.toFile(outputWebp);
}
ImageMagick: A proven tool for batch processing:
for f in *.jpg; do
cwebp -q 80 "$f" -o "${f%.jpg}.webp"
done
Build Pipeline Integration
For Next.js projects (like those we use at GoldenWing), we recommend the Next.js Image Component, which automatically converts images to WebP/AVIF, generates responsive variants, implements lazy loading, and creates blur-up placeholders.
For WordPress sites, there are plugins like ShortPixel or Imagify that can optimize all existing images in a batch (see also our WordPress SEO guide).
Optimization Checklist for Large Websites
- All images converted to WebP (and AVIF where possible)
- Maximum image width limited to 2000 px
- Responsive srcset for all content images
- Lazy loading for all below-the-fold images
- LCP image with preload and fetchpriority="high"
- Alt texts for all informative images
- width/height or aspect-ratio for all images
- CDN configured for global delivery
- Automatic optimization in the upload process
- Regular audits with PageSpeed Insights
Image Compression: Optimally Balancing Quality vs. File Size
Image compression is a balancing act: too much compression leads to visible artifacts, too little compression results in unnecessarily large files. In this section, we show you how to find the optimal middle ground.
Lossy vs. Lossless Compression
In image compression, we fundamentally distinguish between two approaches:
Lossless Compression:
- Reduces file size without quality loss
- Typical savings: 10β30%
- Formats: PNG (with optimization tools), WebP Lossless, AVIF Lossless
- Ideal for: logos, icons, screenshots, graphics with text
Lossy Compression:
- Removes image information that the human eye barely perceives
- Typical savings: 50β90%
- Formats: JPEG, WebP Lossy, AVIF Lossy
- Ideal for: photographs, background images, hero images
Finding the Optimal Quality Level
Based on our experience with hundreds of web projects, the following quality levels have proven to be the optimal compromise:
JPEG/WebP Quality Settings:
- Hero images and header banners: Quality 80β85% β these images are displayed large and artifacts are quickly noticeable
- Content images in body text: Quality 70β80% β a good compromise for most use cases
- Thumbnails and preview images: Quality 60β70% β at small display sizes, quality differences are barely visible
- Background images with overlay: Quality 50β65% β when a text overlay or gradient covers the image, quality can be significantly reduced
AVIF Quality Settings:
AVIF offers approximately 30β50% smaller files at the same visual quality compared to WebP. The quality settings are therefore slightly different:
- Hero images: Quality 65β75%
- Content images: Quality 55β65%
- Thumbnails: Quality 45β55%
Perceptual Quality Metrics
Instead of blindly relying on percentage values, we recommend using perceptual quality metrics. These measure perceived quality from the perspective of the human eye:
- SSIM (Structural Similarity Index): Values above 0.95 are considered visually identical to the original. Target: at least 0.90 for content images.
- DSSIM (Structural Dissimilarity): The inverse of SSIM β values below 0.015 are barely perceptible.
- Butteraugli: Developed by Google, measures the perceived quality difference. Values below 1.0 are considered imperceptible.
Tools like Squoosh (squoosh.app) from Google allow you to visually compare quality while monitoring file size. For batch processing, we recommend Sharp (Node.js) or libvips, both of which support SSIM-based auto-quality.
Practical Workflow for Optimal Compression
Here is our recommended workflow for image compression:
- Prepare the source image: Always start with the highest possible quality (RAW or uncompressed TIFF/PNG)
- Adjust dimensions: Scale the image to the maximum required resolution (e.g., 1920px width for full-width images)
- Choose format: Photographs β WebP/AVIF, Graphics β PNG/SVG
- Compress: Start at quality 80% and gradually reduce until artifacts become visible
- Review: Compare original and compressed version at 100% zoom
- Create responsive variants: Generate different sizes (320, 640, 960, 1280, 1920px)
Automated Image Optimization in CI/CD Pipelines
Manual image optimization is error-prone and time-consuming. For professional web projects, we recommend integrating image optimization into the automated build process.
Why Automated Image Optimization?
In a typical web project, images are uploaded by different people β editors, designers, developers. Without automated optimization, the following happens:
- An editor uploads a 5 MB JPEG straight from the camera
- A designer exports a PNG at 300 DPI instead of 72 DPI
- A developer forgets to create responsive variants
The result: inconsistent image quality and unnecessarily large files. An automated pipeline prevents these problems.
Build-Time Optimization with Sharp
Sharp is the fastest Node.js library for image processing and is based on libvips. Here is an example of a build-time pipeline:
Configuration Example
A typical setup in a Next.js application uses the built-in image optimizer, which uses Sharp under the hood. The configuration in next.config.js allows you to centrally control formats (WebP, AVIF), quality levels, and device sizes.
For static websites, we recommend a build script with Sharp that performs the following steps:
- Scan all images in the source folder
- Create responsive variants (e.g., 640, 960, 1280, 1920px)
- Generate WebP and AVIF versions
- Automatically optimize quality (SSIM-based)
- Write results to an output folder
CMS-Based Optimization
When images are uploaded via a CMS (WordPress, Payload, Strapi), optimization should occur server-side:
WordPress:
- ShortPixel or Imagify: Compress images automatically on upload
- WebP Express: Generates WebP variants on-the-fly
- Cost: from approx. 5 euros/month for 5,000 images
Payload CMS (our standard):
- Integrated image optimization via Sharp
- Automatic generation of responsive variants through the imageSizes configuration
- WebP conversion possible via custom hooks
Headless CMS (Contentful, Sanity, Cloudinary):
- These services offer image CDNs with automatic optimization
- URL parameters control format, quality, and size
- Cloudinary in particular offers extensive transformation capabilities
Monitoring and Quality Assurance
After implementing an automated pipeline, you should regularly review the results:
- Lighthouse CI: Integrate Lighthouse into your CI/CD pipeline to automatically detect performance regressions
- Bundlesize/Size-Limit: Set size limits for images and let the build fail if an image exceeds the threshold
- Visual Regression Testing: Tools like Percy or Chromatic compare screenshots and detect visual changes from overly aggressive compression
Image Optimization for E-Commerce: Displaying Product Photos Perfectly
In e-commerce, images are the most important conversion factor. Studies show that 75% of online shoppers rate product images as decisive for their purchasing decision. At the same time, images must load quickly, as every second of delay reduces the conversion rate by approximately 7%.
Product Image Requirements by Platform
Different sales channels have different requirements for product images:
Own Online Shop (WooCommerce, Shopify, Medusa):
- Main image: at least 1200 x 1200 px (for zoom functionality)
- Background: pure white (#FFFFFF) or transparent (PNG)
- At least 3β5 images per product (different angles, detail, lifestyle)
- File size: under 200 KB per image after optimization
Amazon Marketplace:
- Main image: at least 1000 x 1000 px, pure white background
- RGB color space (no CMYK)
- Maximum 10 MB per image (JPEG, PNG, GIF, TIFF)
- Product must fill at least 85% of the image area
Google Shopping:
- Minimum 100 x 100 px (apparel: 250 x 250 px)
- No watermark, no advertising text in the image
- High-quality product photos without distracting elements
- Supported formats: JPEG, PNG, GIF, BMP, TIFF
Zoom Functionality and High-Resolution Images
A zoom function increases the conversion rate by up to 30%, as customers can see details such as material texture, stitching, or texture. For a good zoom experience, you need:
- Minimum resolution: 2000 x 2000 px for 2x zoom
- Recommended: 3000 x 3000 px for 3x zoom
- Format: WebP at 85% quality (reduces file size by 50β70% compared to JPEG at the same visual quality)
- Lazy Loading: Load zoom images only when the user activates the zoom function
- Progressive Loading: Display a low-resolution preview image immediately, load the high-resolution image in the background
360-Degree Views and Product Videos
Advanced e-commerce stores use 360-degree views that allow customers to view the product from all sides. Optimization is particularly important here:
- Number of frames: 24β36 images for a smooth 360-degree rotation
- File size per frame: maximum 50β80 KB (WebP, quality 70%)
- Total size: ideally under 2 MB for all frames
- Preloading strategy: Load the first 4β8 frames immediately, the rest only on interaction
Product videos should be provided as MP4 (H.264) in different quality levels. Use the HTML5 video element with the poster attribute so that an optimized still image is displayed before the video loads.
Schema Markup for Product Images
Structured data helps Google display your product images correctly in search results. Use the Product schema with the following image-related properties:
- image: URL of the main product image (at least 1 image required, up to 5 recommended)
- additionalImage: URLs of additional product images
- Use absolute URLs and ensure the images are crawlable (not blocked by robots.txt)
Accessible Images: More Than Just Alt Tags
Accessibility for images goes far beyond alt text. With the enactment of the Accessibility Enhancement Act (BStG) in Austria, this topic is becoming a legal obligation for many companies.
Writing Alt Texts Correctly
Alt texts are the most important accessibility measure for images, but they are frequently misused. Here are the rules:
Informative images (photos, illustrations with content):
- Describe the content and purpose of the image
- Be precise but not too long (80β125 characters is optimal)
- Avoid "Image of..." or "Photo shows..." β screen readers already announce "image"
- Bad: "Image of team" β Good: "Five web designers collaborating on a project board in the Vienna office"
Decorative images (backgrounds, dividers, ornamental elements):
- Use an empty alt text (alt="")
- This signals screen readers to skip the image
- Even better: Add the image via CSS as a background-image, then you don't need an alt text
Functional images (linked images, image buttons):
- The alt text describes the function, not the image
- Bad: "Red arrow" β Good: "Navigate to the next project"
- For linked logos: "Go to GoldenWing homepage" instead of "GoldenWing Logo"
Complex images (diagrams, infographics, charts):
- The alt text provides a brief description of the content
- Additionally: A detailed text description in the surrounding content or via aria-describedby
- Example: Alt text "Bar chart: Website loading times by CMS" + detailed data table below
Optimizing Image Descriptions for Screen Readers
Beyond alt texts, there are additional techniques to make images accessible for screen reader users:
Figure and Figcaption:
Use the HTML figure element with figcaption for images with captions. Screen readers read both the alt text and the caption β ensure the content does not repeat but rather complements each other.
Aria-describedby for Complex Descriptions:
For infographics or diagrams, you can use aria-describedby to reference a detailed description text that is visually hidden or displayed as a collapsible section.
SVG Accessibility:
SVGs require special attention. Use the title element within the SVG for a brief description and the desc element for a detailed description. Set role="img" on the SVG element and reference title and desc with aria-labelledby.
Color Contrast and Color Blindness
Approximately 8% of all men and 0.5% of all women have a color vision deficiency. You must consider this in image design:
- Never convey information through color alone: Use additional shapes, patterns, or labels. A pie chart using only colors is unreadable for colorblind people β add labels or patterns.
- Check contrast ratio: Text on images must have a contrast ratio of at least 4.5:1 (normal text) or 3:1 (large text). Use tools like the WebAIM Contrast Checker.
- Color blindness simulation: Test your images with tools like Color Oracle or the Chrome DevTools Rendering tab, which can simulate various color vision deficiencies.
Animated Images and Motion Sensitivity
GIFs and animated images can cause problems for people with vestibular disorders or epilepsy. Keep in mind:
- No auto-playing animations: Provide a play/pause button
- Respect prefers-reduced-motion: Check via CSS media query whether the user prefers reduced motion, and display a static image in that case
- Flash frequency: Animations must not contain more than 3 flashes per second (WCAG 2.3.1)
- Provide alternatives: Always offer a static alternative or text description for animated content
Checklist for Accessible Images
Use this checklist for every image on your website:
- Alt text present and descriptive (or empty for decorative images)
- Captions correctly marked up with figure/figcaption
- Complex images supplemented with detailed text descriptions
- Text on images with sufficient contrast
- Color information not conveyed exclusively through color
- Animations with pause capability and reduced-motion support
- SVGs with title, desc, and correct ARIA attributes
- Images scale correctly at 200% zoom without information loss
Image Optimization for Social Media and OG Tags
When you share your website content on social networks, the preview image significantly determines the click-through rate. Open Graph tags (OG tags) control which image Facebook, LinkedIn, Twitter/X, and other platforms display when a link is shared. Thoughtful image optimization for social media is therefore an often underestimated lever for more traffic and visibility.
Overview of the Most Important OG Tag Image Sizes
Each platform has its own requirements for image size. If you don't follow these, your image will be automatically cropped β often with unattractive results:
- Facebook & LinkedIn: 1200 x 630 pixels (aspect ratio 1.91:1)
- Twitter/X (Summary Large Image): 1200 x 628 pixels
- Twitter/X (Summary Card): 120 x 120 pixels minimum
- Pinterest: 1000 x 1500 pixels (portrait, 2:3)
- Instagram (Feed): 1080 x 1080 pixels (square) or 1080 x 1350 pixels (portrait)
- WhatsApp preview: 300 x 200 pixels minimum
A proven strategy for the DACH region is creating a universal OG image at 1200 x 630 pixels. This format works acceptably on most platforms. For Pinterest and Instagram, however, you should create separate variants.
Implementing OG Tags Correctly
The technical implementation takes place in the `<head>` section of your HTML page. The following meta tags are relevant for image optimization:
- og:image β The absolute URL to the preview image
- og:image:width and og:image:height β The exact pixel dimensions
- og:image:type β The MIME type (e.g., image/jpeg, image/png, image/webp)
- og:image:alt β Alternative text for accessibility
- twitter:card β The card type for Twitter/X (summary_large_image recommended)
- twitter:image β Separate image for Twitter/X (optional, if different)
According to a study by BuzzSumo, posts with optimized preview images on Facebook receive on average 2.3 times more engagement than those without. In the B2B sector, which is particularly relevant for the Austrian market, professional OG images on LinkedIn increase click-through rates by up to 150%.
File Formats and Compression for Social Media
Different rules apply to OG images than to regular website images. JPEG remains the preferred format here, as all platforms reliably support it. While WebP is now recognized by most crawlers, it can cause issues with older clients.
The optimal file size for OG images is between 50 and 150 KB. Facebook recommends a minimum size of 600 x 315 pixels but does not display images below 200 x 200 pixels as a preview at all. Make sure your most important visual content is in the central safe zone area β the outer 10% of the image may be cropped on some platforms.
Automating Social Media Image Generation
For companies in the DACH region with regular content production, automation is worthwhile. Tools like Cloudinary, Imgix, or custom-built solutions can generate OG images dynamically. A template is populated with variable elements such as title, logo, and background image.
A particularly effective approach is dynamic OG image generation with Next.js using the `@vercel/og` library or similar server-side rendering solutions. These automatically create an individual preview image for each page with the respective page title and branding elements.
Testing and Debugging OG Images
After implementation, you should definitely test your OG images. Use the official debugging tools from the platforms:
- Facebook Sharing Debugger β Shows the current OG preview and cached versions
- Twitter Card Validator β Checks the Twitter card display
- LinkedIn Post Inspector β Validates the LinkedIn preview
- Local browser extensions β Tools like "Social Share Preview" show all variants at a glance
Note that social media platforms cache OG images. After a change, you must actively invalidate the cache through the respective debugging tools for the new image to be displayed.
AI-Based Image Optimization: New Tools and Possibilities
Artificial intelligence is fundamentally changing image optimization. What previously required manual work β from compression to cropping to quality enhancement β is now handled automatically by intelligent algorithms, often with better results than conventional methods.
Intelligent Compression Through Neural Networks
Classic compression algorithms like JPEG or WebP work with mathematical models that take no account of image content. AI-based compression, by contrast, analyzes the semantic content of an image and decides context-dependently which areas can be compressed more heavily.
An example: For a product photo, the AI compresses the background more than the product itself. The result is 30β50% smaller files with subjectively better quality. Tools like ShortPixel Smart Compression, Imagify AI, and Squoosh (with experimental AI features) already use this technology.
According to an analysis by HTTP Archive from 2025, 23% of the top 1,000 websites in the DACH region already use AI-powered image compression. The average savings compared to conventional lossy compression is 38% with consistent visual quality.
Automatic Cropping and Focus Point Detection
One of the most powerful applications of AI in image optimization is automatic focus point detection. Instead of manually defining the optimal crop for each image, AI automatically recognizes the main subject and intelligently crops the image for different formats.
This technology is particularly valuable for:
- Responsive images β Automatic generation of optimal crops for desktop, tablet, and mobile
- E-commerce β Consistent product presentation despite different original photos
- Content management β Editors no longer need to manually create image crops for different formats
- Social media β Automatic adaptation to different platform formats
AI Upscaling and Quality Enhancement
Modern AI upscaling tools like Topaz Gigapixel, Adobe Super Resolution, or Real-ESRGAN can enlarge images by 4 to 8 times without producing visible artifacts. For companies in the DACH region, this is particularly relevant when older image assets need to be prepared for high-resolution displays.
Additionally, AI tools offer capabilities for automatic quality enhancement:
- Noise reduction without detail loss
- Sharpening with context-aware edge detection
- Color correction and automatic white balance
- Artifact removal for heavily compressed JPEG images
- Background removal for product photos
AI-Powered Alt Text Generation
The automatic generation of alt texts by AI models such as GPT-4 Vision, Claude, or Google Gemini has now reached a quality level that is sufficient for many use cases. For the German-speaking market, however, it is important that the generated texts are grammatically correct and contextually appropriate.
Best practices for AI-generated alt texts in the DACH region:
- Have the AI generate the alt text in German β translations from English are often awkward
- Check generated alt texts for SEO-relevant keywords
- Add brand and product names that the AI may not recognize
- Use the generated texts as a starting point and adjust them manually
Cost-Benefit Analysis for the Austrian Market
Investing in AI-based image optimization pays off for most companies starting from 500 images per month. Costs range from 10 to 100 euros per month depending on the tool, while the manual alternative at an average of 2β5 minutes per image quickly consumes several working hours per week.
A survey by the Austrian Chamber of Commerce shows that SMEs in the DACH region spend an average of 12 hours per month on manual image editing. By using AI tools, this effort can be reduced by up to 80% β while achieving better results in terms of file size and image quality.
Data Privacy and GDPR for AI Image Tools
When using AI image optimization tools, companies in the DACH region must comply with the GDPR. Images containing personal data β such as photos of employees or customers β may only be transmitted to external AI services with an appropriate legal basis.
Before using an AI tool, check:
- Where are the images processed (EU vs. third countries)?
- Are the images used for AI training?
- Is there a data processing agreement (DPA)?
- How long are the images stored?
On-premise solutions or European providers with server locations in the EU offer the greatest legal certainty here.
Conclusion: Leveraging Images as a Performance Driver
Image optimization is the most effective lever for improving your website's loading time. With the right formats (WebP/AVIF), responsive images, lazy loading, and a CDN, you can reduce page weight by 60β80% β without visible quality loss.
The most important measures summarized:
- Use WebP as the standard format, AVIF as progressive enhancement
- Implement responsive images with srcset and the picture element
- Lazy loading for below-the-fold images, eager loading for the LCP image
- Optimize alt texts for all informative images
- Use a CDN for fast global delivery
- Set up automated pipelines for batch optimization
- Test regularly with PageSpeed Insights and web analysis tools
If you need support with image optimization or website performance optimization in general, contact our team. As an experienced web design agency in Vienna, we have been optimizing websites for maximum speed and best SEO results for over 3 years.
Further reading:




