Perfmatters earns its reputation by hiding complexity. Toggle the global tweaks, point the Script Manager at a page or two, and the heaviest WordPress stack gets noticeably lighter. The catch is that the Script Manager grows quietly. Six months in, dozens of pages carry their own disable rules, exception flags, and regex patterns, and the only way to audit them is to open each page on the front end one URL at a time.

SleekView Charts reads the perfmatters_script_manager postmeta and the perfmatters_options blob and renders dashboard cards over the rule set. A Number card carries the total pages with active rules, a Donut breaks rule count by post type, a Bar surfaces the script handles disabled most often across the site, and an Area chart traces rule edits per day so quiet drift becomes visible.

Charts never invent rules. Every value comes from the data Perfmatters writes, every drill-down points back to the postmeta row, and inline edits route through the plugin's own meta API. The Script Manager UI stays the source of truth; SleekView Charts just turns the data behind it into a working audit.

Perfmatters keeps its UI minimal on purpose. That works while the rule set is small and the site is fresh. Once the Script Manager has touched a hundred pages, the per-page overlay stops being enough to audit anything, and the only honest answer to which scripts the site disables is a Google Sheet and a long evening.

The data needed to answer that question is already in postmeta and the options array. Visualising it as Number, Pie, Bar, and Area cards turns the configuration into a dashboard performance owners can read at standup, while the Script Manager UI keeps doing what it does best for actual rule edits.