Imagify stores per-attachment data in wp_postmeta under the _imagify_data key with the per-size savings, the compression level (Normal, Aggressive, Ultra), and the run timestamp. The _imagify_status key carries the high-level state (success, already_optimized, error), and the _imagify_error key holds the most recent error message. The default Imagify bulk optimization screen renders progress as a counter and a results panel, which works during a fresh run and stops being useful once the library accumulates thousands of rows with errors, retries, and exclusions over time.

SleekView Kanban reads the same Imagify meta rows the bulk screen queries. Pick a derived imagify_state field that buckets rows by status, error presence, and the in-flight queue and every attachment becomes a card grouped under Unoptimized, Optimizing, Optimized, or Errored. Card fronts can show the file name, the original file size, the savings ratio when optimized, the compression level, and the error message when errored so a site manager can see exactly which attachments still need attention.

Dragging a card between columns updates the Imagify meta through the plugin's own API. A move from Errored back to Unoptimized clears the error and re-queues the row for the next bulk run. A move from Optimizing back to Unoptimized cancels the in-flight job cleanly. Any subscriber to the after_imagify_optimize_attachment hook keeps firing as the rows update, so existing automations such as CDN warm-ups continue to run without modifications.

Imagify trades on simplicity. The bulk screen tells the team how many images were optimized and how much space was saved, and most weeks that is enough. The problem starts when the API quota runs out mid-run or when a batch of uploads triggers an unsupported-format error.

Those rows quietly stay errored and never reappear in any working surface. Six months later, the savings ratio on the dashboard looks healthy and the library is still leaking weight from the same few hundred files. A kanban view that reads and writes the same Imagify meta rows as the bulk screen keeps the errored cohort visible, prioritized, and actionable.

Unoptimized images surface before publication. Optimizing images carry a live progress signal. Errored images cluster by message in a single column the developer can clear in an afternoon instead of letting them sit unreviewed until the next time the performance team runs an audit.