Compression and Format Conversion Gate (Delivery)

Compression and Format Conversion Gate (Delivery)

1. 01

   Pull the full image manifest for the client property before touching a single file

   Export every asset reference from the CMS, ad accounts, and email templates so the gate covers what actually ships, not just what sits in the shared drive.

2. 02

   Classify each asset as pipeline work or creative work

   Automated compression, resizing, and WebP or AVIF conversion belong in the pipeline; hero composites, product retouching, and brand-critical visuals stay with a human editor.

3. 03

   Set a per-asset byte ceiling tied to the client's Core Web Vitals target

   A 200KB ceiling for above-the-fold hero images and 100KB for in-body editorial images is a workable starting point for most content sites.

4. 04

   Run the batch through an automated optimizer and log before-and-after sizes

   Tools such as Imagify handle Smart Compression and format conversion in bulk, while MageCDN serves transformed variants through a CDN layer when the client needs delivery plus optimization.

5. 05

   Spot-check the ten highest-traffic assets at full resolution on a real device

   Automated quality scoring misses banding in gradients and softness in fine text overlays; a 30-second visual pass per asset catches what the algorithm rates as acceptable.

6. 06

   Confirm format fallbacks exist for browsers that reject AVIF

   Ship WebP as the fallback and keep the original JPEG or PNG in storage so a rollback does not require re-exporting from source files.

7. 07

   Publish the optimized set and record the size delta in the delivery log

   A one-line entry per batch (asset count, total bytes saved, formats emitted) gives the account lead proof of work for the monthly retainer report.