How scores work
wpsite.health checks a WordPress site in eight areas. This page lists every check, what it looks at and how much it counts. Rules version 1.1.0.
The basics
Every check passes, warns or fails
A check scores between 0 and 1. 90% or more is a pass, 50% or more a warning, anything lower a failure. Timings such as load time score in proportion between a "good" and a "poor" value.
Each area is a weighted average
An area's score is its checks' scores, weighted as shown below, out of 100. Checks we couldn't measure (no forms to check, a theme not listed on WordPress.org) are left out and the rest count for more. If less than 40% of an area could be measured, it isn't scored.
The overall score is a plain average
The overall score is the average of the area scores we could measure. 90 and up is green, 50 to 89 amber, below 50 red.
Fixes start with AI readiness
Every warning and failure becomes a fix. AI readiness fixes come first, then the rest by how many points they'd add to their area (the number after the +).
The AI writes the words, not the scores
Scores come only from these fixed rules. An AI model browses the site to answer four questions (what you do, prices, contact, who runs it) and must quote the page it found each answer on; it also writes the summary and fix wording.
AI and agent readiness
llms.txt, crawler rules, structured content
AI assistants may read the site
15%robots.txt rules for the crawlers AI assistants send when someone asks about a site (ChatGPT, Claude, Perplexity). Blocking AI training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended) is your choice and costs nothing.
Pass: none blocked · Warning: some blocked · Failure: all blocked, or every crawler blocked
llms.txt file
10%A plain-text guide at /llms.txt that tells AI models what the site is and links to its key pages.
Pass: has a # title and at least one link · Warning: exists but has neither · Failure: missing
Sitemap
5%An XML sitemap that lists the site's pages, and a link to it in robots.txt so crawlers find it.
Pass: found and listed in robots.txt · Warning: found, not listed · Failure: none
Structured data about the business
15%JSON-LD that names the organisation or person behind the site (Organization, LocalBusiness, Person, …) on the homepage, and structured data on inner pages too.
Pass: named organisation on the homepage and data on inner pages · Warning: homepage only, or no named organisation · Failure: none
AI can tell what the business does
15%An AI assistant browses the site and must quote the sentence that says what the business does.
Pass: found, and the quote is on the page · Warning: unclear · Failure: not found
AI can find prices
10%The AI assistant looks for prices or rates. Not counted when the business has nothing priced to sell.
Pass: found, and the quote is on the page · Warning: unclear (e.g. "price on request") · Failure: not found
AI can find contact details
15%The AI assistant looks for an email address, phone number, contact form or address.
Pass: found, and the quote is on the page · Warning: unclear · Failure: not found
AI can tell who runs the site
10%The AI assistant looks for the company or person behind the site.
Pass: found, and the quote is on the page · Warning: unclear · Failure: not found
Content readable without JavaScript
5%Words of main homepage content in the HTML as served. Many AI crawlers don't run JavaScript.
Pass: 150 words or more · Warning: 50–149 · Failure: under 50
Performance
Core Web Vitals on mobile and desktop
Speed score on phones
35%Google's Lighthouse performance score for the homepage on a mid-range phone (PageSpeed Insights).
Counts as the score itself: 90+ passes, 50–89 is a warning, below 50 fails
Speed score on computers
15%Lighthouse performance score for the homepage on a desktop computer.
Counts as the score itself: 90+ passes, 50–89 is a warning, below 50 fails
Main content load time
20%How long the largest piece of content takes to appear on a phone (Largest Contentful Paint). Real-visitor data when Google has it, otherwise the test run.
2.5 s or less passes, 4 s or more fails, in between scores proportionally
Response to taps
10%How quickly the page reacts to taps (Interaction to Next Paint from real visitors; Total Blocking Time from the test when there's no visitor data).
INP: 200 ms or less passes, 500 ms or more fails · TBT: 200 ms passes, 600 ms fails
Layout shift
10%How much the page jumps around while it loads (Cumulative Layout Shift).
0.1 or less passes, 0.25 or more fails
Server response time
10%How long the server takes to start answering (Time to First Byte).
0.8 s or less passes, 1.8 s or more fails
Accessibility
Contrast, alt text, landmarks, forms
Lighthouse accessibility score
50%Google's automated accessibility audit of the homepage (contrast, names, labels, ARIA and more).
Counts as the score itself: 90+ passes, 50–89 is a warning, below 50 fails
Image descriptions
15%Images on the homepage, a post and a page with no alt attribute at all (alt="" for decoration is fine).
Pass: none · Warning: 1–3 · Failure: 4 or more
Text contrast
15%Whether text stands out enough from its background (Lighthouse color-contrast audit).
Pass: audit passes · Failure: audit fails
Form labels
10%Form fields and dropdowns have labels a screen reader can announce (Lighthouse label and select-name audits). Not counted without forms.
Pass: every field labelled · Failure: unlabelled fields
Link and button names
5%Links and buttons have text a screen reader can read out (Lighthouse link-name and button-name audits).
Pass: both pass · Warning: one fails · Failure: both fail
Page language
5%The page says which language it's in (<html lang>), so screen readers pronounce it right.
Pass: set · Failure: missing
Mobile experience
Viewport, tap targets, small-screen layout
Fits phone screens
30%A viewport tag with width=device-width, so phones show the page at their own width instead of a shrunken desktop page.
Pass: present · Failure: missing
Pinch to zoom
10%Visitors can zoom in (no user-scalable=no, and maximum-scale of at least 2).
Pass: zoom allowed · Failure: zoom blocked
Tap targets
30%Buttons and links are big enough, and far enough apart, to tap with a finger (Lighthouse target-size audit).
Pass: audit passes · Failure: audit fails
Readable text size
15%Text is large enough to read on a phone without zooming (Lighthouse font-size audit, when Lighthouse still runs it).
Pass: audit passes · Failure: audit fails
Phone-sized images
15%Share of content images that offer smaller sizes for phones (srcset). Not counted with fewer than 3 images.
Pass: 80% or more · Warning: 40–79% · Failure: under 40%
Theme best practices
Coding standards and responsive rules
Page landmarks
20%Each template marks up its header, navigation, main content and footer, so assistive tech and AI can find the main content.
Pass: every template · Warning: one inner template misses some · Failure: two or more, or the homepage
Heading structure
15%Each template has exactly one main heading (h1), and heading levels don't skip (h2 straight to h4).
Pass: every template · Warning: one template off · Failure: two or more
Skip link
10%A "Skip to content" link for keyboard users.
Pass: present · Failure: missing
Lighthouse best practices
25%Google's best-practices audit: HTTPS, console errors, deprecated code, image aspect ratios and more.
Counts as the score itself: 90+ passes, 50–89 is a warning, below 50 fails
Scripts that block the page
10%Scripts in the page head that load without async or defer, so the browser waits for them before showing anything.
Pass: 2 or fewer · Warning: 3–5 · Failure: more than 5
Lazy loading
10%The main image loads straight away, and images further down wait until they're needed.
Pass: main image eager, at least half the others lazy · Warning: others not lazy · Failure: main image lazy
Inline code weight
10%CSS and JavaScript written straight into the homepage HTML, which every visit downloads again.
Pass: under 100 KB · Warning: 100–250 KB · Failure: over 250 KB
Site health
Core version, plugins, updates, security
WordPress version
25%The installed WordPress version against the latest release on WordPress.org. Not counted when the site hides its version.
Pass: latest · Warning: one release behind, or an older patch (counts less) · Failure: two or more releases behind
Plugin updates
20%Plugins whose version we can see (from their files or readme) against the latest on WordPress.org.
Pass: none outdated · Warning: 1–2 · Failure: 3 or more
Abandoned plugins
10%Plugins closed on WordPress.org, or not updated there in two years.
Pass: none · Warning: 1 · Failure: 2 or more
HTTPS
15%The site uses HTTPS, and the http:// address sends visitors there.
Pass: both · Warning: HTTPS, but http:// doesn't redirect · Failure: no HTTPS
Security headers
10%Four response headers that block common attacks: HSTS, nosniff, frame protection and a referrer policy.
Pass: 3 or 4 · Warning: 1–2 · Failure: none
PHP version
5%The PHP version the server shows in its headers, if it shows one, against PHP's end of support.
Pass: hidden or still supported · Failure: shown and out of support
User names hidden
5%Whether the REST API lists the site's user names to anyone (it helps password-guessing attacks).
Pass: hidden · Warning: listed
XML-RPC
5%Whether the old XML-RPC endpoint answers. Few sites need it, and it's a common target for password guessing.
Pass: closed · Warning: open
PHP errors on pages
5%PHP warnings or notices printed into the pages, which leak file paths and look broken.
Pass: none · Failure: present
Theme
Active theme, block or classic
Theme version
31%The installed theme (or the parent of a child theme) against its latest version on WordPress.org. Not counted for themes that aren't listed there.
Pass: latest · Warning: a minor or patch version behind (patch counts less) · Failure: a major version behind
Theme still maintained
19%When the theme (or its parent) was last updated on WordPress.org.
Pass: within 12 months · Warning: 12–24 months · Failure: over 2 years
Tested with current WordPress
19%The "Tested up to" WordPress version in the theme's style.css. Not counted when the theme doesn't say.
Pass: tested with the latest or previous release · Warning: older
Theme CSS and JavaScript
31%How much CSS and JavaScript the theme (and its parent) sends to a phone on the homepage.
Pass: under 150 KB · Warning: 150–400 KB · Failure: over 400 KB
SEO
Titles, canonicals, sitemap, schema
Lighthouse SEO score
30%Google's automated SEO audit of the homepage.
Counts as the score itself: 90+ passes, 50–89 is a warning, below 50 fails
Search engines may index the site
20%No "noindex" on the homepage (meta tag or header), and robots.txt doesn't block Google from it.
Pass: indexable · Failure: blocked
Page titles
10%The homepage has a title of 10–65 characters, and the post and page don't reuse it.
Pass: right length and unique · Warning: wrong length or reused · Failure: missing
Meta description
10%The homepage has a summary for search results of 50–160 characters.
Pass: 50–160 characters · Warning: other length · Failure: missing
Canonical address
10%The homepage names its own preferred address (canonical link) on the same site, over HTTPS.
Pass: present and correct · Warning: points elsewhere · Failure: missing
Sitemap
10%The same sitemap check as under AI readiness. Its fix shows there.
Pass: found and listed in robots.txt · Warning: found, not listed · Failure: none
Structured data
5%Any valid JSON-LD structured data on the homepage. Its fix shows under AI readiness.
Pass: present · Failure: none
Link previews
5%Open Graph title and image, used when the homepage is shared on social media and in chat apps.
Pass: both · Warning: one · Failure: none