WP Rocket keeps its full configuration inside a single serialized array on the wp_rocket_settings option row in wp_options. That array stores cache lifespan, file optimization flags (minify, combine, defer, delay JS), CDN URLs, exclusion lists for URLs and cookies, preload settings, and the lazyload configuration. There are no custom tables.

The default WP Rocket admin spreads those settings across Cache, File Optimization, Media, Preload, Advanced Rules, and Database tabs. To audit which URL exclusions are still relevant, what is in the JavaScript delay list, or which cookies bypass cache, an admin has to flip between tabs and copy values out by hand. SleekView reads the wp_rocket_settings option directly and unpacks it into a grid of named settings, current values, and per-list entries.

Inline edits write back to wp_rocket_settings using WP Rocket's own option-update hooks, so the cache invalidates correctly, advanced rules regenerate, and the .htaccess and config files refresh wherever WP Rocket regenerates them.

WP Rocket is excellent at making sites fast. The problem is that its configuration grew with the plugin: caching, file optimization, media, preload, advanced rules, database, CDN, RUCSS, all spread across tabs and lists. A site running WP Rocket for three years accumulates stale URL exclusions, cookies that no longer exist, JavaScript delay entries for libraries that were removed, and a CDN URL nobody remembers setting.

Auditing all of that requires opening each tab and scrolling textareas. SleekView turns the wp_rocket_settings option into a real grid. Every setting becomes a row with name, value, group, risk, and last-changed timestamp.

URL and cookie exclusions become editable lists. Admins filter the grid for stale entries, performance engineers sort by risk to find changes that need testing, and agency leads export a configuration snapshot per client. Edits route through WP Rocket's own option-update hooks, so the cache regenerates and the config files refresh wherever WP Rocket already runs them.

WP Rocket does the caching. SleekView just makes the configuration auditable at the scale long-running sites actually need.