Website tools
Free website health checker
A quick look at the foundations of your website. Get practical findings you can understand and act on.
Find another tool
This tool needs JavaScript. If the controls don’t appear, check your connection, enable JavaScript and reload this page.
How to use this tool
1. Enter a public HTTPS page address without query strings or a fragment. You can check your homepage or a particular service or product page.
2. Run the check, then open any finding for evidence and next steps. Items worth reviewing appear first. We also check up to eight eligible internal links.
3. Save a print/PDF report to share with your developer. Use the separate PageSpeed Insights link for a rendered-page performance test.
What gets checked?
We inspect one public HTTPS page: response time and HTML size, a sample of internal links, actual titles and descriptions, H1 text and a sample heading outline, mobile settings, language, image alternatives, canonicals, indexing rules, sharing metadata and HTTP resource references. Open each finding for its evidence. Long values and large lists are shortened. We do not execute JavaScript or download images, stylesheets or scripts.
What do the findings mean?
Observed records a measurement or technical signal without guaranteeing quality. Worth reviewing highlights missing pages, inconclusive requests or settings that deserve attention. Not applicable means there was nothing eligible to check or a measurement was not available. Multiple H1s, empty image alternatives and a canonical pointing elsewhere can be intentional. No review flags does not prove a healthy website.
Questions and assumptions
How are broken links checked?
We test the first eight unique eligible links in source order on the same HTTPS origin, with up to three checks at once. We skip query strings, fragment-only links, external links and common account or action paths. Fragments on other links are removed; their anchor targets are not tested. Redirects stay on the same origin and are limited to three. HTTP 404 or 410 is reported as missing, with a GET confirmation if HEAD returns either code. Other failures, blocked requests and timeouts are unverified, not automatically broken. A 200 response can still be a soft 404 or an incorrect destination; open it yourself to confirm. This is a sample, not a recursive site crawl.
Is the speed check a full page-load test?
No. It measures time from our server starting the request until final response headers arrive, plus the time to receive the HTML. This includes DNS, connection setup and redirects. It also reports uncompressed HTML size and source resource counts. Response time over 2 seconds or HTML over 200 kB prompts a review using our rough thresholds, not a Google grade. Images, CSS, scripts, rendering and real-user conditions are not timed. Use Google's separate mobile speed test for Lighthouse and any available field data.
Why might a check fail?
Private addresses, custom ports, non-HTTPS destinations and large or slow responses are blocked. Some websites block automated requests. Individual link failures remain in the report without discarding the other findings. This check cannot see content created only by JavaScript.
Go further
For loading speed and a rendered-page audit, open PageSpeed Insights below. That separate Google service receives the address when you follow the link. Accessibility also needs keyboard, screen reader and human review.
Sources and further reading
- Google Search Essentials ↗
- W3C accessibility easy checks ↗
- Google PageSpeed Insights ↗
- Google guide to HTTP status codes ↗
- Open Graph sharing metadata ↗
Built and maintained by Custom Logic. Page updated .