Swift Performance Pro extends the Lite warmup pipeline with several extra background queues. The warmup table sits in wp_swift_performance_warmup with the familiar status column. Image optimization rows live in wp_swift_performance_image_optimizer with original size, optimized size, and a status column that flows through queued, optimizing, optimized, and failed values. The Critical CSS log writes to wp_options under the swift_performance_ccss_log key with per-template generation attempts. The Pro dashboard exposes a Clear All Cache toggle and three counters, which works on a launch day and hides every interesting detail the moment one of the queues stalls behind a slow upstream request.

SleekView Kanban reads the same warmup, image, and Critical CSS tables the Pro dashboard aggregates. Pick the relevant status column as the grouping and every queue row becomes a card grouped under Queued, Warming, Cached, or Failed. Card fronts can show the URL or image path, the original and optimized sizes, the warmup attempt count, the Critical CSS flag, and the last update timestamp so a developer can spot bottlenecks across the Pro pipelines without leaving the board.

Dragging a card between columns calls the Swift Performance Pro helper API. A move from Failed back to Queued resets the row and re-submits to the next worker tick. A move from Warming back to Queued cancels the in-flight task cleanly. The Pro plugin's automatic purge on post save keeps running, so a manual board action never collides with the plugin's normal cache invalidation flow on disk.

Swift Performance Pro hides several queues behind a single dashboard. The warmup script walks the sitemap. The image optimizer ships uploads to the configured backend.

The Critical CSS generator inlines above-the-fold styles per template. Every one of those pipelines has a status column that flows through queued, processing, cached or optimized, and failed values. The dashboard reduces all of that to a Clear All Cache toggle and three counters, which works on a small site and goes blind the moment one queue stalls behind a slow upstream request that the cron task cannot resolve on its own.

A kanban board flips that around. Every queue row is a card. Every status value is a column.

A glance at the board tells the team how many URLs or images are queued, how many are stuck in the worker, how many succeeded, 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 Clear All Cache toggle 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 Pro pipelines the way the pipelines already see themselves.