Why it matters
Images are usually the heaviest part of a blog post. Uploading straight from a camera or design tool can mean multi-megabyte files displayed 800 pixels wide. Slow pages lose readers and hurt Core Web Vitals.
How to fix it
Check the page details for heavy images and images without dimensions.
Resize images to roughly the largest size they're shown at.
Compress them and convert to WebP or AVIF; most image plugins and CDNs automate this.
Add width and height attributes to every <img> so the browser reserves space.
Lazy-load images below the fold with loading="lazy", but not the first one.
How That One Crawler checks it
Heavy imagesWarning
Images over 300 KB slow the page down, especially on mobile.
Fix: Compress them, resize to the displayed size and serve WebP or AVIF.
Images without dimensionsNotice
Images without width and height make the layout jump while loading (Cumulative Layout Shift). Absolutely positioned images, like Next.js "fill" images, can't shift the layout and aren't counted.
Fix: Add width and height attributes (or a CSS aspect-ratio) to every <img>.
Frequently asked questions
What image size is too big for a blog?
As a rule of thumb, keep most images under 200–300 KB. Hero images can be a little larger if they're well compressed.
How do you weigh responsive images?
Like a browser would. We pick the srcset variant a desktop browser downloads, not the oversized fallback in src, and ask for WebP or AVIF the way Chrome does, so image CDNs answer with the file a visitor really gets.
Does WebP really make a difference?
Yes. WebP and AVIF files are typically 25–50% smaller than JPEG at similar quality, which speeds up every page they're on.
Find every page with this problem
Free, no signup, results in a couple of minutes. Your scans stay in your browser.