Drop in your address. The scan runs live, and the results feed a plain-money projection from the checks completed during that run.
Under the score
The scan reads one public page the way a new customer, a search engine, and a cautious browser meet it. Each check has a plain status and a reason. Here is what runs behind the progress bar.
The scanner reads the raw page before browser scripts take over. It checks the title, description, canonical address, indexing rules, headings, useful page text, structured data, mobile viewport, image text, form labels, contact paths, and social-share tags. It also notes when important content only appears after JavaScript runs.
It confirms HTTPS and looks for the browser instructions that reduce common risks: HSTS, Content Security Policy, frame protection, content-type protection, referrer policy, and permissions policy. It also checks whether the plain HTTP address redirects safely and whether secure pages request insecure files.
The scan asks public DNS for mail servers, SPF, and DMARC. Those records help receiving mail systems tell a real message from a forged one. Missing SPF or DMARC can make estimates, confirmations, and follow-ups more likely to land in spam.
It counts internal links, samples whether they resolve, and checks for robots.txt and a sitemap. The page review also catches heavy or poorly described images, missing dimensions, old image formats, lazy-loading mistakes, and files that hold up the first screen. Together these show whether visitors and crawlers can move through the site without dead ends.
Google PageSpeed supplies a mobile performance run when that service is available. The scan reads its performance score, Largest Contentful Paint, layout shift, blocking time, tap targets, and render-blocking work. One lab run is a useful comparison point; real visitors will see different timings across devices and connections.
Response headers and page markup reveal the server, common frameworks, analytics tags, site builders, and whether meaningful text arrived from the server or waited for the browser. That distinction matters because slow devices, blocked scripts, and search crawlers may never see content that depends entirely on client rendering.
A pass earns full credit, a warning earns half, a failure earns none, and a skipped check is excluded. Category scores are weighted by buyer impact. Critical failures such as no HTTPS, no indexing, no mobile viewport, or client-only content subtract extra points and can cap the grade. Several weak categories also compound rather than hiding behind one strong number.
This is one automated look at one public page. It cannot judge whether the writing sounds like your business, whether the offer fits the market, whether a booking flow works after sign-in, or whether sales calls become customers. Private pages, paid tools, local listings, competitor context, and real-user history need a deeper review. A skipped check means the scanner lacked evidence, not that the site passed.