No. SleekView Charts is an admin reporting surface that reads the postmeta Smush already writes. Optimization, backups, CDN sync, and the directory log continue to be Smush's job. The dashboard is purely a reading layer over the data Smush stores.

Yes. Smush records WebP conversion status per attachment when the WebP module is active. Add a Number or Pie card filtered on the WebP delivered flag to surface coverage gaps and plan the missing-format pass.

Yes. The standard Smush postmeta keys are written by both the free plugin and Smush Pro. Pro features such as super-Smush savings, lossy compression metadata, and the directory Smush tool surface as additional chart sources automatically when Pro is active.

Yes. The dashboard has a top-level filter bar that applies across all cards. Picking a post type narrows every card on the screen, so a product-image-only or blog-image-only audit is one filter away from the library-wide view.

Yes. Smush Pro's directory Smush feature optimizes images outside the standard media library, with progress recorded in its own data. SleekView registers that data as a separate source so a dedicated dashboard for theme images and plugin assets is one click away.

No. Charts are computed against the same postmeta indexes Smush itself uses, with SleekView caching aggregation results between renders. The first paint may take a moment on very large libraries, subsequent loads are immediate.

Yes. Each card supports a CSV export of its underlying aggregation. Export the post-type ranking for the next editorial meeting, or export the yearly savings trend for a quarterly performance memo.

Yes. Smush sets a lazy load eligibility flag on each attachment. Add a Pie card grouped on that flag to see how much of the library is covered by lazy loading, useful after enabling the feature on an older site.