LiteSpeed Cache uses several tables to track its work: wp_litespeed_crawler stores crawler runs and per-URL status; wp_litespeed_img_optm tracks image optimization through QUIC.cloud with WebP and lossy results; wp_litespeed_url stores normalized URL records for crawler and CSS optimization; the litespeed.conf.* options blob holds CCSS, UCSS, and unique CSS hashes. The default LSCWP admin shows each of these as separate screens with limited cross-filtering, and quota usage for QUIC.cloud sits on a different tab from the crawler logs that consume it.

SleekView reads each LSCWP table directly so the crawler, image optimization, and CCSS/UCSS data become a single workspace. Sort crawler runs by completion time and status, filter to QUIC.cloud requests in the failed bucket, or join image optimization rows with the WordPress attachment posts to see which media library items were processed and which still need WebP. ESI block data, when ESI is in use, surfaces as its own view with the placeholder name, post type, and last refresh.

SleekView is read-only against the LSCWP tables and writes only through LiteSpeed Cache's own functions for inline purge or re-queue actions. The plugin keeps managing crawler schedules and the QUIC.cloud integration on its own; SleekView just makes the audit data legible. Saved views like Crawler runs failed today or Images pending WebP can be scoped per role, useful for handing performance triage to a developer without exposing the QUIC.cloud API key or domain key settings.

LiteSpeed Cache covers a wide surface area: page caching through the LiteSpeed Web Server, a crawler that pre-warms URLs, image optimization through QUIC.cloud, CSS optimization with CCSS and UCSS hashes, and ESI for hole-punching dynamic blocks. Each feature carries its own admin screen, its own logs, and its own quota. The plugin reports each one well in isolation, but the work that performance teams actually do crosses those boundaries: which URLs failed in the latest crawler run, which images on those URLs are still missing WebP, and which CCSS hash they use.

The default UI does not let you ask that compound question without flipping between four screens. SleekView reads the LSCWP tables directly and presents them as joinable sources. Crawler results sit next to the image optimization and CSS hash data they relate to, quota usage becomes visible alongside the requests that consume it, and triage stops feeling like detective work.

The plugin keeps doing the heavy lifting; SleekView just lets the team responsible for performance read the data in the shape they actually need it.