Custom Fields Suite is the long-standing free alternative to ACF, known for storing field values in its own dedicated tables rather than in postmeta. That design is good for query performance and for keeping postmeta clean, but it also means the data sits in a place the standard WordPress admin does not surface at all. Editors see the field UI on the post screen; nobody on the team sees field coverage as a number.

SleekView Charts reads the cfs_values table CFS writes to, joins it with wp_posts and renders the result as chart cards. A Number card counts posts where every field in a chosen field group is populated. A Pie shows the field group split across post types. A Bar ranks the most-used field groups by associated post count. An Area trends value writes over time, useful when measuring whether a content sprint actually moved the model.

Because CFS uses its own tables, the cards are fast even on large content models. The same SleekView dataset powers the underlying table view, so filters cross over and inline edits go through CFS's update functions so any save hooks continue to apply.

Custom Fields Suite has stayed a quietly popular alternative to ACF largely because of two design choices: it stores values in its own tables and it keeps the field UI tight. Both choices pay off for performance and for postmeta hygiene, and both choices also make the data harder to see in aggregate from the standard WordPress admin. Editors interact with one record at a time; nobody on the team has a coverage number until somebody writes a SQL query.

SleekView Charts pulls the cfs_values table into the same dataset family as wp_posts and wp_postmeta, so the reporting layer reaches into CFS's own storage rather than ignoring it. Field group coverage becomes a KPI, loop usage becomes a Bar, value writes become a trend. The build that already runs CFS keeps every advantage of its design choice and gains the missing reporting layer for free.