Start with dimensions, not compression
Oversized pixel dimensions often waste significantly more bytes than an imperfect quality setting. Many publishers upload raw camera photos (often 4000px wide or larger) only to render them in a 680px wide content column. The browser is forced to download the massive file and scale it down on the fly, wasting user bandwidth and triggering layout shifts.
Always measure the maximum display width required by your theme layout. For standard content areas, a maximum width of 1200px (or 1920px for full-width hero images) is sufficient. Scale the images to these dimensions before applying compression. By resizing the raw canvas first, you eliminate up to 80% of unnecessary pixel data before the compressor even runs.
Create modern sibling formats safely
WebP and AVIF offer next-generation compression, but replacing original files directly is risky. Older browsers or API tools may fail to load them, and external integrations can break. A safer workflow generates modern WebP and AVIF files as "siblings" alongside the original JPEG or PNG file. This preserves the original file URL while allowing modern browsers to load the lighter sibling asset.
To achieve this without a paid CDN, we check if the server has GD Library or Imagick active with AVIF/WebP support. When a client requests the page, the server uses standard HTML5 `<picture>` tags to output modern formats to compatible browsers, falling back to JPEGs for legacy devices.
- Audit host GD Library or Imagick WebP/AVIF support on the dashboard.
- Generate sibling files under the same directory, keeping original URLs intact.
- Deactivate overlapping image-rewriting plugins to prevent double optimization.
Keep a recoverable backup ledger
Bulk optimization should never be a leap of faith. destructive compression algorithms permanently discard image details, and once saved, they cannot be reversed. If you compress a batch of product photos too aggressively, they can appear pixelated or blurry, hurting conversions.
Always use a backup-first optimizer. Cyphex automatically moves the original master file to a secure local folder (`/wp-content/uploads/cyphex-backups/`) and records the file path in a database ledger. If the optimized result is unsatisfactory, you can restore the original file instantly. Test a small batch of 5 images first to verify quality before executing bulk changes across the entire library.