Speed Booster Pack groups several tweaks under a single performance tab. The page cache writes static HTML under wp-content/cache/sbp/. Local Avatars and Local Google Fonts store cached copies under wp-content/uploads/sbp/ with one file per asset. The asset optimization pass records minified and combined bundle metadata in wp_options under the sbp_assets_meta key with a status column that flows through queued, processing, optimized, and failed values. The default settings screen exposes a Flush Cache button and a savings counter, which works on a small site and hides every interesting detail the moment one cached font or one asset bundle stops updating.

SleekView Kanban reads the same Speed Booster Pack folders and option rows the settings screen aggregates. Pick the asset optimization status field as the grouping and every asset becomes a card grouped under Uncached, Optimizing, Cached, or Failed. Card fronts can show the asset handle, the source URL, the original size, the cached size, the local copy flag, and the last update timestamp so a developer can spot bottlenecks across the optimization pipeline without leaving the board view.

Dragging a card between columns calls the Speed Booster Pack helper API. A move from Failed back to Uncached resets the asset row and re-runs the optimization pass on the next cron tick. A move from Optimizing back to Uncached cancels the in-flight worker. The plugin's automatic purge on post save keeps running, so a manual board action never collides with the plugin's normal cache invalidation flow.

Speed Booster Pack groups a long list of tweaks under one settings screen. A page cache writes static HTML. Local Avatars downloads Gravatar images to the upload folder.

Local Google Fonts pulls font files locally. Asset optimization minifies and combines CSS and JS bundles. Defer scripts move tags to the footer.

Every one of those tweaks records a status that flows from queued to processing to optimized, with a failed branch when something goes wrong. The settings screen reduces all of that to a single Flush Cache button and a savings counter, which works on a small site and hides every interesting detail the moment one cached font stops updating on a remote endpoint. A kanban board flips that around.

Every asset is a card. Every optimization status is a column. A glance at the board tells the team how many assets are uncached, how many are mid-optimization, how many are warm with local copies ready, and how many failed with a reason worth investigating.

Dragging a card writes the change back through the same helpers the cron tasks already trust. The Flush Cache button still exists, and still works as a last resort. The board exists for the rest of the time, when the team needs to see the optimization pipeline the way the pipeline already sees itself.