Cut Image Sizes 50% and Fix LCP: Image SEO for Arizona SMBs
Image SEO means making your images load fast, read clearly to screen readers and search engines, and stay easy for Google to find and index. The single highest-impact move is fixing your Largest Contentful Paint (LCP) image: compress it, size it correctly, preload it, and write real alt text. Get that one element right and most of the rest of this guide is cleanup, not triage.
TL;DR:
- Compress images before upload to reduce file sizes by four to eight times, significantly improving load times and LCP performance.
- Use responsive image techniques with srcset and sizes attributes, creating multiple formats like AVIF and WebP for faster, modern browser support.
- Write concise, descriptive alt text that explains the function and content of images without keyword stuffing or unnecessary phrases.
- Submit an image sitemap, add structured data, and maintain consistent image URLs to improve discoverability and indexing by Google.
- Run Lighthouse audits and monitor Core Web Vitals data after changes to verify performance improvements and ensure proper implementation.
Table of Contents
- Image SEO Checklist: Quick Wins vs. Developer Tasks
- How Do You Implement Responsive Images and Modern Formats?
- What Makes Alt Text Actually Work?
- How Do Image Sitemaps and Metadata Affect Indexing?
- How Do You Confirm the Fixes Actually Worked?
- What Arizona Businesses Should Know Before Hiring Help
- Get Your Images (and Your Site) Actually Fast
- Sources
- FAQ
Image SEO Checklist: Quick Wins vs. Developer Tasks
Not every fix requires a developer. Some take ten minutes in your CMS; others need someone comfortable editing templates and build pipelines. Splitting the list this way keeps you from stalling on a task that needs code when three other fixes don’t.
Quick wins you can do today:
- Compress every image before upload using tools like Hypergamy AI’s Photo Enhancer; a photo straight off a phone is often 4 to 8 times larger than it needs to be for web display.
- Rename files with descriptive, hyphenated names to improve clarity and search relevance.
- Write alt text that describes what the image actually shows and why it’s there.
- Add explicit width and height attributes to every img tag.
- Lazy-load images below the fold only. Avoid lazy-loading images visible on first load to prevent delays.
Developer-level tasks:
- Build responsive images with srcset and sizes so phones don’t download desktop-sized files.
- Convert your image library to AVIF or WebP with JPEG or PNG fallback for older browsers.
- Preload the likely LCP image and mark it with fetchpriority=“high” to ensure faster loading.
Site-wide tasks:
- Keep image URLs consistent, avoid renaming or moving files after indexing.
- Add an image sitemap for large catalogs or CDN-hosted images.
- Add ImageObject structured data and an og:image tag so Google and social platforms pick the thumbnail you want, not one they guess at.
Pro Tip: Sort this list by effort versus payoff, not by what feels most technical. Compressing images and fixing alt text usually takes an afternoon and moves the needle faster than a full responsive-image rebuild.
How Do You Implement Responsive Images and Modern Formats?
Responsive images solve a real waste problem: a phone downloading a 2,400-pixel-wide desktop image can burn through 2 to 4 times the data it actually needs for its screen. The srcset and sizes attributes fix that by letting the browser pick the right file for its own viewport, and Web so the browser has real options instead of guessing between two extremes.
A practical build order looks like this:
- Generate 3 to 5 width variants of every hero and product image during your build process or through an image CDN.
- Convert those variants to AVIF and WebP, keeping a JPEG or PNG fallback inside a
<picture>element for older browsers. - Identify the image most likely to be your LCP element (usually the hero image or the first product photo) and add a
<link rel="preload">tag for it, plusfetchpriority="high"on the img tag itself. - Never apply
loading="lazy"to that same LCP image. Lazy-loading tells the browser to wait, which is the opposite of what an LCP element needs. - If you’re serving images from a third-party CDN domain, add a
preconnecthint, or better, proxy the CDN through your own origin to skip the extra DNS and TLS handshake.
AVIF and WebP conversion can cut file sizes by more than 50% compared to JPEG, according to web.dev’s image performance research, which translates directly into shorter resource load duration for your LCP element.
That last point matters more than most guides admit. Web.dev’s own research on LCP misconceptions makes clear that compressing images alone doesn’t guarantee a faster LCP. LCP breaks into four subparts: time to first byte, resource load delay, resource load duration, and render delay. Shrink the image but leave a slow render delay unaddressed, and you’ve just moved the bottleneck instead of fixing it. Measure all four before declaring victory.
What Makes Alt Text Actually Work?
Alt text does two jobs at once: it tells a screen reader user what’s in the image, and it gives Google semantic context it can’t get any other way. Both jobs fail when alt text is either empty or stuffed with keywords.
Good alt text follows a few consistent rules:
- Keep it under roughly 150 characters. University of Iowa’s accessibility guidance notes that longer alt text causes screen reader fatigue, since some readers announce the full string before moving on.
- Skip “image of” or “picture of.” A screen reader already announces that it’s reading an image; repeating it wastes the visitor’s time.
- Describe function and content, not just appearance. “Golden retriever puppy chewing a shoe” beats “cute dog.”
- For decorative images that add nothing informational (a background texture, a spacer graphic), use
alt=""so screen readers skip them entirely rather than announcing a filename. - For complex visuals like charts or diagrams, write a short alt description, then add a fuller explanation in the surrounding page text or an
aria-describedbyreference. Google’s own technical writing guidance on alt text treats this pairing as the standard pattern for anything too detailed for a single sentence.
Accessible pages tend to rank better for a straightforward reason: the same clear structure that helps a screen reader also helps Google understand what an image means and why it’s on the page.
How Do Image Sitemaps and Metadata Affect Indexing?
Google only reads images from the src attribute of an <img> tag. A background image set purely through CSS never gets indexed as a standalone image asset, no matter how prominent it looks on the page.
A few structural habits keep your images discoverable:
- Submit an image sitemap when you run a large catalog site or host images on a CDN subdomain Google might not crawl on its own; Google’s image SEO documentation treats this as the fix for images it would otherwise miss.
- Add ImageObject structured data and an
og:imagemeta tag to nominate the exact image you want used as a thumbnail in Google Discover or social shares, rather than leaving that choice to an algorithm. - Keep image URLs stable. Renaming or moving a file after Google has indexed it can knock it out of image search results until it gets recrawled.
- Use descriptive, hyphenated filenames as a habit, not an afterthought. It’s a small signal, but it’s a free one.
If you’d rather Google show only a thumbnail without linking through to the full-size file, you can adjust how inline linking works on your image pages, though most small business sites are better served by keeping that link active.
How Do You Confirm the Fixes Actually Worked?
Run Lighthouse first. It flags specific image issues like oversized files, missing preload hints, and improperly sized images with direct fix suggestions attached to each finding.
From there:
- Check Core Web Vitals field data (the real LCP your visitors experience) in PageSpeed Insights or the Chrome UX Report, since lab scores from Lighthouse don’t always match what actual traffic sees.
- Open Search Console’s image indexing report confirming Google is picking up new images and check Discover eligibility.
- Watch for crawl errors right after moving images to a CDN or renaming files. That’s the most common time an image SEO project quietly loses ranking signals.
- Recheck Cumulative Layout Shift after adding width and height attributes. It should drop close to zero if the fix worked.
Pro Tip: Run this check 48 to 72 hours after deploying changes, not immediately. Field data needs real visitor traffic to populate, and checking too early just shows you stale numbers.
What Arizona Businesses Should Know Before Hiring Help
Brett has spent years watching Arizona businesses treat image SEO as an afterthought, right up until a slow-loading hero image quietly tanks a page that should be ranking. An experienced SEO agency has run integrated SEO work since 1997, and the pattern shows up across very different industries. A music-related client saw a 4,490% traffic increase after cleanup work that included site performance and image handling; a roofing client saw rankings jump 1,072%; a pool care company saw its search presence and sales grow 1,060%. None of those numbers came from image fixes alone, but none of them happened without them either.
DIY works fine for a single slow page or a small site with a handful of images. Site-wide responsive image rollouts, structured data, and CDN proxying are where most small teams run out of time or expertise, and where an agency engagement earns its cost back fastest.
— Brett
Get Your Images (and Your Site) Actually Fast
This agency offers an alternative to guessing your way through Core Web Vitals reports alone. Instead of hiring a freelancer for image fixes and a separate contractor for site speed, some agencies handle image optimization, structured data, CDN setup, and the rest of your technical SEO under one roof, supported by an integrated approach like that behind the 4,490% traffic increase case study above.
A typical audit starts by identifying your actual LCP bottlenecks (not just compressing every image and hoping), then prioritizes fixes by impact: responsive image rollout, format conversion, preload strategy, and structured data for thumbnail control. For Scottsdale and greater Arizona businesses, that work often complements broader local SEO services so image fixes support the same rankings your Google Business Profile depends on. If your site was built years ago and the image problem is really a bigger platform problem, a website redesign may be the more honest fix.
Request a site performance review through Webtechs and get a prioritized list of what to fix first, not a generic checklist.
Sources
FAQ
What Is SEO for Images?
Image SEO is the practice of making images fast to load, accessible to screen readers, and easy for search engines to index and understand. It covers technical work like compression and responsive sizing alongside content work like alt text and descriptive filenames.
Is SEO Dead Now With AI?
No. AI-generated answers and search summaries still pull from indexed, well-structured content and images, which means the fundamentals covered here (fast load times, clear alt text, structured data) matter as much as ever. If anything, clean image metadata gives AI systems better signals to work with, not fewer reasons to care about it.
What Is the 80/20 Rule in SEO?
Applied to image SEO, it means a small set of fixes (LCP image optimization, alt text, and compression) delivers most of the ranking and performance benefit, while advanced work like full responsive rollouts and structured data delivers smaller, incremental gains. Start with the 20% that moves the needle before chasing the rest.
What Is the Best SEO Agency in Phoenix, Arizona?
There’s no single objectively “best” agency, but Webtechs has operated out of Scottsdale since 1997 and backs its work with published case studies showing traffic and ranking increases across industries like music, roofing, and pool care. Local businesses evaluating agencies should ask for measurable results tied to their specific industry, not just general promises.
How Long Does It Take to See Image SEO Results?
Most sites see measurable Core Web Vitals improvement within days of deploying compression, preload, and responsive image fixes, since these directly affect page load metrics. Indexing changes and ranking movement in Google Images typically take longer, often several weeks, as Google recrawls and reevaluates the page.