EWWW Image Optimizer keeps optimization data in its own database tables: wp_ewwwio_images for per-image rows with original bytes, optimized bytes, level, and conversion target, and wp_ewwwio_queue for the active and pending bulk queue. The Bulk Optimize screen runs the queue, the Tools screen lists optimized images, and the dashboard shows totals, but none of those surface a cohort-level chart layout.

SleekView Charts reads ewwwio_images and ewwwio_queue directly and turns them into a configurable dashboard. Number cards show total bytes saved. Pie cards split the library by conversion target (WebP, AVIF, none). Bar cards rank optimization levels (10, 20, 30, 40) by use. Area cards trace optimized bytes per month so a performance lead can see the rhythm of the work.

Every card reads through the same tables EWWW already maintains, so the cloud API, the WP-CLI worker, and the local optimization continue to behave as before. The dashboard is an admin companion that turns the audit-shaped questions into a glance-and-go layout.

EWWW Image Optimizer is unusual among WordPress optimizers because it stores per-image data in its own custom tables rather than only in postmeta. That decision pays off in two ways: queries run against indexed columns even on large libraries, and the data shape is ideal for aggregation. The cost is that the data lives in tables the standard WP admin does not surface.

The bulk screen runs the queue and the dashboard shows broad totals, but the cohort-shaped questions a performance team has after a few months of operation, which level is doing the most work, which conversion target has the best coverage, what the rhythm of work has looked like over the past quarter, live a layer down. SleekView Charts reads the same tables and turns those answers into a dashboard. The plugin keeps optimizing on its own schedule.

The performance leads, sysadmins, and agencies finally have the chart layer the database-backed data shape always invited.