WordPress Site Health Analyzer

One address is enough. The server fetches the start page, picks up to three inner pages (a product, a category, a post) and runs a handful of probes: robots.txt, xmlrpc.php, the REST user list, ?author=1, readme.html, the upload directory, the http redirect and one CSS and one JS file. From that it derives what a WordPress or WooCommerce site could do better, scored and sorted by weight. After changes to the site, the button below the report runs it again and shows the difference, as long as this page stays open.

Up to fourteen requests go from this server to the address entered, with a plain GET and no cookies. Requests to private networks, loopback and link-local addresses are refused, including through redirects. The query is protected by reCAPTCHA v3; the calling IP address and the size of the request are stored for seven days, to limit the rate (six runs per hour) and to detect abuse. Neither the address nor the report is stored; only the browser keeps the previous run for the comparison, as long as the page is open.

Analyse the site

Limit worth knowing: this reads the delivered HTML and headers and executes nothing. Images that a script inserts later, tags that load after consent and everything the browser measures at runtime (Largest Contentful Paint, layout shift) stay invisible. The report says where to look, not how fast the page feels.