Every score here is contestable. This is what it was judged against.

What a visitor can understand about the offer from the mobile above-the-fold view alone, without scrolling or interacting.

1. 0–2Nothing above the fold identifies the business or what it sells — logo and navigation only, an unskippable splash/age gate, or a hero that fails to render.
2. 3–4Above the fold is a bare hero image or carousel with no statement of what is sold, or two or more overlays (cookie bar + popup + chat widget) cover the content on load.
3. 5–6The visitor must scroll once, or read a secondary element, to work out what is sold; the hero is decorative (stock photo, abstract slogan) rather than explanatory.
4. 7–8The offer and the next action are both identifiable without scrolling; at most one element competes with them (cookie bar, promo strip, chat bubble) and it closes in one tap.
5. 9–10Above the fold names the product, says who it is for, and shows one next action; at most one primary and one secondary CTA; no overlay obscures the hero; headline and body text are legible at default zoom.

Requires

SCREENSHOT — mobile viewport (412px)

If absent

Without a mobile render the above-the-fold view is unknown. Score at low confidence inside the neutral band, state that the viewport was not captured, and do not claim an element is or is not visible.

Whether the largest text on the page states what is sold and to whom, in the visitor's language rather than the company's.

1. 0–2No H1, or the H1 is the company name alone, or it is an image with no text alternative, or it describes something the page does not sell.
2. 3–4The H1 is a brand slogan or feature jargon that cannot be decoded without reading body copy, or several H1s compete on the same page.
3. 5–6The H1 is understandable but generic — it would fit a competitor unchanged ("Quality you can trust", "Powering growth").
4. 7–8The H1 states the product or outcome and is specific to this business (a competitor could not paste it verbatim); at most one abstract term is used.
5. 9–10The H1 names a concrete outcome and the audience in under 12 words with no unexplained jargon, and the sub-headline adds mechanism or proof rather than restating it.

Requires

DOM SIGNALS (buttons, CTAs, forms, headings, images) · PAGE CONTENT (extracted text)

If absent

Without the extracted heading structure the "largest text" cannot be identified — a paragraph read from flattened text is not an H1. Score at low confidence in the neutral band and say the heading structure was unavailable. Never claim "no H1" from missing evidence.

Whether a visitor who is ready to act finds one obvious action, understands what it will do, and can reach it without hunting.

1. 0–2No call to action anywhere on the page, or every CTA is disabled, broken, or leads off-site to an unrelated destination.
2. 3–4The only CTA sits below the fold, is buried in navigation, is rendered as plain text, or is a phone number/email with no tap-to-act behaviour.
3. 5–6A CTA appears above the fold but its label is generic ("Submit", "Learn more", "Click here"), or three or more equally weighted CTAs compete for the same click.
4. 7–8A single primary CTA is visible without scrolling on mobile, its label states the outcome, and no more than two competing CTAs appear above the fold.
5. 9–10Exactly one primary CTA, repeated with the same label and styling at each decision point, its label naming the outcome ("Get my free audit", not "Submit"), visible above the fold on mobile with a tap target of at least 44px.

Requires

DOM SIGNALS (buttons, CTAs, forms, headings, images) · SCREENSHOT — mobile viewport (412px)

If absent

DOM signals are the source of truth for which buttons exist; the mobile render is the source of truth for whether they are above the fold. With either missing, score at low confidence in the neutral band and state which half is unknown. Never report "no CTA found" when the DOM was not read.

Whether a first-time visitor is given verifiable reasons to believe the business is real, competent, and safe to transact with.

1. 0–2No testimonials, reviews, policies, company identity or contact route — or claims that are demonstrably fake (duplicate stock-photo faces, dead award links).
2. 3–4One weak signal only: a generic "as seen in" strip, a security badge image with no issuer link, or a contact form as the sole route to a human.
3. 5–6Trust claims exist but are unattributable — anonymous testimonials ("— J.D., happy customer"), unlinked logo walls, round unsourced numbers ("10,000+ customers").
4. 7–8At least two independent and attributable trust categories — e.g. reviews carrying reviewer identity AND a published guarantee/refund/privacy position — plus working contact details.
5. 9–10Named customers with attributable detail (full name plus company or city, photo or verified review source), a named third-party proof (press, certification, audited figure), a reachable human channel (address, phone, registered entity), and a stated refund or guarantee position.

Requires

DOM SIGNALS (buttons, CTAs, forms, headings, images) · PAGE CONTENT (extracted text) · SITE FACTS (policy links, contact routes, footer, per-form fields)

If absent

Trust evidence is textual and structural. Without the page text, the markup and the site facts, absence cannot be distinguished from non-extraction. Score at reduced confidence in the neutral band; do not assert missing testimonials or missing policies.

Whether the page is usable on a 412px phone without zooming, horizontal scrolling, or mis-tapping.

1. 0–2Unusable on a phone: layout does not render, a desktop-only table or menu is required, an interstitial cannot be dismissed, or zoom is disabled on illegible text.
2. 3–4Horizontal scrolling is required, text needs pinch-zoom to read, elements overlap, or a fixed-width desktop layout has simply been scaled down.
3. 5–6Readable but cramped — body text between 12px and 16px, tap targets between 30px and 44px, or a sticky bar/chat widget covering part of the primary CTA.
4. 7–8Layout reflows cleanly with no horizontal scroll; at most one interactive target is undersized or one fixed element crowds the viewport.
5. 9–10No horizontal overflow, body text at least 16px, every interactive target at least 44px with at least 8px spacing, sticky elements under a quarter of the viewport, and form fields using the correct input types.

Requires

SCREENSHOT — mobile viewport (412px) · RENDER METRICS (overflow, tap targets and font sizes measured at 412px)

If absent

Mobile readiness is a rendering property. With no measurement, describe only what the screenshot plainly shows and never state a pixel size, a tap target size or the absence of overflow as fact. With no mobile render at all, score at low confidence in the neutral band and state that the 412px viewport was not captured. A responsive meta tag is not evidence that the layout works.

How quickly the page becomes usable on a mid-tier mobile device on a typical connection, measured rather than felt.

1. 0–2Lighthouse mobile performance below 30, LCP over 6s, or the main content never renders inside the measurement window.
2. 3–4Performance 30–49, LCP 4.0–6.0s, CLS above 0.25, or INP above 500ms — the wait is long enough that visitors abandon before first paint of content.
3. 5–6Performance 50–69, LCP 3.0–4.0s, or CLS 0.10–0.25 — a visible wait or a visible layout shift during load.
4. 7–8Performance 70–89 with LCP at or under 3.0s and no single Core Web Vital in a failing band.
5. 9–10Performance 90 or above with LCP at or under 2.5s, CLS at or under 0.1, and INP at or under 200ms.

Requires

LIGHTHOUSE PERF (real mobile measurements)

If absent

Speed is the one dimension with a real instrument. If Lighthouse did not return, DO NOT substitute an impression of heaviness from the screenshot: score at low confidence in the neutral band and state that no measurement was collected.

Whether the page gives search engines and answer engines the minimum structured facts needed to index it and quote it correctly.

1. 0–2No title, no headings, no meta description and no canonical — or the page blocks indexing (noindex/robots) while serving as a commercial landing page.
2. 3–4Title or H1 missing or duplicated, no meta description, no structured data, and alt text on under a quarter of content images.
3. 5–6Title present but templated or generic ("Home | Brand"), meta description missing or auto-truncated, no JSON-LD, alt coverage between 25% and 60%.
4. 7–8Title, meta description, a single H1 and a canonical URL are all present and specific to the page; some valid structured data; alt coverage at or above 60%.
5. 9–10Unique descriptive title (≤60 chars) and meta description (≤160 chars), exactly one H1 over a sensible H2 outline, valid JSON-LD matching the page's actual type, canonical URL, and meaningful alt text on at least 90% of content images (decorative images with an empty alt do not count against this).

Requires

DOM SIGNALS → meta/schema subset (title, meta description, JSON-LD)

If absent

Title, meta description, canonical and JSON-LD are invisible in rendered text and in screenshots. Without the meta/schema extraction, score at low confidence in the neutral band and state that head metadata was not read. Never report "no meta description" from an unread head.

Whether the path from arrival to the completed action is short, unblocked, and free of steps that give the visitor a reason to stop.

1. 0–2The stated action cannot be completed — broken form, non-functional cart or booking, a CTA pointing at a 404, or no path from this page to any conversion at all.
2. 3–4Hard blocks on the path: mandatory account creation before any value, more than 8 form fields, or a checkout/enquiry demanding information the page never explains.
3. 5–6The path works but leaks: 5–8 form fields, at least one field the offer does not justify (company size for a PDF, phone for a newsletter), or the price only becomes visible after a form.
4. 7–8The primary action completes in 3 steps or fewer, every field asked for is justified by the offer, and the main objection (price, timing, commitment) is answered before the CTA.
5. 9–10The primary action completes in 2 steps or fewer with 4 or fewer fields, price/terms/delivery are stated before the commitment point, errors are inline and recoverable, and no account or payment detail is demanded before value is shown.

Requires

DOM SIGNALS (buttons, CTAs, forms, headings, images) · PAGE CONTENT (extracted text) · SITE FACTS (policy links, contact routes, footer, per-form fields)

If absent

Field counts and destinations come from the markup. Without them the funnel is guesswork: score at reduced confidence in the neutral band and state that form structure was not read. Never claim there is no form when forms were not read.