Perfmatters stores all of its tuning in wp_options under keys like perfmatters_options for the global toggles and perfmatters_script_manager_settings for the per-script rules generated by the Script Manager. Each script rule carries a handle, an asset URL, a list of post types or specific URLs where the rule applies, a disable flag, and a delay flag. The default Script Manager UI overlays each frontend page with a popup that lets a developer disable, delay, or exclude scripts. Once the site has hundreds of rules, the popup stops being a working surface and turns into a maze.

SleekView Kanban reads the same perfmatters_script_manager_settings array the popup writes to. Pick a derived perfmatters_state field that buckets rules by the loaded flag, the disable flag, the delay flag, and an audited workflow tag and every rule becomes a card grouped under Loaded, Disabled, Delayed, or Audited. Card fronts can show the script handle, the asset URL, the scope (everywhere or specific URL patterns), and the last update so a developer can see at a glance which rules are still in motion.

Dragging a card between columns rewrites the matching entry in the perfmatters_script_manager_settings array through the plugin's helper. Perfmatters's own runtime keeps applying the rules on the next page render, so a manual move on the board does not need a separate cache purge or a manual settings save inside the admin. Capability checks honor manage_options and the audit log records who changed what.

Perfmatters's Script Manager is a powerful tool buried behind a popup. The popup is great for ad-hoc audits and terrible for sustained work. Front-end developers running a real performance audit need to know which scripts have been touched recently, which ones are still loading site-wide, and which ones were delayed last sprint but are now showing up in long-task reports again.

The popup answers none of those questions across the whole site. Most teams end up keeping the answers in a private spreadsheet, which means the audit history and the actual Perfmatters configuration drift apart by the second week. A kanban view that reads and writes the same perfmatters_script_manager_settings option as the popup keeps the audit team and the live configuration aligned.

Loaded, Disabled, Delayed, and Audited become a real workflow and the next audit starts where the last one stopped instead of starting from scratch on every site refresh.