Results and savings

Read your savings and understand skipped assets.

The dashboard shows what Inverity did to each asset: the original size, the optimized size, and the percentage saved.

Reading the numbers

Savings percentage is the reduction against the source file, per asset. It varies enormously by content and by how optimized your library already was — see Image optimization for what to expect.

Total saved is the aggregate across processed assets. This is the number worth reporting internally, because it maps directly to bandwidth and storage.

Skipped assets are ones Inverity chose not to replace. They are not errors.

Why was an asset skipped?

Sometimes you'll see an asset marked skipped — not smaller. This is normal and expected. It means the optimizer could not beat your original at equivalent quality, so it kept your original instead of shipping a larger or lower-quality file.

Common reasons:

The file was already well-optimized. If your image or video was already compressed efficiently — by a build step, a designer, or the platform that exported it — there may be no room to improve it without hurting quality.

The content is hard to compress. Very noisy or highly detailed content can be close to its optimal size already. Film grain, dense foliage, and heavy texture all resist compression by their nature.

The asset is very small. A 3 KB icon has almost no headroom; encoder overhead can exceed any saving.

A format conversion still happened. For video, if your source needed converting for browser compatibility (for example MOV or MKV to MP4), Inverity keeps the converted file even when it isn't smaller, because the compatibility is the benefit.

When a high skip rate is worth investigating

Skips are normal. A sudden change in the skip rate is a signal:

• If a folder that used to save 50% starts skipping most assets, someone probably changed the export settings upstream and is now uploading pre-compressed files.
• If skips jump right after a profile change, the new profile may be more conservative than the content needs.

Either way, the fix is upstream of Inverity, not inside it.

What counts toward my plan?

Your plan meters the volume of media you process each month, measured from the source file size.

• Counts: each image or video Inverity processes, by its original file size.
• Doesn't count: assets that are skipped (not smaller), and duplicates Inverity has already seen.

You're not charged volume for work that didn't produce a result. See Volume and usage.

Turning savings into a business number

Two multipliers make the aggregate figure meaningful to people outside the team:

• Bandwidth. Saved bytes per asset × how often that asset is served. A 400 KB saving on a homepage hero served a million times a month is 400 GB of egress.
• Storage. The saving applies once, but persists — including across every backup and replica of that library.

Next

• Re-running optimization — reprocess under new settings
• Quality and profiles — change the balance
• Quality and output troubleshooting