← Integrations

Static Shield + EWWW Image Optimizer

EWWW can compress images locally, using bundled or system-level tools, or through its optional cloud API — either way the output is just a static image file by the time a crawl captures it, so which mode is configured doesn't change how this is served. Its own Easy IO CDN, when enabled, rewrites image URLs the same way. WebP/AVIF delivery is the exception: it commonly relies on a server-level rewrite or a PHP-side Accept-header check that a plain static host doesn't perform on its own.

Recommended mode

Hybrid

Static behavior

Compressed image files — local or cloud-processed — and Easy IO CDN-rewritten image URLs when enabled, are both served from the static release as-is.

Dynamic behavior

WebP/AVIF format selection depends on a live per-request check (a server rewrite or a PHP Accept-header check) that a static host doesn't run unless it's separately configured at the host or CDN layer.

Bridges & routes

None needed — EWWW declares no public routes of its own. WebP/AVIF delivery isn't something a bridge route can fix; it needs to be replicated at the host or CDN layer instead.

Setup

No special setup — detected automatically once active, whether images are processed locally or through EWWW's cloud API. If WebP/AVIF savings matter, confirm the format is still actually being served once the site goes static.

Limitations

Without that content-negotiation rule replicated at the host or CDN layer, every visitor silently gets the original, larger image format instead of WebP/AVIF — not a broken page, just a quiet performance regression. Pre-generated <picture>/srcset markup sidesteps the problem entirely if the savings matter for this site. None of this has been behaviorally validated against a live install — the classification is rule-derived, which is why WebP/AVIF confidence is capped lower than plain compression.