WP Image Zoom does not create posts or custom tables. Its data is the settings array in wp_options that defines lens shape, lens size, zoom level, and the rules for which images get the zoom: WooCommerce product galleries, post content images, ACF fields, Elementor widgets, page builder images. That settings shape is small, but the coverage question across the site is real: how many product galleries actually qualify, how many post-content images would trigger zoom, how many ACF image fields are eligible.

SleekView Charts treats the WP Image Zoom settings array as the configuration and scans the relevant content surfaces against it. Number cards count total eligible products, total eligible post-content images, and total eligible custom-field images. Pie cards split coverage by source (WooCommerce, post content, ACF, Elementor). Bar cards rank product categories or post types by zoom coverage. Area cards trace coverage over post_date to show whether new content keeps the zoom rule alive.

Every card reads through the same wp_options blob WP Image Zoom already maintains plus the wp_posts and postmeta the rules apply to, so front-end zoom behaviour is unchanged. The dashboard sits alongside SleekView's table of zoom-eligible content.

WP Image Zoom is the smallest data shape in this batch: no CPT, no custom tables, just a settings array in wp_options that defines lens shape and which surfaces the rule applies to. The coverage question is still real, though. A WooCommerce store with hundreds of products only benefits from zoom on the products that have proper gallery imagery.

An editorial site only benefits on the posts whose images meet the rule. The default settings screen confirms the rule is enabled but never says how often it actually fires. SleekView Charts applies the rule across the database and renders the answers as cards.

A donut of surface mix confirms where the rule lands. A horizontal bar of category coverage surfaces the imagery work still ahead. An area chart of cadence confirms whether new content keeps the rule alive.

A single number KPI gives owners the coverage figure the settings page does not. The configuration is small, the coverage question is large, and the dashboard turns it into a managed surface.