Image Performance & Core Web Vitals: The Complete Guide for Local Business SEO
Images are the single largest contributor to poor Core Web Vitals scores in most local business websites. The hero image on your homepage is almost certainly your Largest Contentful Paint (LCP) element — the metric Google uses to measure how fast your page loads for real users. A slow LCP score is a direct ranking signal. But the standard fix — compressing images — destroys the EXIF metadata that makes your images valuable for local search. This guide explains how to optimise images for both performance and SEO without sacrificing either.
How Core Web Vitals affect local search rankings
Core Web Vitals are a set of performance metrics that Google uses as a direct ranking signal. They measure three aspects of user experience: loading speed (LCP), visual stability (CLS), and interactivity (INP). Google introduced Core Web Vitals as a ranking factor in 2021, and they have been part of the Page Experience signal ever since.
For local businesses, the most impactful metric is LCP. The Largest Contentful Paint measures the time from page load to when the largest visible element is fully rendered. In virtually every local business website, that element is the hero image. A slow, unoptimised hero image is therefore a direct drag on your search ranking — not just your user experience.
The critical tension is this: the same EXIF metadata that makes your images valuable for local SEO is stripped by standard image compression tools. Most businesses are forced to choose between performance and metadata. LinkDaddy Media's pipeline eliminates this choice by compressing images and re-injecting metadata in a single automated step.
Core Web Vitals metrics: image impact and fixes
| Metric | Good | Poor | Image impact | Fix |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | < 2.5s | > 4.0s | Critical — hero image is almost always the LCP element | Compress hero image, use WebP, add fetchpriority='high', serve from CDN |
| Cumulative Layout Shift (CLS) | < 0.1 | > 0.25 | High — images without width/height attributes cause layout shifts | Always declare width and height on every <img> element |
| Interaction to Next Paint (INP) | < 200ms | > 500ms | Low — images rarely cause INP issues directly | Ensure image load does not block main thread via large synchronous decoding |
| First Contentful Paint (FCP) | < 1.8s | > 3.0s | Medium — large above-fold images delay FCP | Preload hero image, use eager loading, reduce file size |
| Time to First Byte (TTFB) | < 800ms | > 1.8s | Medium — slow origin server delays all image requests | Serve images from CDN edge nodes (Cloudflare R2 recommended) |
LCP optimisation: the hero image is your most important ranking asset
The hero image — the large image at the top of your homepage or service pages — is almost always the LCP element. Google measures how long it takes from the moment the user navigates to your page to when this image is fully visible. A score under 2.5 seconds is "good". Over 4 seconds is "poor" and will suppress your ranking.
Three factors determine your hero image LCP score: file size, format, and delivery. A 2MB JPEG served from a shared hosting server in a different country will produce a poor LCP score regardless of any other optimisation. The same image at 120KB in WebP format, served from a Cloudflare CDN edge node, will produce a good LCP score.
The critical rule: never lazy-load your hero image. Add loading="eager" and fetchpriority="high" to the hero image element. Lazy-loading the LCP image is one of the most common and damaging Core Web Vitals mistakes — it instructs the browser to delay loading the very element Google is measuring.
Image format comparison: performance vs. metadata support
The choice of image format affects both file size (performance) and metadata support (SEO). The table below compares the five main formats used for web images.
| Format | Compression | Metadata | Browser support | Recommended? |
|---|---|---|---|---|
| WebP | 25–35% smaller than JPEG | Full EXIF + XMP | All modern browsers | Yes |
| AVIF | 40–50% smaller than JPEG | Limited EXIF support | Chrome, Firefox, Safari 16+ | No |
| JPEG | Baseline | Full EXIF + XMP | Universal | No |
| PNG | Larger than JPEG for photos | Limited EXIF | Universal | No |
| HEIC | 40% smaller than JPEG | Full EXIF | Safari only (no Chrome/Firefox) | No |
WebP is the recommended format for all business images. It delivers the best balance of compression, metadata support, and browser compatibility. Use JPEG as a fallback for older browsers or when metadata preservation is critical and WebP encoding is not available.
The metadata-compression conflict: why most pipelines destroy your SEO
Standard image compression tools — Squoosh, TinyPNG, most WordPress plugins, most CMS image processors — strip EXIF and XMP metadata by default. This is intentional: metadata adds file size, and the goal of compression is to reduce file size. The result is that every time you compress an image through a standard pipeline, you destroy the entity signals that make that image valuable for local search.
The EXIF Artist field (your business name), the GPS fields (your service area), the ImageDescription (your primary service keyword), and the Copyright field (your copyright claim) are all removed. The ImageObject schema on your page still declares these facts, but the image file itself is now anonymous — it carries no metadata that Google's image indexing pipeline can read directly.
The solution is a two-step pipeline: compress first, then re-inject metadata. This is exactly what LinkDaddy Media does. Every image is compressed to the optimal format and quality, then all EXIF and XMP metadata is re-injected before the image is delivered. You get the performance benefit of compression and the SEO benefit of full metadata — without having to choose between them.
How to optimise images for Core Web Vitals without losing SEO metadata
1.Identify your LCP element
Use Google PageSpeed Insights or Chrome DevTools to identify your Largest Contentful Paint element. In most local business websites, the LCP element is the hero image. This is the image that must be optimised first.
2.Convert images to WebP format
WebP delivers 25–35% smaller file sizes than JPEG at equivalent quality and supports full EXIF and XMP metadata. Convert all images to WebP as your default format. Serve JPEG as a fallback for older browsers using the <picture> element.
3.Compress to the correct quality level
For hero images (LCP candidates): target under 150KB. For gallery images: under 80KB. For thumbnails: under 30KB. A quality setting of 75–85 is the sweet spot for WebP and JPEG. Do not compress below 70 — the visual degradation is visible and does not significantly reduce file size.
4.Set explicit width and height on every image
Always declare width and height attributes on every <img> element. This allows the browser to reserve the correct space before the image loads, preventing Cumulative Layout Shift (CLS). Missing width/height is the most common cause of CLS failures.
5.Use eager loading for hero images, lazy for the rest
Add loading='eager' and fetchpriority='high' to your hero image. Add loading='lazy' to all images below the fold. Never lazy-load the LCP image — it will delay the LCP score and directly hurt your ranking.
6.Re-inject EXIF metadata after compression
After compressing, re-inject your EXIF Artist, GPS, ImageDescription, and Copyright fields. Also re-inject XMP dc:creator, dc:description, and dc:subject. This step is what most pipelines skip — and it is the step that preserves your local SEO signal.
7.Serve images from a CDN
A CDN serves images from the edge node closest to the user, reducing TTFB for image requests by 50–80%. Cloudflare R2 with CDN delivery is the recommended setup. All images uploaded to LinkDaddy Media are automatically served from Cloudflare's global network.
Frequently asked questions about image performance and Core Web Vitals
- Do images affect Core Web Vitals scores?
- Yes — images are the single largest contributor to poor Core Web Vitals scores in most websites. The Largest Contentful Paint (LCP) metric is almost always an image on local business websites. A slow LCP score directly affects Google's ranking algorithm. Images also affect Cumulative Layout Shift (CLS) when width and height attributes are missing.
- What is LCP and why does it matter for image SEO?
- Largest Contentful Paint (LCP) measures the time from page load to when the largest visible element is fully rendered. Google considers an LCP under 2.5 seconds 'good', 2.5–4 seconds 'needs improvement', and over 4 seconds 'poor'. A poor LCP score is a direct ranking signal. Since the LCP element is almost always an image on local business websites, image optimisation is the single most impactful action you can take to improve your Core Web Vitals score.
- Does compressing images remove EXIF metadata?
- Standard image compression tools strip EXIF and XMP metadata by default. This destroys the entity signals that make your images valuable for local search. The solution is a two-step pipeline: compress first, then re-inject metadata. LinkDaddy Media handles both steps automatically.
- What image format is best for SEO and performance?
- WebP is the recommended format for most use cases. It delivers 25–35% smaller file sizes than JPEG at equivalent visual quality, is supported by all modern browsers, and supports full EXIF metadata. Use WebP as your default, with JPEG as a fallback for older browsers.
- Should I use lazy loading on all images?
- No. Lazy loading should be applied to images below the fold only. The hero image (your LCP element) must never be lazy-loaded. Use loading='eager' and fetchpriority='high' on the hero image. Lazy-loading the LCP image is one of the most common and damaging Core Web Vitals mistakes.
- Can I optimise images for performance without losing SEO metadata?
- Yes — but only with the right pipeline. Standard compression tools strip EXIF and XMP metadata. You need either a compression tool that explicitly preserves metadata or a two-step process: compress first, then re-inject metadata. LinkDaddy Media's image hardening pipeline handles both steps: it compresses images to the correct format and quality, then re-injects all EXIF and XMP metadata before delivery.