website health checker
Free Website Health Checker
Get a full website health report in under a minute. Scans discovered internal pages for HTTP errors, blank content, broken assets, and browser crashes — then gives you a health score and a sorted list of what to fix.
Free first-pass scan
Check your website for broken pages
Paste a public URL into IsItCrashing and scan discovered pages for failed responses, blank pages, broken assets, and website health issues.
Quick answer
IsItCrashing is a free website health checker. It discovers internal pages from your sitemap and links, checks each one for HTTP errors, blank responses, broken critical assets, and JavaScript crashes, then returns a health score and a sorted list of failing pages with diagnostic details.
What website health means
Website health is a measure of how reliably your public pages load and serve working content to visitors and search engines. An unhealthy website has pages returning errors, loading blank, serving broken JavaScript or CSS, or failing silently — problems that erode user trust, conversion rates, and search rankings.
A quick health check after every deployment, content update, or infrastructure change catches these problems before users report them. IsItCrashing automates that check across all your discovered public pages.
What the health check covers
- HTTP status codes: 200 OK, 404 Not Found, 500 Server Error, and other response codes.
- Blank page detection: pages that return 200 but contain no visible rendered content.
- Critical asset health: JavaScript bundles, stylesheets, preload files, and important images.
- Redirect behavior: chains, loops, and final destination status.
- Network reliability: timeouts and connection failures.
- JavaScript crash signals: important frontend errors on browser-checked pages when browser scanning is configured.
How to run a website health check
Enter your website URL in the scanner. The tool normalizes the URL, discovers internal pages from your sitemap and links, then checks each page concurrently. A progress log shows results in real time as each page is tested.
When the scan finishes, you get a health score showing the percentage of pages that passed, a metric grid with total pages, working pages, failed pages, and scan duration, then a detailed table of failed pages sorted by severity.
When to run a health check
The best practice is to run a health check after every significant change: code deployments, CMS content updates, redirect changes, plugin or dependency updates, DNS migrations, and CDN configuration changes. Catching issues at this point takes minutes; catching them after users complain takes hours.
Health checks are also valuable before campaign launches (to confirm landing pages work), before client handoffs (to document site health), and after platform migrations (to verify nothing broke in the move).
Reading your health score
Your health score is the percentage of discovered pages that returned a successful response and loaded their critical assets. A score above 95% is healthy for most sites. Between 80–95% suggests issues worth investigating. Below 80% indicates significant problems that likely impact users and search rankings.
The score alone does not tell you which pages matter most. A single broken checkout page is more critical than ten broken archive pages. Use the Failed Pages table to prioritize by page importance, not just by count.
Health checker vs monitoring service
A monitoring service runs continuously and alerts you when something breaks in production. IsItCrashing is an on-demand health checker you run before problems reach production — during development, staging review, pre-launch, and post-deployment. Use both: run IsItCrashing proactively, and monitoring reactively.
FAQ
What is IsItCrashing?
IsItCrashing is a free website crash checker that lets you enter a public URL and scan discovered pages for broken pages, failed requests, blank pages, broken critical assets, and website health issues.
What does the scanner check?
The scanner checks discovered public pages for HTTP 404 and 500 errors, timeouts, redirect loops, blank content where visible HTML does not load, broken critical scripts or stylesheets, failed important requests, and JavaScript crash signals when browser scanning is configured.
Does it detect JavaScript errors?
It can detect important JavaScript crashes on browser-checked pages when browser scanning is configured. It is not a replacement for runtime error monitoring, logs, or a full frontend observability setup. For ongoing JavaScript error tracking, use a dedicated error monitoring service.
Should I still use monitoring?
Yes. Use IsItCrashing for fast proactive scans before and after changes, then use a monitoring service for ongoing production visibility and alerting. The two tools complement each other — IsItCrashing catches issues at deployment time, monitoring catches issues that emerge later in production.
Who should use IsItCrashing?
It is useful for developers, QA testers, SEO teams, agencies, marketers, website owners, and product teams that need a quick check after deployments, migrations, CMS edits, or campaign launches. Any team that ships changes to a public website benefits from a fast automated first-pass before users or search engines encounter problems.
How many pages does it scan?
The scanner discovers up to 60 internal pages per scan from your sitemap and internal links. It checks the most important pages first based on sitemap priority and crawl depth. Very large sites with hundreds of pages may need a dedicated crawl tool for full coverage.
More answers in the full website crash checker FAQ.
Free first-pass scan
Check your website for broken pages
Paste a public URL into IsItCrashing and scan discovered pages for failed responses, blank pages, broken assets, and website health issues.