I build and run ZipPic — known as zippic.app internationally and zippic.cn for Chinese users — a free toolkit of 18 media tools that run entirely in your browser. I spend most of my days thinking about one surprisingly neglected topic: how much your images are costing you in search rankings.
Here's the thing nobody tells you when you're obsessing over meta tags and backlinks: images are typically 50–70% of a page's total weight. And page speed — specifically Largest Contentful Paint — is a confirmed Google ranking factor. In other words, that beautiful 4MB hero PNG is quietly dragging your SEO down.
Why I care about this
A while back I was optimizing my own site's Core Web Vitals and discovered something embarrassing: my tool pages were slow because of the demo screenshots. The irony of a compression tool shipping uncompressed images was not lost on me.
That experience shaped how I think about image SEO. It's not a separate discipline — it's just performance work with a search-ranking payoff.
The three levers that actually matter
1. Pick the right format
This is the highest-ROI change most sites can make:
- Photos → WebP or AVIF (typically 30–50% smaller than JPG at the same quality)
- Graphics with transparency → WebP instead of PNG
- Simple icons/logos → SVG, always
I converted my entire site's imagery to WebP and watched LCP drop by over a second on mobile. One format change, no redesign.
2. Compress before you upload, not after
Most CMS "optimization" plugins compress images after they've already been uploaded at full size. That's backwards. The damage — slow uploads, wasted storage, oversized originals sitting on your CDN — is already done.
My workflow now: compress locally first, then upload the already-optimized file. Because zippic runs 100% in the browser via WebAssembly, there's nothing to install and no file ever leaves my machine — which matters when you're handling client assets.
3. Batch it or you won't do it
The reason most sites ship unoptimized images isn't ignorance — it's friction. Nobody wants to compress 40 blog images one by one.
Bulk processing changed this for me. Drag in a folder of images, pick WebP at 80% quality, download them all. Five minutes, done. If your tooling makes the right thing the easy thing, image SEO stops being a chore.
What the numbers look like
On a recent pass over my own content pages:
- Average image size: 1.2MB → 180KB (WebP, visually identical)
- Mobile LCP: 3.8s → 2.1s
- The pages that got faster also started ranking better for their target keywords within a few weeks
Correlation isn't causation, and I won't pretend image compression alone moves rankings. But when Google explicitly tells you speed matters, and images are most of your page weight, the math isn't complicated.
My honest take
You don't need my tool for this — Squoosh, Sharp, and plain old cwebp all work. What you need is the habit: right format, compressed before upload, in batches.
I built zippic because I wanted that workflow to have zero friction: no signup, no upload limits, no files leaving the browser. If that sounds useful, it's free at zippic.app — or zippic.cn if you're in China. 18 tools, 11 languages, everything local.
But even if you use something else: go compress your images this week. Your LCP — and probably your rankings — will thank you.
Disclosure: I'm the developer of ZipPic. The performance numbers above are from my own site.
Top comments (0)