✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for ImageOptim: optimization queue & savings as tables

The ImageOptim WordPress plugin uploads images to the ImageOptim API and stores queue state and savings on each attachment in wp_postmeta. SleekView reads that data and turns the optimization library into a flat sortable table with savings, status, and queue position as proper columns.

♾️ Lifetime License available

SleekView table view for ImageOptim

Read your ImageOptim queue as one audit-shaped table

The ImageOptim WordPress plugin sends each upload to the ImageOptim API and writes the result on the attachment in wp_postmeta, including the optimized URL, the size before and after, and the queue state for pending and failed entries. The plugin's settings screen handles the API key and global behaviour, but the per-attachment list still uses default WordPress columns, so per-image savings and queue state live behind individual file dialogs.

SleekView reads the same postmeta keys ImageOptim writes and pivots them into proper columns on the attachment row. Original size, optimized size, percentage saved, queue status (pending, optimized, failed), API response time, and last optimized date all become sortable. Saved views like 'failed optimizations to retry', 'images pending for more than an hour', or 'biggest savings of the quarter' load in one click and can be shared with the team. A queue lane column makes the API throughput visible from the attachment list itself.

Inline actions trigger ImageOptim's own retry function, so retries use the configured API endpoint, quality, and retry policy. Bulk retries, bulk re-uploads, and per-uploader audits all run through the same hooks. The plugin keeps owning the API integration; SleekView gives the team a real list view for the optimization library it already produces.

Workflow

From ImageOptim postmeta to a queryable media library

1

Map the optimization keys

SleekView reads the postmeta keys ImageOptim writes on each attachment: original size, optimized size, queue state, last run, and API response time. All are pre-mapped to filterable columns.
2

Compose savings views

Choose file, original size, savings, last run, uploader, and status. Save views like Pending Over An Hour, Failed Last Week, or Biggest Savings This Quarter for the team.
3

Filter and group

Combine status, MIME, uploader, and upload year filters. Group by month or by uploader to roll savings totals up to the slice the team reports on.
4

Retry inline

Trigger ImageOptim's own retry from a row or as a bulk action. The API call and retry policy behave the same way as a retry from the plugin's screen.

Sample columns

A typical ImageOptim optimization view

One row per attachment with original size, savings, queue state, and last optimized date.
Source: wp_postmeta (ImageOptim keys) + wp_posts (attachments)
File Original Saved Last run Uploader Status
feature-hero.jpg 1.9 MB 63% May 12 alex@studio.co Optimized
case-grid.png 2.6 MB 48% May 11 ria@design.io Optimized
press-banner.jpg 4.2 MB tom@hello.dev Pending
legacy-poster.png 5.1 MB May 09 mia@brew.coop Failed

Comparison

Default ImageOptim admin vs SleekView

Default ImageOptim admin

  • Settings screen handles config but not per-attachment audits
  • Default WordPress media library list ignores ImageOptim postmeta
  • Per-image savings live behind individual file dialogs
  • Failed and pending entries are easy to miss at list level
  • Bulk retry needs the dedicated tool, not the media library

SleekView

  • Pivot original size, savings, queue state, and last run into proper columns
  • Filter by status, uploader, MIME type, and upload year together
  • Sort by savings or original size to plan the next batch of retries
  • Retry through ImageOptim's own API call so settings stay authoritative
  • Save views like Pending over an hour for the on-call rotation

Features

What SleekView gives you for ImageOptim

Per-image savings as columns

Original bytes, optimized bytes, and percentage saved sit on the row. Sort by savings to find the wins worth reporting and by size to find the next batch worth running.

Inline retry

Trigger ImageOptim's own retry from a row or as a bulk action. The API call, the quality setting, and the retry policy all behave the same way as a retry from the plugin's screen.

Status filters

Combine pending, optimized, failed, MIME, and upload year filters. Build a view of failed JPEGs from last week and clear them in one pass before the next deploy.

Audience

Who uses SleekView for ImageOptim

Performance teams

Audit savings and surface stalled queue entries. A view filtered to pending for more than an hour catches the API throughput edge cases before they affect page weight on the live site.

Site editors after migrations

Find every attachment that arrived in a bulk import and never made it through the queue. A failed and pending view with bulk retry clears the backlog without flipping back and forth between screens.

Agencies tracking savings

Hand a client a per-quarter savings summary. A grouped view by upload month gives total bytes saved and average percentage saved without exporting raw data to a spreadsheet.

The bigger picture

Why API-backed optimization needs an audit surface

ImageOptim works in the background. Each upload goes through the API, the result is recorded on the attachment, and the page weight numbers quietly improve. That is the shape the plugin solves elegantly.

The shape it leaves missing is the audit. APIs fail sometimes, queues stall sometimes, and bulk imports drop hundreds of files into the pipeline at once. None of that is visible from the default WordPress media library, which renders the same columns it has since 2010.

A performance lead needs to know which uploads are still pending and for how long. A site editor needs to find and retry the failures from yesterday's migration. An agency needs a per-quarter savings summary grouped by uploader or by month.

SleekView reads the same postmeta ImageOptim already writes and gives the team a flat, sortable, filterable list with savings, status, and queue lane as proper columns. The plugin keeps owning the API call; the table makes the result of that work legible at the scale the API runs at.

Questions

Common questions about SleekView for ImageOptim

Yes. The plugin uses the ImageOptim API to optimize each upload and stores the result on the attachment in wp_postmeta. SleekView reads those postmeta keys directly, so the columns and filters work the same whether the API is hosted by ImageOptim or by a self-hosted equivalent.

 

Yes. The retry action calls the plugin's own retry function, so the API key, the quality settings, and the retry policy apply the same as a retry from the plugin's admin screen. Bulk retry selects multiple rows for a single pass.

 

Yes. The dashboard view summarises total bytes saved and average percentage saved across optimized rows. A grouped view by upload month or by uploader breaks the totals down for editorial and budget conversations.

 

Only the formats ImageOptim itself supports. The plugin writes postmeta for the image formats it processes (JPEG, PNG, GIF, and modern formats where supported). Other attachments stay in the table with empty optimization cells, which makes it easy to see which uploads are in scope and which are not.

 

No. Pagination uses the same attachment indexes WordPress core uses, and saved views resolve in the database. The optimization columns read from cached postmeta and do not call the ImageOptim API on render, so the admin stays responsive on large libraries.

 

Yes. Any view exports to CSV with original size, optimized size, savings, queue state, and last run columns. A grouped export by month or by uploader gives the shape most agencies need for client savings reports.

 

Yes. The plugin handles the API call from the WordPress server, so SleekView never needs to reach the ImageOptim API directly. Sites behind basic auth, IP allow-lists, or restricted networks work the same as public sites for the optimization columns.

 

No. SleekView reads only the postmeta keys ImageOptim writes. Other optimizers like Smush or ShortPixel write their own keys, and a row can show both sets of columns side by side without either plugin stepping on the other.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView