WP Clone is a single-purpose backup plugin: package the entire site as a single ZIP, store it under wp-content/uploads, and restore from URL or upload on the target install. The default UI is intentionally minimal: a button to create, a field for the URL to restore from, a list of existing ZIPs. That minimalism is the plugin's selling point and the reason it is still widely used. It is also why the question 'how many clones did we generate last quarter?' has no straight answer in the default admin.

SleekView Charts reads the same wp_options entries WP Clone writes for each clone and restore, and reconciles them with the ZIP manifest on disk. A Number card surfaces total clones in the last 30 days. A Pie splits jobs between clone and restore. A Bar groups average archive size per month, so site growth becomes a chart line. An Area trends clones over time so the actual cloning cadence in a migration project becomes visible.

Filters carry between the chart view and the table view: filter to restores only, or to archives over 500 MB, and both surfaces narrow together. WP Clone keeps doing the cloning; SleekView Charts handles the visibility side.

WP Clone's reason for existing is simplicity: one button, one ZIP, one URL on the other end. That deliberate scope keeps the plugin easy to recommend. It also leaves the data the plugin produces on the floor.

Sites that use WP Clone for staging-to-prod cycles or for periodic safety snapshots accumulate hundreds of archives over a year, and the default screen surfaces none of it as an aggregate. Charting the same data fixes that without changing the plugin's character. A KPI card answers 'is the cloning workflow still in use?' A trend chart answers 'how often are we restoring?' A size trend warns when archives are getting big enough that a restore over a hotel WiFi is going to be a problem.

Same plugin, same ZIPs, much better posture for the team relying on them.