Open Developer Tools → Network, filter to images, and reload. Each failing image shows a status. 404: the file isn't at that address (moved, renamed, not uploaded, or a case mismatch like Photo.JPG vs photo.jpg). 403: the server refuses it (permissions, or hotlink protection). Blocked: an http:// image on an HTTPS page. If images load slowly rather than failing, they're too big.
What's the problem
Images show as broken icons, blank spaces or alt text, everywhere or only on some pages, often after a migration, a domain change, or moving to HTTPS.
Why it happens
- Wrong paths after a migration or domain change, often still pointing at the old domain.
- Files missing from the server or the deploy.
- Case sensitivity: works on your computer, fails on a Linux server.
- Mixed content:
http://image links on an HTTPS site. - Permissions or hotlink protection returning 403.
- A CDN or image service that's down or misconfigured.
- Lazy-loading scripts failing, so images never get their real address.
How to fix it
- Check failing images in the Network tab and note the status and URL.
- For 404s, fix the path, re-upload the files, or search and replace old domain links in the database (back up first).
- For mixed content, change image links to
https://. - For 403s, check file permissions and hotlink protection rules.
- Check the console for errors from lazy-loading scripts.
- Compress and resize images that load but are slow.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows page weight, oversized images and caching; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them; insecure http:// files on any of up to 50 pages. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when. It doesn't fill in forms, log in or make payments, so test the feature yourself as well.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
- MDN Web Docs: <img>: The Image Embed elementreference
If an error occurs while loading or rendering an image, and an onerror event handler has been set for the error event, that event handler will get called.
- MDN Web Docs: Mixed contentreference
"Mixed content" refers to securely loaded web pages that use resources to be fetched via HTTP or another insecure protocol.