[B] Image Optimizer

Conversion happens in the background through Action Scheduler, not while the page loads. When you upload an image, it is added to a processing queue that runs outside the HTTP request flow. The result is that the user experiences no delay. For batch processing of existing libraries, you can set the batch size according to your server's capacity (5-40 images per batch). The system is fully asynchronous and does not block.

The plugin automatically detects which formats your server supports when it is activated. If your server only supports WebP but not AVIF, simply turn AVIF off in the settings. If your server supports neither, the plugin works in fallback mode: it keeps optimising metadata and applying lazy loading, but it does not convert formats. We show a clear status in the dashboard so you know exactly what is available.

Yes, as long as your theme or builder uses the standard WordPress image functions (wp_get_attachment_image, the_post_thumbnail, img tags with src, etc.). If your theme generates image HTML in a completely custom way without going through the WordPress hooks, we will need to use the "Process full page HTML" option (in Advanced), which analyses the final rendered HTML. We have tested it with Elementor, Divi, Beaver Builder, GeneratePress, Astra and hundreds more. If you have a specific case, contact us and we will check it.

Absolutely. You can add the CSS class "no-opt" to any image to exclude it from optimisation. You can also set global selectors in the settings to exclude, for example, every logo (class "custom-logo") from lazy loading. There are also developer filters (bdw_image_optimizer_skip_attachment) for custom logic based on the attachment ID, URL, metadata or any other condition.

If you are migrating from another optimisation plugin, we recommend: 1) Deactivate the previous plugin, 2) Activate [B] Image Optimizer, 3) Go to Media → Optimisation Queue, 4) Start a "Full regeneration" campaign. Our system will detect which images already have WebP/AVIF files and skip duplicate processing. If you want to force a full regeneration (for example, because the previous plugin used different quality settings), there is a "Clear optimised status" option for each image in the Media Library.

There are no technical limits. We have clients processing 50,000+ images without problems. What matters is the batch size: on shared servers, use 5-10 images per batch. On dedicated servers or VPS, 20-40. The system progresses slowly but reliably, without overwhelming your server. You can pause, resume or change the batch size at any time.

Yes, fully. In a multisite environment, each site has its own independent [B] Image Optimizer settings. The queues are isolated per site, so processing on one site does not interfere with another. Global network settings are also supported if you need them. Perfect for agencies that manage several clients.

No, never. All processing happens locally on your server using Imagick or GD. There are no external dependencies, no API calls and no data leaving your infrastructure. This means total privacy, no API costs and complete control over your assets. The only optional external integration is Cloudflare cache purging (if you define the credentials in wp-config.php), which is purely for cache invalidation, not for image processing.

Professional: email support during office hours (9:00-18:00 CET, Monday to Friday), with replies typically within 24 hours. Agency: email + live chat with priority, replies within 4 hours. Business: dedicated 24/7 support, a 99.9% availability SLA and monthly consultancy sessions. Every plan includes access to complete documentation, video tutorials and lifetime updates.

A typical example: . This provides: 1) WebP for modern browsers, 2) a JPG fallback for older browsers, 3) srcset/sizes for responsive images, 4) width/height to prevent CLS, 5) loading="lazy" to defer off-screen images. All perfectly semantic and accessible.