SmallPict LogoSmallPict
Torna al Blog
Web Performance4 min read

Why Modern WordPress Sites Need Dual AVIF/WebP (And How to Cut Image Payloads by 80%)

Discover how serving modern AVIF with WebP fallback via HTML5 <picture> tags drastically improves Core Web Vitals and mobile LCP scores without breaking legacy browsers or wasting cloud quota.

SM
SmallPict Performance LabPerformance Engineering
•
October 6, 2026

Images account for over 60% of total web page weight on the average WordPress site. On WooCommerce stores and media-heavy blogs, that number easily climbs past 80%.

When a mobile visitor visits your site over a cellular connection, downloading multi-megabyte JPEG or PNG hero banners is the single biggest cause of failing Google Core Web Vitals (Largest Contentful Paint - LCP).

Every additional second of load time directly drops conversion rates, pushes bounce rates up, and hurts your Google search visibility.

The Format Dilemma: JPEG vs WebP vs AVIF

For years, WebP was celebrated as the successor to legacy JPEG and PNG formats, cutting file sizes by roughly 25% to 35%.

However, AVIF (AV1 Image File Format) represents an even larger technological leap forward:

  • Up to 50% smaller than WebP at equivalent visual quality.
  • Up to 80-85% smaller than original JPEGs.
  • Exceptional preservation of fine gradients, text sharpness, and high-contrast boundaries.
  • Native support for 10-bit and 12-bit High Dynamic Range (HDR) color profiles.
Image FormatAverage Compression RatioBrowser Support (2026)Visual Fidelity
Legacy JPEGBaseline (100%)100%Degrades with high artifacts
Google WebP~65% of JPEG~97%High, slight blur on fine lines
Modern AVIF~18-25% of JPEG~94%Exceptional sharpness & color

The Trap: Why Single-Format Delivery Breaks Browsers

If AVIF is so superior, why doesn't every WordPress site switch all images to AVIF?

The trap lies in legacy browser compatibility. While modern Chrome, Safari (v16.1+), and Firefox support AVIF natively, older mobile devices, embedded webviews, in-app social browsers, and legacy operating systems still cannot decode AVIF files.

If you simply replace image .jpg extensions with .avif, users on older devices see broken placeholder boxes.

The Solution: HTML5 Dual Picture Tag Delivery

The standard-compliant, future-proof solution is Dual Format Delivery using native HTML5 picture tags with progressive source fallback:

HTML
1
2
3
4
5
6
7
8
<picture>  <!-- 1. Modern browsers download ultra-lightweight AVIF -->  <source type="image/avif" srcset="hero.avif">  <!-- 2. Compatible browsers fallback to WebP -->  <source type="image/webp" srcset="hero.webp">  <!-- 3. Legacy clients safely render original JPEG -->  <img src="hero.jpg" alt="Optimized Hero Image" width="1200" height="630" loading="lazy"></picture>

With this markup, modern devices download the razor-sharp 45KB AVIF asset, intermediate browsers download the 95KB WebP asset, and older devices gracefully fall back to the original JPEG—without layout shifts or JavaScript overhead.

The Cloud Quota Waste Problem (And How SmallPict Solves It)

Most WordPress image optimizer plugins suffer from a fundamental architectural flaw: they upload and convert every single thumbnail size to the cloud.

When you upload one image, WordPress core automatically generates 6 to 12 intermediate sub-sizes (e.g. thumbnail, medium, large, woocommerce_catalog, etc.).

If a plugin sends 12 sub-sizes to an external cloud API for AVIF and WebP transcoding, a single photo upload consumes 24 cloud conversion credits! Your monthly plan quota evaporates in days.

SmallPict's Zero-Cloud Local Sub-Size Generation

SmallPict solves this with an upfront dispatch calculator:

  1. Only the Master Image is Dispatched: SmallPict sends the original high-resolution master asset to our cloud API for lossless/lossy next-gen conversion.
  2. Local Generation via WP_Image_Editor: Once the optimized master .avif and .webp files return to your server, SmallPict reuses WordPress's native local image processor (WP_Image_Editor / GD or Imagick) to generate all intermediate thumbnail sub-sizes directly on your local server for free.
  3. Zero Quota Waste: A photo with 12 thumbnails consumes only 1 cloud credit, saving you up to 90% in cloud processing fees.

Real-World Benchmark Results

We benchmarked a standard WooCommerce single product page featuring 8 high-resolution product photos before and after implementing SmallPict's Dual AVIF pipeline:

  • Original Image Payload: 4.62 MB (JPEGs)
  • SmallPict Optimized Payload: 684 KB (AVIF with WebP fallback)
  • Total Weight Reduction: -85.2%
  • Mobile Largest Contentful Paint (LCP): Dropped from 4.3 seconds to 1.1 seconds
  • Google PageSpeed Mobile Score: Jumped from 41 to 96 (Green)

How to Get Started

You don't need to rebuild your theme or modify template files. SmallPict automatically filters WordPress media output on the fly (wp_content_img_tag, the_content, wp_get_attachment_image), safely injecting <picture> tags with zero layout shifts.

Install the free SmallPict plugin from the WordPress repository or check out our Pricing & Plans to supercharge your site's speed today.

S

Written by SmallPict Performance Lab

Performance Engineering

Engineering cloud media acceleration, next-generation image optimization, and CDN tooling to speed up modern web experiences.

Core Web Vitals Accelerated

Speed Up Your WordPress Site & Pass LCP

SmallPict automatically optimizes media into next-gen AVIF & WebP formats, offloads heavy libraries to global Anycast CDN, and protects hosting disk space without breaking layouts.

Non-destructive retentionZero cloud quota wasteNo credit card required

Related Articles

Explore more insights on image performance, Core Web Vitals, and cloud infrastructure.