Perfmatters' Script Manager writes per-page disable rules to postmeta as perfmatters_script_manager, with the script handles or URLs to disable, exception flags, and regex patterns serialized into the value. Global tweaks (heartbeat, autosave, emojis) live in the perfmatters_options array. Lazy load exclusions, preload hints, and CDN rewrites also live in the options blob. The default Script Manager loads on the front end as an overlay, one URL at a time. There is no admin screen that lists every page that disables jQuery, every URL with a custom regex, or every post with at least one exception flag set.

SleekView reads the postmeta and options Perfmatters stores and surfaces them as flat rows. One row per page can show its slug, post type, the count of disabled scripts, the count of exception rules, and which global tweaks are active. Sort by rule count to find pages with the heaviest customization, filter to posts that disable a specific handle (like elementor-frontend or woocommerce-general), or group by post type to see whether your Script Manager work is concentrated on landing pages or scattered across the blog.

SleekView never invents new rules. Inline edits write through Perfmatters' own update_post_meta and options API, so the plugin's settings page remains authoritative. Saved views like Pages with disabled jQuery or Lazy load exceptions can be scoped per role, useful for handing performance ownership to a developer without giving them access to license keys or global tweak toggles.

Perfmatters earns its reputation by hiding complexity. Toggle the global tweaks, point the Script Manager at a page or two, and a heavy stack like Elementor plus WooCommerce gets noticeably lighter. The catch is that the Script Manager grows quietly.

Six months in, dozens of pages each carry their own disable rules, exception flags, and regex patterns. Some are deliberate, some were copy-pasted from a tutorial, and some target a plugin that was uninstalled last quarter. The default UI does not list any of this.

The only way to audit it is to open each page on the front end and read the overlay one URL at a time. SleekView solves the audit problem by treating Perfmatters' postmeta and options as the structured store they really are. Every rule is a row, every page is a record, and every script handle is a filter.

Performance engineers can refactor rules in bulk, agencies can hand clients a read-only inventory, and migrations can start with the actual list of disabled scripts instead of educated guesses. The plugin's UX stays minimal; the audit surface stops being a manual job.