Enter a URL — it pulls a PageSpeed Insights audit and loads the page in a real browser to measure every image's actual rendered size, then shows the bytes you can save by resizing + WebP. Optimized images ready to download.
Tip: paste a product or landing page — that's where oversized hero images usually hide.
Lighthouse scores this page 100/100 on mobile — fast. All Core Web Vitals are in the green — solid foundation. Images are already lean — no meaningful resize/format savings found across 0 images.
Lab metrics — Lighthouse simulated
Largest Contentful Paint
0.8 s
how long until the biggest thing above the fold (usually the hero image or headline) finishes painting — healthy here (target ≤ 2.5s).
First Contentful Paint
0.8 s
how long until the very first text or image shows up — healthy here (target ≤ 1.8s).
Speed Index
0.8 s
how quickly the page visually fills in — healthy here (target ≤ 3.4s).
Total Blocking Time
0 ms
how long the main thread was frozen — i.e. how long taps/clicks feel dead — healthy here (target ≤ 200ms).
Cumulative Layout Shift
0
how much the layout jumps around while loading — healthy here (target ≤ 0.1).
Time to Interactive
0.8 s
how long until the page reliably responds to input — healthy here (target ≤ 3.8s).
No raster images detected on load
The audit didn't find images it could optimize. Common reasons:
The page lazy-loads images only on deeper interaction (carousels, tabs) that a one-pass crawl doesn't trigger.
Images are served as SVG (vector — nothing to resize) or as CSS that didn't resolve.
The site may serve a lighter page to datacenter IPs (bot protection), so fewer images load than for a real visitor.
Try the desktop strategy, or a more image-heavy page (a product or landing page).
Auditing the page…
Starting up
Runs Lighthouse + loads the page in a real browser. Usually 20–60s.