Image SEO: How to Optimize Images for Search Rankings and Page Speed

Images account for an average of 45% of total page weight on small business websites, and image-related searches make up 22% of all Google queries. Despite this, image optimization is the most consistently neglected element in most SEO strategies. Business owners upload full-resolution photos directly from their camera, skip alt text, use generic file names like IMG_4837.jpg, and wonder why their pages load slowly and their images never appear in search results. The opportunity cost is significant: properly optimized images improve page speed (which directly affects rankings and conversion), generate traffic through Google Image Search, and provide contextual relevance signals that strengthen the surrounding content's rankings.

This guide covers every dimension of image SEO: file format selection, compression, sizing, alt text strategy, file naming, lazy loading, and structured data. Revenue Group optimizes images as part of every website build and every technical SEO engagement because the impact spans both performance and rankings.

Image Format Selection: WebP Is the Default

The format you choose determines the file size, quality, and browser compatibility of every image on your site. In 2026, WebP is the default format for most web images. WebP provides 25% to 35% smaller file sizes than JPEG at equivalent visual quality, supports transparency (replacing PNG for most use cases), and is supported by all modern browsers including Chrome, Firefox, Safari, and Edge. The file size reduction directly improves page speed, which affects both Core Web Vitals scores and user experience.

The exceptions: use SVG for logos, icons, and simple graphics that need to scale to any size without quality loss. SVG files are vector-based (not pixel-based), so they are sharp at every screen resolution and typically smaller than equivalent raster images. Use AVIF when maximum compression is the priority and browser support is not a concern — AVIF provides 20% smaller files than WebP but has slightly less browser support. Revenue Group converts all client images to WebP during the build process, with JPEG fallbacks served to the less than 2% of visitors using browsers that do not support WebP. For the full picture of how image weight affects load times, see our guide on why websites load slowly.

Image Compression: The Quality Threshold

Most images can be compressed by 60% to 80% without visible quality loss. The key is understanding the quality threshold — the compression level below which the human eye cannot detect degradation. For JPEG and WebP, a quality setting of 75 to 85 (out of 100) produces visually identical results to the original for most photographs. Below 70, artifacts begin to appear in areas with gradual color transitions. Revenue Group compresses all client images to quality 80, which produces the optimal balance between file size and visual fidelity across our testing.

The tools: Squoosh (free, browser-based, supports all formats), ShortPixel (WordPress plugin that compresses on upload), ImageOptim (Mac desktop app for batch processing), and TinyPNG (API-based compression for build pipelines). For sites with hundreds of images, Revenue Group integrates compression into the build pipeline using Sharp (a Node.js library) so every image is automatically compressed to the target quality and format during deployment. A 20-page service website with 60 images typically sees total image weight reduced from 15MB to 3MB after compression — an 80% reduction that improves LCP by 1.5 to 2.5 seconds on mobile connections.

Image Sizing: Never Upload Camera Resolution

A modern smartphone camera produces images at 4032 x 3024 pixels (12 megapixels). A typical website displays images at 800 to 1200 pixels wide. Uploading the full-resolution image means the browser downloads a 4MB file and then scales it down to display at one-quarter of its actual size — wasting 75% of the downloaded data. This is the single most common image performance mistake Revenue Group encounters during audits, appearing on virtually every site that has not been professionally optimized.

The sizing guidelines: hero and banner images at 1200 to 1600 pixels wide (covering the maximum display width on large desktop screens), content images within the body at 800 pixels wide (matching the typical content column width), thumbnail images at 300 to 400 pixels wide, and team headshots at 400 to 600 pixels wide. These dimensions match the CSS display sizes, meaning the browser downloads exactly the pixels it needs with no waste. For responsive delivery, use the srcset attribute to serve different image sizes to different screen widths — a 400-pixel image to mobile phones and a 1200-pixel image to desktop monitors. Revenue Group implements responsive images with srcset on every client site, reducing mobile image payload by 40% to 60% compared to serving desktop-sized images to all devices.

Alt Text Strategy: Description Plus Context

Alt text serves two audiences: screen reader users who need a text description of the image, and Google's crawler that uses alt text to understand image content and page context. Effective alt text is descriptive (it tells the reader what the image shows), contextual (it relates the image to the page content), and natural (it reads like a sentence fragment, not a keyword list). Revenue Group's approach: describe the image's content in 5 to 15 words, naturally incorporating the page's primary keyword when it fits without forcing.

Good examples: "white shaker cabinet kitchen remodel with quartz countertops" (descriptive, includes relevant keywords naturally), "Revenue Group team meeting in Tampa office" (descriptive, provides brand and location context), "before and after comparison of bathroom tile replacement" (descriptive, includes service-relevant terms). Bad examples: "kitchen" (too vague to be useful), "kitchen remodel kitchen remodeling Tampa kitchen renovation company" (keyword stuffing that triggers spam signals), and "" (missing entirely — the most common failure, appearing on 54% of all website images). For the full accessibility requirements around alt text, see our guide on common accessibility mistakes.

File Naming: Descriptive and Consistent

Google uses the image file name as a secondary ranking signal for image search. A file named "kitchen-remodel-white-cabinets.webp" provides Google with relevant context. A file named "IMG_4837.jpg" provides nothing. The file naming convention Revenue Group uses: lowercase letters only, hyphens between words (not underscores — Google treats hyphens as word separators but underscores as joiners), descriptive of the image content, and 3 to 7 words maximum. Rename all image files before uploading them to the site — most CMS platforms retain the original file name in the URL, so "IMG_4837.jpg" will appear in Google Image Search results if that is the file name on the server.

Lazy Loading: Below the Fold Only

Lazy loading defers image download until the image is about to enter the viewport, improving initial page load speed by reducing the amount of data the browser must fetch before rendering the visible content. The implementation is now native to HTML: add loading="lazy" to any img tag, and the browser handles the rest. No JavaScript library needed.

The critical rule: do not lazy load above-the-fold images. The hero image, logo, and any images visible without scrolling should load immediately (loading="eager" or simply omitting the loading attribute). Lazy loading these images delays their appearance and worsens Largest Contentful Paint — the Core Web Vitals metric that measures when the main content becomes visible. Revenue Group audits lazy loading implementation on every site to ensure above-the-fold images load immediately while all below-fold images are deferred. The typical LCP improvement from proper lazy loading configuration is 0.5 to 1.5 seconds on mobile.

Image Sitemaps and Structured Data

An image sitemap extends your XML sitemap to include information about the images on each page — their URL, caption, title, and geographic location. While Google can discover images by crawling your pages directly, an image sitemap ensures complete coverage and can accelerate indexing of new images. Revenue Group includes image sitemap entries for portfolio images, product images, and team photos — any image that has standalone value in image search results.

For product images and portfolio images, adding ImageObject structured data provides Google with additional metadata: the image description, the creator, the date created, and the content associated with the image. This structured data improves the likelihood that images appear in rich results and image packs in Google Search. Revenue Group implements ImageObject schema on portfolio and project gallery pages where image search visibility is a strategic priority for the client. For service businesses, optimized portfolio images are often the first touchpoint — a homeowner searching for "kitchen remodel ideas" sees your project photo in Google Images and clicks through to your site, entering the sales funnel through visual content rather than text-based search results. For broader schema markup implementation, see our guide on schema markup services.

The Image Optimization Checklist

Revenue Group runs every client image through this checklist before deployment: format converted to WebP (with JPEG fallback for compatibility), compressed to quality 80 or equivalent, sized to match CSS display dimensions (not camera resolution), responsive srcset attributes serving appropriate sizes per device, descriptive file name with hyphens between words, descriptive alt text under 125 characters, lazy loading on all below-fold images (above-fold images load eagerly), and width and height attributes set on every img tag to prevent cumulative layout shift. This checklist takes 30 to 60 seconds per image for manual optimization, or runs automatically through our build pipeline for sites with automated image processing. The cumulative effect on page speed, accessibility, and image search visibility makes image optimization one of the highest-ROI technical SEO investments available.

The most common mistakes Revenue Group encounters during image audits: uploading images at camera resolution (4000+ pixels wide) when the page displays them at 800 pixels, using PNG format for photographs instead of WebP or JPEG, omitting alt text entirely on decorative images that actually carry meaning (a portfolio photo is not decorative — it is a selling tool), and setting all images to lazy load including the hero image above the fold. Each of these mistakes is individually minor but they compound across a 30-page site with 10 images per page. A site with 300 unoptimized images typically loads 4 to 6 seconds slower than the same site after a full image optimization pass, and that speed gap directly affects both rankings and conversion rates. For a deeper look at how page speed connects to search rankings, see our guide on diagnosing slow website performance.