speed-lens

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.

29Perf

https://gempages.net/

mobile · viewport 1366×900 @1x · 22 images (+11 offscreen) · 27d ago

＋ New audit

SlowExpert read of this page's load speed

Lighthouse scores this page 29/100 on mobile — slow. The main drag is Largest Contentful Paint, First Contentful Paint, Speed Index, Total Blocking Time, and Time to Interactive (12.1 s, 8.4 s, 8.4 s, 1,970 ms, 22.1 s). Compress/preload the LCP image and cut render-blocking CSS & JS. On image weight specifically, you're shipping 6.6 MB (94%) more than needed across 22 images — and since LCP is weak, right-sizing the hero image is the single highest-leverage fix here.

Cut 6.6 MB of image weight (resize to render size + WebP) — see the table below.
Largest Contentful Paint (12.1 s): compress/preload the LCP image and cut render-blocking CSS & JS.
First Contentful Paint (8.4 s): lower server response time (TTFB) and remove render-blocking resources.
Speed Index (8.4 s): prioritize above-the-fold content and defer offscreen work.
Total Blocking Time (1,970 ms): break up long JavaScript tasks and drop unused third-party scripts.

Real-world data — Chrome UX Report, 28-day p75 from real visitors

LCP

4.1 s

FCP

4.2 s

INP

657 ms

CLS

0.00

TTFB

907 ms

Lab metrics — Lighthouse simulated

Largest Contentful Paint

12.1 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.4 s

how long until the very first text or image shows up — a problem here (target ≤ 1.8s).

Speed Index

8.4 s

how quickly the page visually fills in — a problem here (target ≤ 3.4s).

Total Blocking Time

1,970 ms

how long the main thread was frozen — i.e. how long taps/clicks feel dead — a problem here (target ≤ 200ms).

Cumulative Layout Shift

how much the layout jumps around while loading — healthy here (target ≤ 0.1).

Time to Interactive

22.1 s

how long until the page reliably responds to input — a problem here (target ≤ 3.8s).

Conclusion — image weight you can cut (resize to render size + WebP)

−6.6 MB (94% lighter)

after 406.0 KBsaved 6.6 MB

21 of 22 images optimizable 21 oversized for their slot 21 not in a modern format Biggest win: −1.7 MB (Frame_1321314627)

Images by savings

Frame_1321314627

backgroundpng

↳ oversized: 2880px served for a 1366px slot↳ format: png → webp

2880×2456 → shown 1366×11462 · 1.8 MB → 89.0 KB

−1.7 MB

95% smaller

speed-lens

Real-world data — Chrome UX Report, 28-day p75 from real visitors

Lab metrics — Lighthouse simulated

Images by savings

PageSpeed opportunities — 2 fixable issues

Diagnostics