TinyPNG writes per-attachment compression data to wp_postmeta under keys like tiny_compress_images, with one serialized record per registered image size that stores the original bytes, compressed bytes, the timestamp, and the API response. Plugin configuration and the monthly quota counter live in wp_options under tinypng_*. The default Media Library shows a small status string next to each attachment and an aggregate count on the settings screen, but there is no admin grid that lists every compressed file with its savings and the size variants that succeeded or failed.

SleekView reads the postmeta and options TinyPNG already writes and surfaces them as flat rows. One row per attachment can show the file name, the post type that uses it, total bytes saved, the size variants compressed, the variants still pending, and the date of the last API call. Sort by savings to find the heaviest payoff candidates that have not been touched yet, filter to errors only after a quota lapse, or group by MIME type to compare PNG and JPEG behaviour across the library.

SleekView never bypasses TinyPNG's pipeline. Inline actions trigger the plugin's own compression hooks through Tiny_Compress::compress, so credits, quota counters, and the per-size status fields stay authoritative. Saved views like Errors this month or Uncompressed over 1 MB can be scoped per role, useful for handing a media cleanup project to an editor without exposing the API key in the settings tab.

TinyPNG works best when it is invisible. Upload an image, the plugin compresses it on the way in, and the original file gets a tidier counterpart on disk. The trouble starts when something goes quietly wrong.

The free plan hits its monthly cap, a registered image size is missing from tinypng_sizes, or a batch retry stalls on an oversized PNG. The default admin shows aggregate counts and a status string per attachment, but it never shows the library as a ledger. Most teams notice a compression gap only when a page weight report flags an outlier, then dig through serialized postmeta by hand to confirm what happened.

SleekView reframes the same data as exactly what it already is: one row per attachment with original bytes, compressed bytes, variant progress, and last run timestamp. Failures sort to the top, large uncompressed files become a punch list, and editors can run retries without ever seeing the API key. The plugin keeps doing what it does best while the team responsible for media weight gets a surface they can actually read.