Skip to content
Audience Intel
Report section · measured

Pass, warn or fail. Measured by code, not judged by a model.

Inside the free Insight Report, the technical section runs real checks against your site: Google's PageSpeed test on mobile, your robots.txt and sitemap, your page structure and markup. Each one comes back pass, warn or fail.

Live Live as a section of the free Insight Report. There is no standalone version.

Cover of the sample report for Hadley & Whitmore Solicitors: report date, the three buyer archetypes read, the three firms it is compared with, and the note that all four firms are constructed
Sample report · Hadley & Whitmore is a constructed test firm
Mobile test: performance score and core measures
Google PageSpeed
Source: src/lib/connectors/pagespeed.ts · checked 2026-10-13
Each check marked against a fixed threshold
Pass · warn · fail
Source: src/lib/technical/audit.ts · checked 2026-10-13
The checks are deterministic code
No model in the verdicts
Source: src/lib/technical/audit.ts runTechnicalAudit · checked 2026-10-13
What it is

What it is, and how it works.

The measured part of the Insight Report: Google PageSpeed on mobile, crawlability, indexing, sitemap, structured data and the basics a search engine needs, each marked pass, warn or fail.

A robots file that blocks the wrong thing. A missing sitemap. A page with no title. A homepage that stalls on a phone. Each is cheap to fix and easy to miss, and each holds a site back however good the writing is. This check finds them.

It is part of the free Insight Report. When the report builds, we read your site, run Google's PageSpeed test on the mobile version, probe how the site responds, and read your robots.txt and sitemap. Then a fixed set of checks runs over what came back. These checks are written in code, not judged by a language model, so the same site gives the same verdict.

The checks cover whether the site uses HTTPS and loads cleanly; whether search engines and other crawlers are allowed in; whether pages can be indexed; whether a sitemap exists; whether the page is set up for mobile; loading speed from the PageSpeed result; structured data; whether your business name and location are clear; headings and FAQs; contact details; and the meta description, canonical address and page title.

Each comes back as pass, warn or fail. For speed we use the PageSpeed performance score and the core measures behind it (largest contentful paint, layout shift and total blocking time), plus Google's field-data category where Google has one for your site.

Who it is for

  • Owners who want to know whether their site has basic technical faults
  • Anyone briefing a developer and wanting a list to hand over
  • Firms preparing a site rebuild
What it does

What it reads, and what you see.

Speed on mobile

Google's PageSpeed test, run on the mobile version of your page, with the measures behind the score.

Can it be found

HTTPS, robots.txt, indexing, sitemap and canonical address, each checked.

Can it be understood

Titles, descriptions, headings, structured data, business name, location and contact details.

By hand, or with it

The same job, two ways.

By hand

  • Run PageSpeed yourself and puzzle over the output
  • Not know whether robots.txt blocks anything
  • Find out a page has no title only after launch
  • Rely on a developer's word that it is fine

With Technical and speed check

  • PageSpeed run for you, with the key measures
  • Crawl and index checks in one list
  • Each check marked pass, warn or fail
  • The same verdict every time for the same site
What you walk away with

What you keep.

A pass / warn / fail list

Every check, with its result.

A speed reading

The mobile performance score and the measures that drive it.

A developer brief

The fails and warnings, ready to hand over.

A baseline

Something to re-run after the fixes, to see what changed.

How it works

Three steps.

  1. Start the free report

    Enter your web address.

  2. We run the checks

    PageSpeed, robots.txt, sitemap and the page checks run against your site.

  3. Read the results

    Each check marked pass, warn or fail in the technical section.

Limits

What it does not do.

  • It tests the page you give us, on mobile. It is not a full crawl of every page.
  • PageSpeed results vary between runs; treat a single score as a reading, not a constant.
  • It checks the basics. It is not a full search-engine audit and does not track rankings.
  • Google's field data is only available for sites with enough traffic; smaller sites get the lab test only.
Price

Part of the free Insight Report.

The technical section is one of the report's sections; depending on which sections the free view opens, it may be among those that open with the unlock.

Free Insight Report
FAQ

Technical and speed check: questions

Is there a standalone version?

Not today. The checks run as the technical section of the free Insight Report.

Is a language model judging my site here?

No. The technical verdicts come from fixed checks written in code. The same site gets the same result.

Why only mobile?

Because most sites are judged on their mobile version, and running one consistent test keeps results comparable.

Why did my speed score change when I re-ran it?

PageSpeed results vary from run to run with network and server conditions. Look at the pattern, not one number.

Run it on your own business.

Live as a section of the free Insight Report. There is no standalone version.