Find the bloat
Every image on the page, sorted by file size. Flagged when its natural dimensions exceed what's actually displayed. The kind that hurts Largest Contentful Paint.
A free Chrome extension that finds the heavy images on any page and compresses them with Sukat — entirely in your browser, never on a server.
Add to Chrome — Free
Every image on the page, sorted by file size. Flagged when its natural dimensions exceed what's actually displayed. The kind that hurts Largest Contentful Paint.
Hover any row in the audit and the matching image is outlined on the page and scrolled into view. No more hunting through DevTools to find the offender.
Send one image — or every flagged image — to Sukat in a single tab. Sukat receives the batch and hands you a ZIP. No upload, no account, no waiting in line.
Five clicks from "is this page slow?" to a folder of compressed images.
Privacy by design
The extension fetches an image's bytes from the host where it lives (your CDN, the site's origin server) and passes them to the open Sukat tab using Chrome's local inter-process messaging. The bytes travel inside your own browser — from the extension to Sukat — and are then compressed by Sukat's existing Canvas pipeline. No backend. No transit. No exception.
Source host → Your browser → Sukat
Every public release of Sukat Inspector, dated and versioned. Updates ship through the Chrome Web Store — if auto-updates are on, you're already on the latest.
The right-click menu gains Original vs Page-displayed sizing with live dimensions, multiple Compress clicks now collect into a single Sukat tab, and a new Social card preview catches broken or wrong-shape og:images that fly under the radar everywhere else.
og:image, og:title, twitter:image, and twitter:card values. Each card mirrors the platform's real typography, spacing, and image aspect ratios, so a title that gets truncated on X (but not on Facebook) is visible at a glance.og:image or twitter:image points to a URL that returns a 404 (or any non-2xx status), the row gets a red broken pill and the issue is called out at the top of the section. A broken og:image looks fine in your HTML — the tag is there, the URL parses — so it can quietly break every share for weeks. Now it surfaces immediately.og:image is shaped wrong for Facebook (which wants 1.91:1) or your twitter:image is too small for the chosen card type, you'll see both a per-image pill and a summary at the top of the section.twitter:image shape detection. The card-type lookup was reading from the wrong path and defaulting twitter:card to undefined — which meant twitter:image was always evaluated as the small summary card (expecting 1:1), even when the page declared summary_large_image (which wants 1.91:1). Pages with perfectly correct 1.91:1 Twitter images were getting falsely flagged. Fixed.Two new collapsible audit panels at the top of the popup — Page Metadata and Social & SEO Images — plus a Heavy flag that catches the byte-size cases the dimension-only audit was missing.
<title>, meta description, and canonical URL. Each card shows a live character count with warn/error thresholds (title: warn at 60c, error at 70c, warn under 30c; description: warn at 160c, error at 170c, warn under 70c) and a one-click copy button. Canonical is checked for presence and for matching the current URL (origin + path, ignoring query and fragment). When every check passes the section collapses to a single all good status.og:image, twitter:image, favicon, manifest icons. The header shows the count detected so you can see at a glance whether the page is complete on social previews.Heavy filter pill. A 1.99 MB photo served at its natural size — previously invisible to the dimension-only audit — now surfaces immediately.+N inline SVGs on page line surfaces SVG elements as context rather than mixing them into the file audit, since inline SVGs aren't downloadable files and don't belong in the compress pipeline.Compress N flagged (was Compress N oversized). It sends every oversized and heavy image in one batch.heavy column so the action list in the spreadsheet matches what's in the popup.Image() probe resolves naturalWidth/Height for images below the fold, so lazy-loaded photos stop silently skipping the audit. Each lazy image carries a lazy tag in its row so the cause of the catch is visible. The audit re-runs after the probe and after each file-size batch, so flags light up as data resolves.A focused security pass on how Inspector builds its UI from page data. No new features, no permission changes, nothing user-visible — just stricter, safer handling under the hood.
http: and https: links are followed when Inspector opens a tab or loads a thumbnail. Anything else is rejected before the request is made.onerror attribute.Images now list in the order they appear on the page, a resizable side panel keeps Inspector open while you work, you can scope by image format, and oversized images carry a clear “N× too big” badge. Larger pages also send more images per batch.
4× too big.First public release on the Chrome Web Store. Inspector audits images on any page, flags oversized files, and hands them off to Sukat in one click — without anything leaving the browser.
sukatapp.com/?import=<url>&ref=<source> so the round-trip stays clean and traceable.chrome.runtime.sendMessage. The image is never uploaded — Sukat's privacy promise carries over end-to-end.No. Free forever, no account required, no premium tier, no ads. Same model as the rest of Sukat.
No — the extension does nothing unless you click it. It doesn't run on every page you visit, doesn't track you, doesn't sit in the background fetching things. Open the popup, click Scan, and only then does it audit the current page.
Any website. WordPress sites, Shopify stores, custom React apps, static blogs — anywhere there's an <img> tag or CSS background image, Sukat Inspector can audit it.
Sukat (this website) is for compressing images you have — drag in a file, hit a file size target, download. Sukat Inspector is for finding images that need compressing on a webpage you're looking at. Use Inspector to find them, Sukat to fix them. The two pipe directly into each other.
Yes. The extension has no backend — there is literally no server we control that could receive your data. We don't use Google Analytics, advertising scripts, or any tracking in the extension itself. The only thing leaving your browser is the request to fetch image bytes from their original host — the same kind of request your browser makes when it loads the page normally. Full disclosure here.
Chrome and Chromium-based browsers (Edge, Brave, Arc, Vivaldi) work today. Firefox support is on the roadmap. Safari requires significant rework due to Apple's extension model and isn't planned yet.
Or just keep using sukatapp.com directly — the extension is the audit superpower, but the compressor is what you already love.