Image Optimization SEO: Faster Pages and Images Google Can Use
Images are usually the heaviest part of a page and often the LCP element, so they decide a lot of your page speed. They are also content Google can show in Image search, if it can find and understand them. Image optimization for SEO covers both jobs: smaller, faster files, and images that are discoverable and described.
Why Image Optimization Matters for SEO
- Speed. On many templates the LCP element is an image, so its size and how early it loads set the largest contentful paint. Images without width and height also cause layout shifts.
- Image search. Google can only show images it can find, fetch and understand. Google's image SEO guide lists what it needs: an img element, a supported format, descriptive alt text and context on the page.
- Accessibility. Alt text is what a screen reader reads aloud. The same text helps search engines.
SEO ProCheck's complete guide to image SEO goes deeper into the search side. This guide stays practical: what to change, and how to check it on every page.
Image Formats Google Supports
Google Search indexes images referenced in the src of an img element in these formats (Google):
| Format | Compression | Transparency | Animation | Best for |
|---|---|---|---|---|
| AVIF | Lossy or lossless | ✓ | ✓ | Photos, smallest files |
| WebP | Lossy or lossless | ✓ | ✓ | Photos and graphics |
| JPEG | Lossy | – | – | Photos, fallback |
| PNG | Lossless | ✓ | – | Screenshots, sharp edges |
| SVG | Vector | ✓ | ✓ | Logos, icons |
| GIF | Lossless, 256 colors | ✓ | ✓ | Avoid; use video |
| BMP | None | – | – | Avoid |
AVIF and WebP usually give the smallest files for the same visual quality, and every current major browser shows both. Serve them with a picture element and keep a JPEG or PNG fallback. For animation, a short muted video is usually far smaller than a GIF. Make sure the file extension matches the real file type, as Google asks.
Image Size Targets at a Glance
| Target | Value | Source |
|---|---|---|
| Image file size to flag | over 100 KB | Image Over 100 KB |
| GIF file size to flag | over 100 KB | GIF Over 100 KB |
| Saving worth a new format | 4 KiB or more | Images Are Not Served in a Modern Format |
| Saving worth resizing | 4 KiB or more | Images Are Larger Than Displayed |
| Resolution too low below | 0.75 x pixel ratio x size | Image Resolution Is Too Low |
| Alt text too long over | 100 characters | Image Alt Text Over 100 Characters |
100 KB is a line to review, not a rule: a large hero photo may need more, and a 90 KB thumbnail is still far too big. What matters is that each image is no larger than the size it is shown at, times the screen's pixel ratio, and compressed in a modern format. Resizing a 4,000 pixel camera photo to the 1,200 pixels the layout uses often saves more than any format change.
Responsive Images and Lazy Loading
srcset lets the browser pick the right file for the screen. Google supports srcset and picture, and asks for a fallback in src because not every crawler reads them:
<picture>
<source type="image/avif" srcset="/img/sofa-800.avif 800w, /img/sofa-1600.avif 1600w">
<source type="image/webp" srcset="/img/sofa-800.webp 800w, /img/sofa-1600.webp 1600w">
<img src="/img/sofa-800.jpg" width="800" height="533" sizes="(min-width: 900px) 50vw, 100vw"
loading="lazy" decoding="async" alt="Green velvet three-seat sofa with oak legs">
</picture>
loading=lazy delays images below the first screen until the visitor scrolls near them, which saves data and frees the network for what is visible. It is right for most images and wrong for one: the LCP image, which should load at once with fetchpriority=high. web.dev's article on browser-level lazy loading covers the details. Google renders the page with a tall viewport, so native lazy loading does not hide images from it; lazy loading that only reacts to scroll events can.
| Image | loading | fetchpriority | width and height |
|---|---|---|---|
| LCP or hero image | eager (default) | high | ✓ |
| Other images on the first screen | eager (default) | auto | ✓ |
| Images below the first screen | lazy | auto | ✓ |
Alt Text, File Names and Context
Google calls alt text the most important attribute for images. Write what the image shows, in the words of the page, and keep it short. Leave alt empty only for decorative images.
| Alt text | Verdict |
|---|---|
| (missing) | – Not described |
| IMG_2034.jpg | – File name |
| sofa sofas cheap sofa best sofa | – Keyword stuffing |
| Sofa | ◐ Too vague |
| Green velvet three-seat sofa with oak legs | ✓ |
File names help a little too: green-velvet-sofa.jpg says more than DSC0042.jpg. The text around the image, the caption and the page title give it context. Images in CSS backgrounds are not indexed at all: Google's guide says plainly that it does not index CSS images, so any image that matters belongs in an img element.
We found this on our own site: the Neova crawl of seoprocheck.com on October 17, 2026 flagged 2 images without alt text across 4,561 HTML pages. Small, but each one is an image a screen reader announces only by its file name. SEO ProCheck's alt text glossary entry has the short definition.
Let Google Fetch Your Images
An image Google cannot fetch cannot appear in Image search. The usual blocks:
- robots.txt. A Disallow on /wp-content/, /media/ or an image CDN path blocks Googlebot-Image.
- noimageindex in meta robots or an X-Robots-Tag header.
- Images only added by script after interaction, or only in CSS.
- Broken or redirecting image URLs after a migration.
We found the first one on our own site. During our SEO pass on November 20, 2026, the favicon files on neova.app sat behind a Disallow: / rule, so Google showed a plain letter instead of the logo next to neova.app in results. Allowing /favicon and /apple-touch-icon.png in robots.txt fixed it. A quick look at your own rules is below; the robots.txt tester guide shows how to test a path properly:
curl -s https://www.example.com/robots.txt | grep -iE "disallow|user-agent"
Image sitemaps help Google find images it might miss, including images on a CDN on another domain.
Image Optimization Checklist
| Check | Speed | Image search |
|---|---|---|
| Modern format with fallback | ✓ | ◐ |
| Resized to displayed size | ✓ | – |
| Compressed | ✓ | – |
| width and height set | ✓ CLS | – |
| LCP image not lazy, high priority | ✓ LCP | – |
| Other images lazy-loaded | ✓ | – |
| Descriptive alt text | – | ✓ |
| img element, not CSS | ◐ | ✓ |
| Not blocked by robots.txt | – | ✓ |
| Descriptive file name | – | ◐ |
Check Every Image With Neova
Neova's Images category lists every image the crawl fetched or a page uses, with its size, its alt text and how many HTML pages use it. On large sites, Image Sample fetches the images of the first 1 to 100 pages of each page group instead of all of them, or Skip Images leaves the rest while alt text is still read from every page. The checks:
- Image Is Missing Alt Text and Alt Text Is a File Name or Placeholder Name
- Image Width and Height Are Not Set
- Images Are Not Efficiently Compressed, with Lighthouse
- LCP Image Is Not Discoverable, Not Prioritized or Lazy-Loaded and LCP Image Is Lazy-Loaded
- Image Is Displayed at the Wrong Aspect Ratio, with JavaScript rendering on
- HTML Page Uses an Image Disallowed by robots.txt
- Content Image Is Delivered as a CSS Background, with the AI reader
Every check runs on every plan, Free included, on up to 1,000 URLs a crawl, on
Questions
What is image optimization in SEO?
Making images small and fast, in the right format and size, so pages load quickly, and making them easy for search engines to find and understand, with img elements, descriptive alt text and nothing blocking them in robots.txt.
What is the best image format for SEO?
AVIF or WebP for photos, with a JPEG fallback; SVG for logos and icons; PNG for screenshots that need sharp edges. Google indexes all of them in an img element.
How large should images be for a website?
No wider than the size they are shown at times the screen's pixel ratio, and compressed. Review anything over 100 KB; a typical content image can usually be well under that in WebP or AVIF.
Does Google index CSS background images?
No. Google's image guidelines say it does not index CSS images. Put any image you want in Image search in an img element with alt text.
Does lazy loading hurt SEO?
Native loading=lazy does not hide images from Google. It hurts speed only on the LCP image, which should load at once. Script-based lazy loading that waits for scroll events can keep images from being found.