CDN Enabler is a configuration-only plugin maintained by KeyCDN: it does not maintain its own database tables, instead storing settings in wp_options under the cdn_enabler key. That option holds the CDN host, the relative URL filter, the list of included directories (wp-content,wp-includes), and the exclusion list. The default admin shows everything as a single form with comma-separated textareas, which makes any audit a copy-paste exercise.

SleekView reads cdn_enabler and pivots it into flat rows. The CDN host becomes a top-level field, each included directory becomes a row with the count of files inside it, and each exclusion becomes a row with the count of front-end requests it removes from rewriting. Relative URL handling and TLS overrides surface in dedicated columns so the resolved behaviour is visible at a glance.

SleekView is honest about CDN Enabler's scope: the plugin does not store hit counts, purge events, or zone metrics because it never calls a CDN API. Counts come from indexing the WordPress filesystem and the rewrite filter, not from upstream logs. Inline edits write through the standard WordPress option API. Saved views like Exclusions with zero requests or Directories outside wp-content scope per role so a developer audits the configuration without exposure to the licence-less cdn_enabler option as a whole.

CDN Enabler is intentionally minimal. The plugin does one job, rewriting asset URLs from the local host to a CDN host, and it does it without analytics, dashboards, or upstream API calls. That minimalism is appropriate for the role, but it leaves no audit surface inside WordPress.

The default form keeps directories and exclusions as comma-separated lists, and nothing tells you whether an exclusion is doing anything or whether a directory still exists on disk. Most teams discover a stale exclusion only during a theme refactor, when a path referenced in excludes turns out to belong to a plugin removed last quarter. SleekView treats the cdn_enabler option as exactly what it is: a structured record with directories, exclusions, and toggles.

Each entry becomes a row, each exclusion gets a real match count, and each included directory shows its file count on disk. Developers can remove dead entries with confidence, agencies can audit configurations across client sites, and site owners can confirm coverage without learning a new admin. The plugin stays small; the audit gets first-class treatment.