RocketCDN is the CDN add on for WP Rocket. Its configuration lives inside the wp_rocket_settings option, with keys like cdn_cnames, cdn_zone, cdn_reject_files, and the boolean cdn. License and zone details from the RocketCDN dashboard are written to wp_options under rocketcdn_* keys. Per file exclusion patterns and reserved paths sit in the same options blob. The default UI is a single tab inside WP Rocket's settings screen, which is excellent for a one time setup but offers no list view of exclusions, no count of how many URLs each pattern affects, and no diff for recent changes.

SleekView reads those options and unpacks them into rows. One row per exclusion pattern can show its type, the post type or path it targets, and (when log data is available) how many rewrites it has affected. License and zone details appear in a companion view with the active CDN host, account email, and last sync time.

Inline edits route through WP Rocket's own settings update path, so the plugin keeps owning the runtime. Saved views like Active exclusions or Reserved paths can be scoped per role for delegating CDN tuning to a developer without exposing license keys.

CDN configuration is the kind of state that quietly drifts. A path gets added during a launch, an extension gets excluded to fix a font issue, and six months later nobody remembers why half the rules exist. RocketCDN's tab inside WP Rocket is fine for the initial setup but provides no surface for periodic review.

The exclusion list arrives as a textarea, and the CNAME field is a single line entry, so audit work means scrolling through a settings screen and trying to remember what was there last quarter. Performance engineers and SREs need this configuration as data they can sort and filter. SleekView reads the same options WP Rocket writes for the CDN, unpacks them into rows, and presents them as a queryable surface.

The result is that CDN posture reviews become real work instead of a checkbox someone defers.