Perfmatters earns its reputation by hiding complexity behind clean toggles and a per-page Script Manager. Toggle the global tweaks, point the Script Manager at the pages that need it, and a heavy Elementor plus WooCommerce stack gets noticeably lighter. The trade-off, six or twelve months in, is that the configuration grows in places no single screen ever summarises. Disable rules live in postmeta, exceptions live alongside them, lazy load exclusions and tweaks live in the perfmatters_options array.

SleekView reads the same postmeta and options Perfmatters already writes. Page, post type, script handle and disabled count become sortable columns. Filter to script_handle = elementor-frontend to find every page disabling Elementor. Filter to post_type = product for a per-area audit. Sort by last_modified to see recent tuning.

Perfmatters' settings stay where they are for the per-page work and the global tweaks. SleekView is the audit, refactor and migration table performance engineers, agency leads and developers planning an upgrade actually need.

Perfmatters does its job by hiding complexity behind toggles and a per-page Script Manager, which is exactly the right interface for the tuning work. The configuration that interface produces, on the other hand, grows quietly. After a year of disable rules, exception flags, lazy load exclusions and tweak toggles, the only way to audit the install is to open each page on the front end and read the overlay.

SleekView reads the same postmeta and options Perfmatters writes and renders a sortable, filterable WP Admin grid on top of them. Performance engineers refactor rules in bulk against a real table. Agency leads hand clients a read-only inventory.

Migration planners scope the work by script handle before touching a single page. The plugin's UX stays minimal; the audit surface stops being a manual job.