The site does not answer on the URL you gave

Audit check reachable · worth 15 of 100 points · all checks

What the audit saw

The audit could not load the page at all, or the server returned a 4xx or 5xx status.

Why it costs you

Nothing else can be measured until this works, which is why it carries the largest weight. It also means every real visitor sees the same failure, and search engines drop pages that keep returning errors.

How to find it on your site

  1. Does it answer at all, and with what status? 
    curl -sS -o /dev/null -w '%{http_code} %{url_effective}\n' -L https://your-site.com/
  2. Follow the redirect chain to find where it breaks 
    curl -sSI -L https://your-site.com/ | grep -iE '^(HTTP/|location:)'
  3. DNS and TLS in one shot 
    dig +short your-site.com; curl -sSI https://your-site.com/ | head -1

How to know it is fixed

The first command should print 200 or a 3xx that resolves to 200. Anything else is the bug.

The part people get wrong

A bare domain that answers on http but not https looks like a DNS problem and is usually a missing certificate or a proxy bound only to port 80.

Check it against your own site

Open an issue with your URL and a bot runs this check plus 14 others, posts the failures with the measured values, and publishes a report page: free audit. If you want the fixes applied and re-verified instead: fixed-price tiers.

Other checks

The page is served over plain HTTP · The TLS certificate is expired or about to exp · No mobile viewport tag · The page title is missing or the wrong length · The meta description is missing or the wrong l · The page has no H1, or more than one · Images have no alt text · Responses are not compressed

All published audits · Check reference