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.
MiddlingExpert read of this page's load speed
Lighthouse scores this page 57/100 on mobile — middling. The main drag is Largest Contentful Paint, First Contentful Paint, Speed Index, and Time to Interactive (10.8 s, 8.7 s, 8.7 s, 10.8 s). Compress/preload the LCP image and cut render-blocking CSS & JS. On image weight specifically, you're shipping 1.5 MB (69%) more than needed across 31 images — and since LCP is weak, right-sizing the hero image is the single highest-leverage fix here.
- Cut 1.5 MB of image weight (resize to render size + WebP) — see the table below.
- Largest Contentful Paint (10.8 s): compress/preload the LCP image and cut render-blocking CSS & JS.
- First Contentful Paint (8.7 s): lower server response time (TTFB) and remove render-blocking resources.
- Speed Index (8.7 s): prioritize above-the-fold content and defer offscreen work.
- Time to Interactive (10.8 s): reduce JavaScript execution and defer non-critical scripts.
Largest Contentful Paint
10.8 s
how long until the biggest thing above the fold (usually the hero image or headline) finishes painting — a problem here (target ≤ 2.5s).
First Contentful Paint
8.7 s
how long until the very first text or image shows up — a problem here (target ≤ 1.8s).
Speed Index
8.7 s
how quickly the page visually fills in — a problem 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
10.8 s
how long until the page reliably responds to input — a problem here (target ≤ 3.8s).