Skip to content

Technical SEO · guide 5 of 7

Image SEO: faster photos that Google can find and understand

Why your hero photo may be your slowest asset, and how sizing, formats, lazy loading, alt text and file names make images load fast and show up in Google.

26 min readUpdated 9 Nov 2026

  • 9 questions to test yourself
  • 2 calculators
  • 8-item checklist
On this page11 sections

The photo you love may be the slowest thing on your site

You paid for good photography, or took the shots yourself on a new phone, and they look wonderful. Then someone tells you the site is slow on mobile. You look at the page and see nothing heavy: a logo, a headline, a few buttons and one beautiful photo across the top.

That photo is the first suspect. In the next two minutes you can find out how heavy it really is, and in an afternoon you can usually fix it for free. Along the way: five habits (size, format, compression, loading order and description) that make photos load fast and show up in Google Images and Google Lens.

Two things to watch for as you read. There is one setting, often switched on with the best intentions, that makes a perfectly optimised hero photo arrive late; we will come back to it. And there is a report most owners have never opened that shows whether your photos already bring you customers. First, a guess.

Quick quiz

A florist’s homepage takes about six seconds to look ready on a phone. It has a logo, a short headline, a booking button and one large photo of a bouquet. What is the most likely cause?

Pick one. Your first answer is the one that counts.

Two jobs every image has: arrive fast, and be understood

An image on your site has two separate jobs, and most owners only think about one of them.

The first job is speed. Google’s Core Web Vitals include Largest Contentful Paint (LCP): the time until the biggest thing on the first screen appears. Google counts 2.5 seconds or less as good. On many pages that biggest thing is a photo, so the hero image often sets your LCP almost on its own. Google says page experience, speed included, is one signal among many and that relevant content still matters most; the bigger cost of a slow photo is the visitor who gives up before it appears.

The second job is being understood. Google works out what an image shows from the image itself, the alt text, the file name and the words around it. Get those right and your photos can appear in Google Images, Lens and the image strips inside normal results. None of this guarantees a ranking: good images remove reasons to leave and help Google understand a page, but they do not turn a weak page into a strong one.

The fixes for both jobs are the same few habits, done once when you upload. If you want the full picture of LCP and the two other measures first, the guide on Core Web Vitals explains them without the jargon; you do not need it to follow this one. Before any of the habits, get your own numbers: the rest of the guide is more useful with them.

Step by step

Check your own hero photo in two minutes

Step 1 of 4

Open the photo on its own

On a laptop, right-click your homepage’s main photo and choose “Open image in new tab”. In Chrome and Firefox the tab title shows its size in pixels, for example 4032 × 3024. Write down the first number: that is the width you will use in the calculator below.

Sizing: the single biggest win, and the one almost everyone skips

A typical 12-megapixel phone photo is 4032 pixels wide. On a phone screen, your hero box is usually around 360 to 430 “CSS pixels” wide. Modern phone screens pack two or three real pixels into each of those, so a sharp image there needs roughly 700 to 1,300 pixels of width. Everything beyond that is downloaded, decoded and then thrown away.

So how much bigger is that 4,032 px photo than the screen needs? Most people answer with the width: about three times. Make your own guess first.

  • Resize before you upload. A good rule of thumb is about twice the width the image is shown at, and rarely more than 2,000 to 2,500 px even for a full-width desktop banner.
  • Let the site offer several sizes. Responsive images (the srcset attribute) let each phone or laptop download the version that fits it. WordPress has created these sizes automatically for years, and Shopify, Wix and Squarespace resize on their own image servers in most themes. A hand-built site may need a developer to set it up.
  • Check what visitors actually get. Your platform may resize, but a theme can still request the original. PageSpeed Insights points this out in its image delivery advice.

Make a guess

A 4,032 × 3,024 phone photo is shown 400 px wide on a phone with a 3× screen, which needs 1,200 px of width. How many times more pixels does the photo carry than the screen can use?

3× as many
1× as many30× as many

Anything within ±3× as many counts as right.

Use three numbers: your photo’s width, the width it appears at, and the screen’s pixel density (3 for most recent iPhones and many Android flagships, 2 for many other phones and laptops).

Try the numbers

How many more pixels is your photo than the screen needs?

4,000 px
400 px
3×

Widest version this screen can use

1,200 px

Pixels sent compared with pixels needed

11.1× as many

Simple geometry for one image on one screen, assuming the shape stays the same. If the second number is above about 2×, resizing is your first fix; the first number is roughly the width to resize to. Do the sum for desktop too: a full-width banner on a laptop may be shown 1,400 px wide at density 2.

Formats: JPEG, PNG, WebP, AVIF and SVG in one table

The format is the way the pixels are packed into a file. The same photo can be a few hundred kilobytes in one format and several megabytes in another, with no difference anyone would notice. But before you start converting everything, a question of priorities.

Quick quiz

Your hero is a 4,000 px wide JPEG, shown about 800 px wide. You have time for one change before lunch. Which usually saves the most weight?

Pick one. Your first answer is the one that counts.

Side by side

FormatBest forWatch out for
JPEGPhotos, everywhere. Every browser and tool supports it.No transparency. Heavy if saved at maximum quality.
PNGScreenshots, simple graphics, images that need a transparent background.Huge for photos. A photo saved as PNG is a common cause of multi-megabyte pages.
WebPPhotos and graphics on the web. Supported by all current major browsers.Some older desktop software will not open it, which only matters for files people download.
AVIFPhotos where every kilobyte counts; often smaller again than WebP.Slower to create, and support in tools and some platforms is newer. Check your platform handles it.
SVGLogos, icons and simple illustrations. Sharp at any size, often tiny.Not for photos. Only upload SVGs from a source you trust.
Google Search supports all of these formats for indexing. Many platforms now convert uploads to WebP or AVIF for you, so check before you convert by hand.

Compression: how much your page actually has to carry

Compression is how hard the file is squeezed. Photos saved for print or straight from the camera use very high quality settings that the eye cannot tell apart on a screen. As a rule of thumb, many photos look the same to visitors at a quality setting somewhere around 75 to 85, at a fraction of the weight. Judge with your own eyes, at the size the photo is shown, not zoomed in to 400%.

Weight adds up fast on gallery, menu and product pages. Put in your own page below.

Try the numbers

How much does your photo page weigh?

12 photos
2,500 KB
10 Mbps

Total photo weight

30 MB

Time just to download them at full speed

24 seconds

Same photos at 150 KB each

1.8 MB

Pure arithmetic on your numbers, not a measurement. Real loads are usually slower (connections rarely run at full speed), while lazy loading means not every photo is needed at once. The gap between the first and last number is roughly the weight compression and resizing can take off this page.

If your numbers came out in the tens of megabytes, you are in common company. The Fenerche Lamps study on our Case studies page follows a lamp shop whose camera-sized product photos of 4 to 8 MB each were the biggest of several speed problems, and the order it fixed them in. It is an illustrative example, an invented shop with modelled figures, not a client result.

Step by step

A ten-minute routine for every new photo

Step 1 of 5

Pick and crop

Crop to the shape the site shows it in. Cropping away empty sky or floor is free weight loss and usually a better photo.

Lazy loading: helpful for the gallery, harmful for the hero

Lazy loading tells the browser to wait before fetching an image until the visitor scrolls near it. On a long page of photos that saves a lot of data. Modern browsers support it natively with a single attribute, loading="lazy", and many platforms and speed plugins add it automatically.

Here is the setting promised at the start. If the hero photo is lazy-loaded too, the browser deliberately waits before fetching the most important image on the page, so all your resizing work arrives late. Google’s web.dev guidance on LCP says not to lazy-load images that are visible when the page opens. Developers can go further and mark the hero with fetchpriority="high" so the browser fetches it first.

The trap is that “lazy-load all images” sounds like pure good sense, which is why a plugin or theme often switches it on for everything. Test yourself on the beliefs around it.

Myth or fact?

Four beliefs about loading images

For each one: myth or fact?0 of 4 answered
  1. 1.Lazy loading every image on the page always makes it faster.

  2. 2.Setting a width and height on each image stops the page jumping as photos load.

  3. 3.Googlebot scrolls down your pages like a visitor, so any lazy-loading trick is fine.

  4. 4.A lighter hero photo can improve your Largest Contentful Paint.

Alt text: describe the photo to someone on the phone

Alt text is the short description stored with an image. Screen readers read it aloud to blind and partially sighted visitors, browsers show it when an image fails to load, and Google says it uses alt text, together with computer vision and the page around the image, to understand what the image shows. When an image is a link, its alt text also works like the link’s words.

The test is simple: imagine describing the photo to a customer on the phone, in one sentence, in the words they would use. Try it.

What would you do?

An illustrative example: a furniture maker’s product photo

A small workshop (made up for this example) sells a six-seat walnut dining table with tapered legs and an oiled finish. The main product photo shows the table in a bright room. The upload screen has an empty alt text field.

What should go in the alt text?

A few rules cover almost every case:

  • Describe what is in the image, specifically. “Plumber fitting a combi boiler in a kitchen” beats “plumbing services”.
  • Keep it to a sentence. There is no official character limit, but long alt text is tiring to listen to.
  • Do not start with “image of” or “photo of”. Screen readers already announce that it is an image.
  • Use empty alt text (alt="") for decoration, so screen readers skip it. Leaving the attribute out completely is different and worse: some screen readers then read the file name aloud.
  • If the image contains words, such as a menu or a poster, put those words in the alt text or, better, in the page text itself.

File names and the words around the photo

Google’s documentation says a file name can give it clues about what an image shows, and gives the example that a name like my-new-black-kitten.jpg is better than IMG00023.JPG. It is a small signal, but it costs only seconds, and it also keeps your own media library searchable.

Use lower-case words joined by hyphens, describe the subject, and stop. If your site is in several languages and you have separate images per language, translate the file names too. Rename new photos before you upload them; renaming an old photo changes its address, so leave the ones that already bring visits from Google Images alone. Try renaming these before you flip them.

Test yourself

Think of your answer, then flip the card.0 of 4 flipped

The page around the image matters more than the file name. Google uses the text near an image, captions and the page title to understand it. A photo of a walnut table on a page about walnut tables, with a caption saying so, is easy to understand. The same photo on a page called “Gallery” with no words is a puzzle.

Put your most important image near the top of the relevant page, near the heading it illustrates, and give each image one clear home. If a photo matters to your business, write a sentence about it.

Getting found in Google Images, Lens and product results

Image search is not only people browsing pictures. People photograph a chair they like with Google Lens and ask where to buy it, or search for a dish and pick the restaurant whose photo looks best. For anything visual, an original photo can be the thing that earns the click.

Here is the report promised at the start. In Google Search Console, open the Performance report and switch “Search type” from Web to Image. You will see which pages and searches bring visits through Google Images. Owners who look usually find one of two things: a source of visits they never knew about, or nothing at all, which tells you image search is an opportunity you have not used yet. If you have never opened Search Console, the guide to it is a 20-minute tour that starts with setting it up.

  • Use original photos where you can. Stock photos are not penalised, but the same photo appears on hundreds of sites, so it gives nobody a reason to pick yours.
  • Make the image crawlable: a normal image tag, not a CSS background, on a page Google can index.
  • For shops, product structured data (schema markup) with an image tells Google which photo belongs to which product, which helps it show your products with photos in shopping-style results. The guide on schema markup covers which types are worth adding, and the guide on product pages shows how photos, descriptions and reviews work together on a page that sells.
  • If your images are loaded by unusual scripts, an image sitemap can help Google find them. Most small sites on mainstream platforms do not need one.

Quick quiz

A café’s best-selling cinnamon bun deserves to be found in Google Images. Which setup gives its photo the best chance?

Pick one. Your first answer is the one that counts.

To see these habits applied to a whole image-heavy site, read the Atelier Rouille study on our Case studies page: a print studio in Lyon whose twelve-megabyte hero images, missing alt text and JavaScript galleries kept its work out of image and shopping results. Like every study there, it is an illustrative example with an invented business and modelled figures, not a client result.

How your images score today

Be honest: “partly” is a perfectly good answer, and you can check most of these in a few minutes with the speed test at the end of this guide and your site’s media library.

Score yourself

Your images, point by point

  1. The big image on my homepage is resized to roughly the size it is shown at, not straight from the camera.

  2. My photos are served as WebP or AVIF, or as well-compressed JPEGs.

  3. Images further down the page lazy-load, and the hero image does not.

  4. Images have a width and height set, so the page does not jump while they load.

  5. Important photos have specific alt text; decorative ones have empty alt text.

  6. File names describe what is in the photo.

  7. My key photos are real images on the page, not CSS backgrounds or text baked into pictures.

0 / 14

0 of 7 answered. Answer them all to see your result.

What to do this week

The order matters: measure first, fix the hero, measure again. Write your before number down now, so you have something to compare with after the fix.

Checklist

Your image fixes

0 of 8 done

Saved on this device only

Questions people ask

Do I need an image optimisation plugin or service?

Not always. Many platforms already resize and convert images. A plugin helps when you upload a lot of photos and your platform does not do this. Check first: test a page, and see what file type and size visitors actually receive.

Will smaller images make my photos look worse?

Not if you resize to the shown size and use a sensible quality setting. Compare at the size the photo appears on screen. If you can see the difference there, raise the quality a little.

Should I compress the photos already on my site?

Start with the pages that matter most: homepage, main service or category pages and best-selling products. Replacing a few heavy images there usually does more than reprocessing an entire archive.

Does the image title attribute matter for SEO?

Not in any way Google documents as important. Spend the time on alt text, captions and the words on the page instead.

Where you go next depends on what the self-score above showed you.

  • Images fixed but the speed test still fails: the guide on Core Web Vitals sorts the remaining causes (sliders, widgets, banners) into the three measures, with the request to send your developer for each.
  • You run a shop: the guide on product pages picks up where this one stops, with descriptions only you could write, reviews and Merchant Center.
  • A redesign or new platform is coming: the next guide in this series, on moving a site without losing your Google traffic, shows how to keep what already works, including the photos, file names and alt text you just fixed.

You reached the end

Your summary

This guide has 9 quick questions

Try them to see how much you already know. Your first answer is the one that counts.

Start with the first question
Your checklist0 of 8 done
Revisit the section “What to do this week”

New guides by email when they are published.

Unsubscribe in one click.

What to do next

  1. Run your homepage through the free speed test below and note which element sets your Largest Contentful Paint.
  2. Resize and re-export your hero photo at about twice its shown width, upload it, and test again.
  3. Write specific alt text for the ten photos that matter most to your sales.

How fast is your site, really?

Test your pages on a simulated phone and see the Core Web Vitals Google measures.

Run the speed test

Technical SEO

Moving or redesigning a site without losing your Google traffic

The most expensive line in a redesign is often not in the quote: it is the old URLs nobody redirected.

28 min readStart reading

See it applied in an illustrative case study

Invented businesses and modelled figures, not client results: how the work in this guide fits into a whole engagement.

See all 83 studies