Free Website Health Score Checker

Type your website address into the checker below and get a score out of 100 in about half a minute. It looks at four things that affect both visitors and search engines: security and HTTPS, SEO basics, speed, and mobile readiness. Every check that fails comes with a short instruction on how to fix it. The tool is free, needs no sign-up, and reads only what any browser or search engine can already see.

What the Website Health Score checks

The score adds up 23 individual checks across four groups. Security carries 25 points, SEO basics 35, speed 20 and mobile and content 20. SEO carries the most weight because a technically sound, crawlable page is the foundation for everything else. Here is what each group tests, why it matters and what to do when a check fails.

Security and HTTPS (25 points)

Visitors expect a padlock, and browsers warn people away from sites without one. Google has also said for years that HTTPS is a lightweight ranking signal, so a secure site is a small advantage and an insecure one is a real trust problem. The checker tests five things:

  • Site loads over HTTPS (8 points). Your pages must be served from an address that starts with https://. If this fails, install an SSL certificate. Most hosts provide one free.
  • http:// redirects to https:// (4 points). Anyone who types the old address should land on the secure version automatically, with a permanent redirect, so you do not end up with two copies of every page.
  • HSTS header (4 points). Strict-Transport-Security tells a browser to use HTTPS every time, which blocks a class of downgrade attacks. Add it once HTTPS works everywhere on your site.
  • X-Content-Type-Options (3 points). The value nosniff stops browsers guessing file types, which prevents some content-injection tricks.
  • Clickjacking protection and Referrer-Policy (3 points each). X-Frame-Options or a Content-Security-Policy frame-ancestors rule stops other sites embedding yours in a hidden frame, and a Referrer-Policy such as strict-origin-when-cross-origin limits how much of your address leaks to other sites.

Most of these are one-line changes in your server configuration or a security plugin. They do not change how your site looks, so they are some of the safest improvements you can make.

SEO basics (35 points)

These checks confirm that a search engine can find, read and understand the page you entered. They do not measure how good your content is, only whether the technical foundation is in place.

  • Page title (6 points). A unique title of roughly 30 to 60 characters that names the page topic. Titles that are missing, duplicated or far too long are one of the most common and most fixable problems.
  • Meta description (6 points). A summary of about 70 to 160 characters. Google does not use it as a ranking factor, but it often shows it under your title, so a clear description improves the chance of a click.
  • Exactly one H1 heading (5 points). One main heading that states the topic. No H1, or several competing ones, makes the page structure harder to read for people and for search engines.
  • Canonical link (2 points). A rel=”canonical” tag names the preferred address of a page when the same content is reachable at more than one URL, for example with tracking parameters.
  • Page is open to search engines (5 points). A noindex rule keeps a page out of Google. It is the right tool for thank-you pages and the wrong one for pages you want found, and it is often left on by mistake after a site launch.
  • Social sharing tags (3 points). Open Graph tags such as og:title and og:image control how a link looks when someone shares it on social networks and messaging apps.
  • robots.txt (4 points) and XML sitemap (4 points). robots.txt tells crawlers where they may go, and a sitemap lists the pages you want indexed. Check that robots.txt does not contain Disallow: / unless you really want the whole site hidden.

Speed (20 points)

Fast pages keep visitors and help search engines crawl efficiently. Google measures real-visitor speed through Core Web Vitals: loading (LCP, good under 2.5 seconds), responsiveness (INP, good under 200 milliseconds) and visual stability (CLS, good under 0.1). This tool does not measure those directly. It checks the server-side factors that most often cause slow loading:

  • Server response and page download (8 points). How long the server takes to answer and deliver the page. Slow answers usually point to weak hosting or no page caching.
  • HTML size (4 points). Very heavy pages, often caused by page builders, inline scripts or large embeds, load more slowly on mobile networks.
  • Compression (4 points). gzip or Brotli can shrink text files by well over half. It is normally a single switch in your host settings.
  • Caching headers (4 points). Cache-Control headers let browsers and a CDN reuse files instead of downloading them again.

Because the timing is measured from our server, your own visitors may see different numbers. For real-user data, use PageSpeed Insights and the Core Web Vitals report in Google Search Console alongside this score.

Mobile and content (20 points)

Google indexes the mobile version of your page first, so mobile readiness is not optional. These checks look at the basics:

  • Mobile viewport tag (6 points). Without it, phones show a shrunken desktop page that is hard to read.
  • Page language (3 points). The lang attribute, for example lang=”en-IN”, helps browsers, translation tools and screen readers.
  • Image alt text (5 points). Alt text describes images for people who cannot see them and gives search engines context. It scores by the share of images that have it.
  • Favicon (3 points). The small icon in browser tabs and some search results. It is a minor signal of a finished, trustworthy site.
  • Enough visible text (3 points). Pages with fewer than about 300 words rarely give search engines enough to work with. This is a guide, not a rule, and some pages such as contact pages are short on purpose.

How to read your score

A score of 75 or above means the technical basics are mostly in place. Between 50 and 74, you have several fixable gaps worth working through. Below 50, something fundamental is probably wrong, such as no HTTPS, a noindex rule or a missing viewport tag. Treat the number as a to-do list rather than a grade. Two sites with the same score can have very different problems, so read the individual results.

What to fix first

  1. Anything marked as failed under security, because it affects trust and can block visitors.
  2. A noindex rule or a robots.txt that blocks the site, because these stop the page from appearing in search at all.
  3. A missing title, meta description or H1 on your most important pages.
  4. Server response time, compression and caching, which usually improve together with better hosting or a caching plugin.
  5. Warnings last, starting with the cheapest to fix, such as the favicon, social tags and alt text.

Fix one group at a time and run the checker again. Changes to headers and caching can take a few minutes to show, and the checker keeps a result for ten minutes to limit repeat requests.

What an automated check cannot do

This is one automated check of the single address you enter, made from our server. It cannot see pages behind a login, it does not judge content quality, backlinks or search intent, and it does not replace a full audit. A good score will not guarantee rankings, and nobody can honestly promise that. For deeper data, use our SEO tools and website audit, which can also pull PageSpeed, Search Console and Analytics information when you connect your own Google account.

How often should you check?

Run the checker after any change that touches your hosting, theme, plugins, security settings or redirects, and at least once a quarter otherwise. Check your homepage and one or two key service or product pages, because a problem on a template usually appears on every page that uses it.

Frequently asked questions

Is the Website Health Score really free?

Yes. It is free, needs no sign-up and does not ask for your email address. We may offer a free consultation afterwards, and you can ignore it.

What data does the checker collect?

It reads the public address you type, fetches that page and a few standard files such as robots.txt and the sitemap, and keeps the result for ten minutes to limit repeat checks. It does not log in to anything or change your site.

Why is my score lower than what PageSpeed Insights shows?

They measure different things. This score combines security, SEO basics, speed and mobile readiness in one number, while PageSpeed Insights focuses on loading performance and Core Web Vitals. Use both.

Will a higher score improve my Google ranking?

Fixing real problems removes obstacles to being crawled and understood, and that helps. But rankings depend on content quality, competition, links and time, so no score can guarantee a position.

Can I check a competitor or a client?

Yes, for any public website address. The checker only reads what is publicly visible, so it works for competitor research and client reviews, but it cannot see anything private.

Why does the checker say it could not reach my site?

The address may be mistyped, the server may block automated requests, or the site may be down. The tool only accepts public websites on the standard web ports.

Does the score check every page?

No. It checks the one address you enter, plus site-wide files such as robots.txt and the sitemap. Run it on each important page separately.

Related free tools and services

Want a fuller review? Try the SEO tools and website audit, then plan improvements with our guidance on website speed, security and backups and technical SEO. More tools are on our free website tools page, including the Readability and Headline Checker for the content side of SEO.

Need help acting on your results? Technology consulting is free, and we can go through the fixes with you.

Share Your Love