NitroPack delivers optimization through its remote service plus a small local plugin that stores configuration in wp_options under keys like nitropack-siteSecret, nitropack-siteId, and nitropack-cachePath. URL-level optimization state lives in the remote NitroPack control panel and is mirrored locally through a small marker file per URL under wp-content/nitropack/. Each URL ends up in one of four broad states: never optimized, currently optimizing, optimized and served from the cache, or invalidated by a recent post update. The default NitroPack dashboard widget exposes a couple of counters, which works for a healthy site and offers little when something looks off.

SleekView Kanban combines the NitroPack URL state API with the local marker files. Pick a derived nitropack_state field that buckets URLs by remote optimization status, local marker presence, and the last invalidation timestamp and every URL becomes a card grouped under Unoptimized, Optimizing, Optimized, or Invalidated. Card fronts can show the URL path, the last optimization timestamp, the device type (desktop or mobile), and the reported PageSpeed score so a developer can spot underperforming URLs without leaving WordPress.

Dragging a card between columns calls the NitroPack helper, which talks to the remote API for purge and optimization jobs. A move from Invalidated back to Unoptimized requests a fresh optimization. A move from Optimizing back to Unoptimized cancels the in-flight job through the standard NitroPack cancellation path. The plugin's automatic invalidation on post update continues to run, so a manual board action never collides with the normal invalidation flow.

NitroPack does most of its work in the cloud and surfaces very little of it inside WordPress. The dashboard widget shows aggregate counts. The control panel lives in a separate browser tab.

Performance leads end up flipping between two surfaces and a spreadsheet whenever they want to understand which URLs are quietly underperforming. That works once or twice and then quietly stops happening. Six months later, dozens of URLs sit at score sixty and the team has stopped looking.

A kanban view that reads the NitroPack URL state API and the local cache markers brings the operational data back into WordPress. Unoptimized URLs surface before they go live. Stalled Optimizing jobs cluster in a single column instead of disappearing into a remote queue.

Invalidated URLs after a deploy show up as a clear list to triage in the morning instead of being silently re-optimized at whatever priority the queue happens to assign.