Here is an uncomfortable truth about website performance: most slow pages are not slow because of bad code or a cheap host. They are slow because someone uploaded a 4MB photo straight from their phone and dropped it into a blog post. Images are typically the heaviest thing on a web page, which means image optimization is the single highest-leverage speed fix available to most site owners — and it directly affects how Google ranks you. This guide explains the connection and shows you how to fix it for free.
How images feed into your Google ranking
Google uses page experience as a ranking signal, measured through Core Web Vitals. Two of those metrics are dominated by images:
- Largest Contentful Paint (LCP) — how long the biggest visible element (often your hero image) takes to render. Google's "good" threshold is 2.5 seconds. A 3MB banner can drag LCP to 6–8 seconds on mobile.
- Cumulative Layout Shift (CLS) — how much the page jumps as things load. Images without declared width and height push surrounding content around, and a high CLS score hurts rankings.
Page speed is not the only ranking factor — relevance and content quality matter more — but when two pages are otherwise comparable, the faster one wins. And speed is something you fully control.
What "optimized" actually means in numbers
Optimization is not one setting; it is matching each image's weight to its job. Reasonable upper limits for web use:
| Image role | Target size | Notes |
|---|---|---|
| Hero / banner | under 200KB | Largest by area, so it dominates LCP. |
| Product / blog photo | under 100–150KB | Resize to display width first. |
| Thumbnail | under 30KB | Small on screen, so it should be small in bytes. |
A photo straight off a modern phone is 3–8MB. To meet these targets you are usually reducing file size by 95% or more — and almost none of that loss is visible, because you were never displaying that much detail in the first place.
Resize before you compress — the step everyone skips
Compression and resizing are different things, and the order matters. A 6000-pixel-wide camera photo displayed in a 800-pixel-wide column is wasting roughly 80% of its data before compression even starts. The efficient workflow is: resize the dimensions to (at most) the size it will display, then compress. Skipping the resize step is the most common reason "compressed" images are still too heavy. Our Image Resizer handles the first step; the compressor handles the second.
Choosing the right format
- WebP — Google's preferred web format, typically 25–35% smaller than JPG at the same visual quality. Use it wherever your site supports it (nearly all modern browsers do). Convert with our Image to WebP tool.
- JPG — the dependable default for photographs and any image with lots of colour and gradients.
- PNG — best only for logos, screenshots of text, and images that need transparency. PNG photos are needlessly huge; do not use PNG for photographs.
A 5-minute optimization routine for a blog post
- Resize each image to the maximum width it will display at.
- Convert photos to WebP (or compress as JPG if you need maximum compatibility).
- Run the batch through the Bulk Image Compressor in one pass.
- Add width and height attributes in your CMS so the layout does not shift while loading.
For a typical post with five images, this takes well under five minutes and can shave several megabytes off the page — often the difference between a "needs improvement" and a "good" Core Web Vitals score.
Frequently asked questions
Will compressing images hurt how they look?
At sensible settings, no — the tool discards detail your visitors were never going to see at display size. Quality loss only shows up if you compress aggressively and then display the image much larger than intended.
Does image optimization really move search rankings?
Indirectly but reliably. Faster pages improve Core Web Vitals and reduce bounce rate, both of which feed into ranking. It will not outrank genuinely better content, but among similar pages, speed is a tiebreaker you control.
Should I switch everything to WebP today?
For photos and decorative images, yes. Keep an original copy in case you ever need to re-export, but serve WebP to visitors.
What about alt text?
Separate from file size, but worth doing in the same pass: descriptive alt text helps accessibility and image search, and costs nothing.