The official Cloudflare WordPress plugin gives a small analytics summary on its own screen: total visitors, bandwidth saved, threats blocked, and cache hit ratio. The numbers come from Cloudflare's API and land in cloudflare_analytics. The summary is a useful headline, but once a site grows it starts hiding the interesting questions. Has cache hit ratio drifted after a content release? Which day did threats blocked spike, and why? Is bandwidth saved trending up faster than visitors?

SleekView Charts reads the same data as a normal source. A Number KPI carries cache hit ratio from the latest analytics snapshot, a Donut splits requests across cache hits, misses, and bypasses, a Horizontal Bar ranks days by threats blocked, and a Gradient Area traces bandwidth saved over the selected window. Purge events from the plugin's own cron join in for a fifth view when needed.

The Cloudflare plugin keeps polling the API on its schedule. Charts query the same option keys the plugin writes after each sync, and saved dashboards can be scoped per role so a hosting support team reads cache health while a security lead watches the threats trend. No second store, no separate API calls.

The Cloudflare WordPress plugin pulls a small analytics snapshot from the API on a schedule, which is exactly enough data to be useful and exactly little enough to feel cramped on a single summary screen. The data needed to spot a trend already exists in the same options the plugin writes after every sync. Visualising those values as Number, Pie, Bar, and Area cards costs nothing on the writing side and reframes the same summary as a real dashboard.

The cadence of edge review shifts from a quarterly look at the Cloudflare app to a daily glance inside WP Admin, and the options stay exactly where the plugin wrote them.