Directly from wp_options, wp_postmeta, wp_commentmeta, and the plugin's scheduled task log entries. No shadow copy, no export pipeline. The chart cards run live queries against the same rows the cleaner scans, so the dashboard reflects the current database state.

Both. The free orphan scans for options, postmeta, and commentmeta back chart sources directly. Pro features like scheduled cleanup and the task log surface as additional chart group-by candidates so the dashboard reflects the full cleanup pipeline.

Yes. The plugin's scheduled cleanup writes task entries that SleekView reads as a time series. An Area card grouped by run date with rows-deleted as the value surfaces whether the automation is keeping up with new cruft or falling behind.

Yes. SleekView only queries the columns and rows the active cards need, so a multi-million-row wp_postmeta produces a lean grouped count rather than a full table scan. Heavy aggregations are pushed to the database engine and cached at the view level.

SleekView reads tables, not plugin signatures. If WP-Optimize and Advanced Database Cleaner both maintain logs in wp_options, point separate views at each option-name pattern and chart them side by side. The cards do not care which plugin wrote the row.

Yes. View-level filters for autoload flag, key pattern, or date range apply to every chart card on the dashboard. One saved configuration drives both the editing table and the reporting view, so investigation and summary stay in sync.

Charts are read-only summaries by design. To act on an insight, switch to the SleekView table filtered to the same slice (for example, transients matching a stale prefix) and delete from there. The cleanup itself stays inside the plugin's existing workflow.

No. The plugin's scan tabs, cleanup buttons, and scheduling settings stay where they are. SleekView Charts adds a reporting surface on top of the data the plugin already exposes, so cleanup remains a one-click action and the dashboard owns the summarisation.