WordPress Image Optimization Scanner

1. WebP vs. AVIF Next-Gen Image Formats

Modern WebP and AVIF image formats provide superior compression over legacy JPEGs. As documented in Google Web Vitals Image Compression Guide, next-gen formats cut byte payload sizes by 80%.

2. Alt Text Accessibility & Image SEO

Descriptive alt attributes allow screen readers and search crawlers to understand image content. Audit technical tags in our WordPress SEO Health Checker.

3. Auditing Broken Image Link URLs

Check 404 URL errors in our WordPress Broken Link Checker.

4. Instant Image CDN Delivery via Nimbica Static Edge

Nimbica pre-renders WordPress sites and optimizes image assets delivered from 300+ global edge locations, giving visitors sub-50ms image load times.

5. How the Image Scan Works

Enter a WordPress page URL and the tool fetches the rendered HTML, then extracts every <img> tag on the page — up to the first 30 found. For each tag it reads the src attribute (the image URL) and the alt attribute (the accessibility description), then classifies the format by checking whether the file extension in the URL ends in .webp or .avif. Anything else — .jpg, .jpeg, .png, .gif — is reported as a legacy format.

The report surfaces two headline metrics: Next-Gen Format Adoption (how many of the scanned images are already WebP/AVIF) and Missing Alt Attributes (how many images have no alt attribute at all — an empty alt="" is treated as intentionally decorative and does not count as missing). Below the summary, each individual image tag is listed with its source URL, alt text (or a missing-text warning), and format badge for manual review.

6. Worked Example: Interpreting a Report

Scanning a typical product review post with 22 embedded images might return: 22 Image Assets Audited, 6/22 Next-Gen Formats, and ⚠️ 9 Missing Alt Text.

Interpretation: only 27% of images are served as WebP/AVIF, meaning roughly three-quarters of the visual payload is likely oversized JPEG/PNG — a strong candidate for bulk conversion via a plugin like ShortPixel, Imagify, or WordPress core's native WebP support (added in 5.8+ via image_editor_output_format). The 9 missing-alt images are an accessibility and image-SEO gap: prioritize adding descriptive alt text to any of those that are also above the fold, since they're most likely to be the LCP candidate.

7. Practical Use Cases

• Pre-publish accessibility check: Scan a new post before publishing to catch images uploaded without alt text.
• Bulk conversion audit: Measure WebP/AVIF adoption across your top landing pages before and after installing an image optimization plugin, to confirm it's actually converting existing media.
• Client site handoff review: Quickly spot-check a client's product or blog pages for glaring image SEO gaps as part of a site audit deliverable.
• LCP root-cause investigation: Combine with the Core Web Vitals Checker — if LCP is failing, check whether the hero image on that page is still a legacy JPEG.

8. Limitations & Edge Cases

• Extension-based format detection: Images served in WebP format via server-side content negotiation (same .jpg URL, different bytes based on Accept headers) will not be detected as next-gen, since the check only reads the URL string.
• Lazy-loaded placeholders: If a plugin swaps the real image URL into a data-src attribute and leaves a placeholder in src, the scan reports the placeholder rather than the final delivered image.
• CSS background images are not scanned: Hero sections using background-image in CSS rather than an <img> tag are invisible to this scanner, even though they can be significant LCP contributors.
• 30-image cap: Image-dense gallery or portfolio pages beyond 30 images will only have the first 30 tags in document order reported.