How It Works

What You Get

Paste the address of one page, pick the checks you want and press the play button in the frame's corner (it reads Run the Test as you reach it). Each check runs on its own helper and fills its board the moment it answers, so a slow one never holds the others. Every fresh result goes to your history, one row per click (a result that came back from the last 10 minutes adds none), where a click on the row opens its fixes again. Every check reads the page as published: a change made on your own computer shows once the page is published again.

Under each board, the fixes sit in a bucket of their own. Show opens the list; every item opens to a step: what to change, where it lives, what the test found, and a line to paste into the AI that has your site's code open.

Speed Check

What it tests

Google's own PageSpeed test of your page, as a phone or as a desktop: the lab score from 0 to 100, the six timings behind it, and the failed audits with the files Google names under each. When Google has enough Chrome visitors on the page, the real-visitor numbers of the last 28 days come too; those are the numbers Google ranks on.

Why it matters

Google ranks on the Core Web Vitals: how fast the biggest thing on the screen appears, how fast the page answers a tap, and how much it jumps about while it loads. A slow page loses the visitor before it loses the ranking.

How it works

A single run of the test moves 10 to 20 points between runs of the same page, so five runs go out at once and the middle one counts; the lowest and the highest show under the ring. Your first test of an address on a device is its baseline, and every later test shows the change against it in the status box (the app keeps your newest 300 results, so once the first one goes, the oldest kept becomes the baseline).

Where it stops

Three tests of the same address and device inside 10 minutes, by any member; after that the last result, whoever ran it, comes back until the window has passed. The app's Google tests are a shared daily pool, split fairly among the members who tested that day, so one account cannot cut the others off.

Security Check

What it tests

Twenty-five checks in six groups: the certificate and TLS, the security headers, the third-party code the page loads, information the site leaks, the mail and domain records (SPF, DMARC, DNSSEC, CAA) and a few best practices. The result is a score, a grade from A+ to F, and a cap when one finding holds the grade down whatever the score: no HTTPS, no DMARC policy, a secret key in the page.

Why it matters

A site that can be spoofed, hijacked or read from the outside loses mail, trust and rankings, and the headers that stop most of it cost a line each. Google marks pages without HTTPS and browsers warn on them.

How it works

The scanner reads your page, its headers and its DNS records the way a visitor's browser would, and nothing more: it logs into nothing, sends nothing to the page and leaves nothing behind. Each failed check comes with the scanner's own lines to add or change.

Where it stops

For security reasons the scanner takes one scan every 30 seconds and each account gets one security check a minute (a second check of an address you tested in the last 10 minutes brings your last result back with the time a new one can run; another address waits until that time), and 100 security checks a day; three scans of the same address inside 10 minutes, by any member, bring the last result back, whoever ran it. It reads one page, not the whole site.

Technical SEO Check

What it tests

The HTML of the page, the tags that build it, read against the HTML standard by the W3C checker: errors (code the standard forbids, such as a tag opened and never closed, two elements with the same id, an image with no alt text), warnings (code that can misbehave) and notes (habits worth dropping).

Why it matters

A browser and Google's crawler guess at broken code, and they can guess differently; structured data, accessibility and the layout itself depend on code that parses one way.

How it works

The checker fetches the page as published and lists every message with its line. The score starts at 100 and takes 5 for each kind of error and 1 for each kind of warning; the same mistake on twenty images is one kind, since it is one fix. The messages come grouped by kind, each with up to ten of the lines it sits on. The checker stops at about 1,000 messages on one page (notes count too), at a tag it cannot recover from, or at a charset declared too late in the page, and the board says so: what it read is not the whole page, so no score stands; fix what it listed, publish and test again.

Where it stops

Each account gets five HTML checks a minute (a sixth check inside the minute, of an address you tested in the last 10 minutes, brings your last result back with the time a new one can run; another address waits until that time) and 100 a day. Three checks of the same address inside 10 minutes, by any member, bring the last result back, whoever ran it, and it reads one page, not the whole site. The checker is the W3C's public service, which asks for fair use: when that service is busy the check answers "try again in a minute", and the app's own limits name the time instead.

What comes next

A crawl of the whole site, page by page: titles, descriptions, headings, broken links, redirects and the pages Google is told not to index. It arrives with an Advanced mode that goes deeper on all three checks.

Your History

Every test you ran, newest first, the parts of one click on one row: the speed score as a ring, the security grade and the Technical SEO score as pills. Click a row and its result unfolds under it, on the same three boards a fresh test draws, with its address back in the form; a second click folds it. The address sits on one line, cut when it is long (open the row to read it whole), the day and the device beside it, or under it on a narrower screen; the search box at the top narrows the list (your last 100 tests, your own only) to the addresses that contain what you type; the History pill at the form's bottom left, opposite the play button, drops the list open under the form with its search box, and folds it again.

What We Keep

The addresses you test and their results, in rows only your login can read; a result from the last 10 minutes may come from another member's test, without their name or its time, and the newest 300 results of each check are kept per member. The checks run on the app's own helpers with keys that never reach the browser, and no password or key of yours goes into any check. A test reads a public page; it never logs into anything.