Website Analysis

Broken Resource Analyzer

Scan a webpage to detect broken CSS, JS, image, and other linked resources.

All tools

Broken Resource Analyzer - Find Broken CSS, JS, and Image Files

The Broken Resource Analyzer scans a webpage to detect broken CSS, JavaScript, image, and other linked resources that fail to load correctly. Broken resources can slow down pages, damage user experience, and negatively impact SEO. This tool helps identify those issues quickly so they can be fixed.

What Is a Broken Resource?

A broken resource is any external file referenced by a webpage that fails to load correctly. This includes images that return 404 errors, CSS files that cannot be fetched, JavaScript files blocked by servers, or CDN assets that no longer exist. Even if the page itself loads, broken resources can silently degrade performance and layout.

Why Broken Resources Are a Problem

Broken resources affect both users and search engines. Missing images create visual gaps, broken CSS can distort layouts, and failed JavaScript files can break functionality. From an SEO perspective, broken resources increase page load time, harm Core Web Vitals, and reduce overall page quality.

How the Broken Resource Analyzer Works

This tool fetches the HTML of a page and scans for linked resources such as images, stylesheets, and scripts. Each resource URL is resolved to an absolute path and checked using HTTP requests. Resources returning 4xx or 5xx responses are flagged as broken.

Types of Resources Checked

Images (<img src>)
Stylesheets (<link rel="stylesheet">)
JavaScript files (<script src>)
Relative and absolute resource URLs

SEO Impact of Broken Resources

While a single broken image may not destroy rankings, widespread broken resources send negative quality signals. Search engines evaluate page completeness, rendering quality, and performance. Pages with many broken assets often load slower and provide poorer user experience.

Common Causes of Broken Resources

File deletions during site updates
Incorrect paths after migrations
CDN misconfiguration
Expired or blocked external assets
Case-sensitive file name mismatches

How to Fix Broken Resources

Fixes typically involve correcting file paths, re-uploading missing files, updating CDN URLs, or removing unused assets. After deploying fixes, always re-test pages to confirm that all resources return successful responses.

Who Should Use This Tool

The Broken Resource Analyzer is useful for SEO professionals, developers, website owners, and performance auditors. It is especially helpful after migrations, redesigns, CMS updates, or CDN changes.

Best Practices to Avoid Broken Resources

Use versioned asset paths
Validate deployments before going live
Monitor logs for 404 asset requests
Avoid hotlinking critical assets from third-party domains
Regularly audit important pages

Final Thoughts

Broken resources are easy to overlook but can cause long-term performance and SEO issues. Regular audits using tools like the Broken Resource Analyzer help maintain a clean, fast, and reliable website.

FAQ

Does this tool check external resources?

Yes, it checks both internal and external resource URLs.

Does it check fonts and videos?

It checks resources referenced via standard HTML tags like img, script, and link.

Is this tool safe to use?

Yes. It only performs read-only HTTP requests.

Can broken resources affect SEO?

Indirectly yes, by harming performance and user experience.

Does it use third-party APIs?

No. All checks are performed directly from your server.

Should I scan all pages?

Focus on important landing pages and templates.

Does it check HTTP status codes?

Yes, it flags 4xx and 5xx responses.

Can CDNs cause false positives?

Occasionally, if a CDN blocks HEAD requests.

How often should I run this?

After updates, migrations, or major content changes.

Will fixing broken resources improve performance?

Yes, especially for render-blocking assets.

Related tools

Pro tip: pair this tool with Screen Resolution Simulator and Mobile Friendly Test for a faster SEO workflow.