SleekView Kanban for LiteSpeed Cache
SleekView reads the LiteSpeed Cache queue tables and image optimization pulls directly, groups every URL or image by its current job status, and lets your team drag cards between Queued, Processing, Done, and Failed so the underlying record updates the moment the column changes.
♾️ Lifetime License available
Why LiteSpeed Cache queues fit a kanban view
LiteSpeed Cache runs several background queues that share one admin screen. The crawler queue lives in wp_litespeed_crawler and tracks page cache warm-up status per URL. Critical CSS jobs sit in wp_litespeed_img_optm and the CCSS data table, with each row carrying a status column that flows from notified to pulled. Image optimization rows track pull cycles from the QUIC.cloud service, including the original size, the WebP variant, and the failure reason on rejection. The default Toolbox screen surfaces a counter and a Purge All toggle, which works on a small site and gets opaque the moment a queue stalls.
SleekView Kanban reads the same wp_litespeed_* tables the Toolbox aggregates. Pick the status column as the grouping field and every queue row becomes a card grouped under Queued, Processing, Done, or Failed. Card fronts can show the URL or image path, the QUIC.cloud job ID, the original file size, the optimized size, the WebP variant flag, and the last update timestamp so a developer can spot stuck CCSS pulls or failed image optimizations without leaving the board.
Dragging a card between columns calls the LiteSpeed helper API. A move from Failed back to Queued resets the row status and re-notifies QUIC.cloud for the next pull cycle. A move from Processing back to Queued forces the queue to re-issue the notification request. LiteSpeed's automatic cron pulls keep running, so a manual board action never collides with the plugin's normal queue processing flow.
Workflow
From Toolbox toggles to a live LiteSpeed queue board
Connect the LiteSpeed Cache source
Pick the status column to group by
Configure card fronts per queue type
Move cards to update LiteSpeed Cache
Sample board
Sample LiteSpeed image optimization layout
Comparison
Default LiteSpeed Toolbox versus SleekView Kanban
Default LiteSpeed Toolbox
- Toolbox shows aggregate counters with no per-URL or per-image queue breakdown
- Failed rows surface as a number with no card-level reason or retry control
- Crawler progress hidden behind a hit-rate graph with no visible per-URL state
- No board view that groups jobs by QUIC.cloud status with drag-to-retry semantics
- Audit history of queue resets and manual pulls is not exposed in the admin
SleekView Kanban
-
Live grouping by the
statuscolumn across crawler, CCSS, and image queues -
Drag-and-drop calls the same helpers the
Pullaction uses internally - Card fronts show path, QUIC.cloud job ID, original size, optimized size, and reason
- Per-user audit log records every column change with timestamp and source column
- Filters apply at the SQL level so QUIC.cloud queues with thousands of rows stay fast
Features
What SleekView Kanban gives you for LiteSpeed Cache
Group by real QUIC.cloud status
SleekView reads the queue status column LiteSpeed Cache writes during each notification, request, and pull cycle. The same values the Toolbox aggregates into counters now drive a column layout, so the board mirrors what QUIC.cloud actually returned for each URL or image row.
Drag to reset or retry
Every move writes back through the LiteSpeed helper layer. Dragging a Failed card to Queued resets the row and re-notifies the QUIC.cloud service. Dragging into Done forces a cache purge for the affected URL. Automatic cron pulls keep running alongside, no collisions.
See image savings on the card
QUIC.cloud returns the optimized size, the WebP variant size, and the savings percentage for every successful pull. SleekView shows those fields on the card front, so an editor can spot images where the savings are unusually low and flag the source asset for replacement.
Audience
How teams use the LiteSpeed Cache board
Failed image triage
Filter to Failed rows with a fetch error reason and drag the batch back to Queued. The queue re-notifies QUIC.cloud for each row on the next cron tick, often clearing transient upstream timeouts on the second attempt.
Crawler stall recovery
Filter to crawler rows in Processing for longer than the worker timeout and drag them back to Queued. The crawler reissues the warm-up request rather than waiting for the long timeout to expire on its own.
Savings audit by media folder
Filter Done rows by upload year and month and sort by savings percentage. The board surfaces folders where image optimization is underperforming, so the team can replace large source files before the next campaign.
The bigger picture
Why a kanban view changes LiteSpeed Cache operations
LiteSpeed Cache hides a lot of queues behind a small Toolbox screen. The crawler walks the sitemap to warm the page cache. The critical CSS pipeline notifies QUIC.cloud, waits for the pull, and stores the response.
Image optimization notifies QUIC.cloud per image and pulls back the WebP variant. Every one of those queues has a status column that flows from notified to requested to pulled, with a failed branch for transient upstream errors. The Toolbox reduces all of that to a counter and a Purge All toggle, which works on a small site and goes blind the moment any queue stalls.
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 are queued, how many are stuck in processing, 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 call internally. The Toolbox still exists, and still works for a one-button purge.
The board exists for the rest of the time, when the team needs to see the queues the way the queues already see themselves.
Questions
Common questions about SleekView Kanban for LiteSpeed Cache
Live. SleekView queries the same wp_litespeed_crawler, wp_litespeed_img_optm, and CCSS data tables that LiteSpeed Cache writes to during each cron tick. Filters apply at the SQL level, so a board scoped to today's stuck pulls reflects rows that are stuck right now, not yesterday's snapshot.
No. SleekView calls the same helper methods the cron tasks use internally for notification and retry. Automatic pulls continue to run normally. A manual board move and an automatic cron tick can both happen in the same minute without leaving the queue in an inconsistent status on disk.
Each queue runs in its own board to keep the columns meaningful, since the status values differ between CCSS and image queues. SleekView lets you save board presets so an operator can switch from the CCSS board to the image board with one click without rebuilding filters.
Yes. Every move runs through current_user_can('manage_options') before any LiteSpeed helper is called. A contributor account can drag cards for personal sorting but the change does not persist, with a toast notification explaining why the move was rejected by the capability check.
Filters are applied at the database query level rather than in JavaScript. A typical board scopes to a single upload year, to Failed rows only, or to Queued rows older than an hour, so the rendered card count stays under a thousand. Older entries remain queryable through saved filter views.
Yes. QUIC.cloud returns the optimized size and the WebP variant size on every successful pull. SleekView surfaces both fields and a derived savings percentage on the card front, so an editor can sort by savings when auditing image folders or by WebP flag when troubleshooting delivery.
Yes. The queue tables and QUIC.cloud integration run regardless of the web server. The page cache backend differs by server type but the kanban board reads the queue rows that LiteSpeed Cache writes either way, so an Nginx-fronted site sees the same image optimization view.
Yes. Every drag writes a meta entry naming the user, the source column, the destination column, and the timestamp. The entry lives in a SleekView audit table so audits, exports, and downstream automations can read the trail without a separate event log or external service integration.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout