The proof. Plain and simple.

This is how your report looks. A real Adam Designs scan from October 1, 2026, with the full case file open for this sample. No payment required.

Download evidence

THE SHERIFF’S RULES

Cuff ’em. Then lock ’em up.

Under 75%: cuffs. Under 65%: the bars drop.

Desktop page captured from adamdesgns.com during the saved scan — **64% · Site in lockup**Demo check percentage · actual scan unchanged

Effect demo only. These percentages are examples, not Adam Designs’ result. The real report is below. Effects follow technical checks, not design taste.

WEBSITE INSPECTION

adamdesgns.com

A solid start. A few things to check.

Desktop + Phone · One public page

62 of 73 applicable checks passed

Confirmed issues: 0None in these checks
Needs a look: 9Review before changing
Not verified: 2Needs a manual check

THE INSPECTION

Your website, at a glance.

Choose a category

More filled stars = more applicable checks passed. Stars measure check results, not design taste or business success. 32 inapplicable checks are excluded.

Design & messaging

Not assessed in this technical scan. No design rating has been assigned.

Getting discovered

Search setup is checked above. Rankings, traffic and actual inquiries are not verified.

FOLLOW THE EVIDENCE

What to check first.

11 recorded next steps

Confirm the context, make the smallest useful change, then check it again.

01Needs context review · medium priorityCheck what moves while the page loads
What we observed0.1270 in a 2188ms initial-load lab capture. Reference threshold 0.1; this is one unthrottled run, not real-user Core Web Vitals.
Recommended next stepReserve dimensions for images and embeds; prevent late content and font swaps from shifting visible content.
How to verify itRepeat under comparable conditions, then check real-user field data before claiming a performance improvement.
02Needs context review · medium priorityTake a closer look at large downloads
What we observed4770 KiB across 27 finished network requests; 0 failed/blocked. This is a lower bound for the capture window, including redirects where reported. A heavy page is not automatically slow.
Recommended next stepInspect the largest assets and remove unnecessary downloads without reducing required functionality.
How to verify itCompare transferred bytes and measured loading time on a repeat visit under the same conditions.
03Needs context review · medium priorityReview which content your browser can load
What we observedNo enforcing Content-Security-Policy header observed.
Recommended next stepReview required resource origins and deploy a tested content policy, starting with report-only where needed. Avoid breaking scripts, embeds or payments.
How to verify itExercise the actual website with enforcement on and inspect policy violations. Header presence alone is not a security pass.
04Needs context review · medium priorityDecide where your website can be embedded
What we observedX-Frame-Options: not observed.
Recommended next stepIf embedding is not intended, configure CSP frame-ancestors with the allowed origins. Frame ancestors takes precedence over X-Frame-Options.
How to verify itTry the intended and an unintended embedding origin; confirm that allowed integrations still work.
05Needs context review · medium priorityCheck how browsers handle your files
What we observedX-Content-Type-Options: not observed.
Recommended next stepSet X-Content-Type-Options: nosniff and serve assets with the correct MIME types.
How to verify itConfirm nosniff and correct script/style Content-Type values on their actual responses.
06Needs context review · medium priorityReview what outgoing links disclose
What we observedNo explicit Referrer-Policy header. Modern browser defaults still apply; this is not proof of a leak.
Recommended next stepConfirm the referrer policy fits the site’s privacy and integration needs.
How to verify itInspect outgoing referrer information on relevant links without submitting sensitive information.
07Needs context review · medium priorityConsider useful business information for search
What we observed0 JSON-LD block(s); 0 invalid JSON; detected types: none. 0 microdata/RDFa marker(s). Syntax parsing does not validate schema or eligibility.
Recommended next stepRepair malformed JSON first. Add or validate only schema supported by actual page content; structured data is not required on every page.
How to verify itValidate relevant markup with a schema validator and, where appropriate, Google’s Rich Results Test. Confirm every claim on the page.
08Needs context review · medium priorityConfirm your crawler instructions
What we observedHTTP 200. Public crawler directives found. User-agent: * | Allow: / | Sitemap: https://adamdesgns.com/sitemap.xml Rules were not evaluated for each crawler. Robots.txt controls crawling, not guaranteed indexing.
Recommended next stepConfirm intended crawler access and any sitemap declaration; preserve intentional exclusions.
How to verify itOpen the actual document, validate its contents, and check the intended public URLs. Do not infer whole-site coverage from one file.
09Needs context review · medium priorityCheck the pages in your sitemap
What we observedHTTP 200. Sitemap markup found; XML validity and listed destinations were not verified.
Recommended next stepCheck the sitemap declared in robots.txt or the hosting configuration. A sitemap may intentionally use another path.
How to verify itOpen the actual document, validate its contents, and check the intended public URLs. Do not infer whole-site coverage from one file.
10Needs manual verification · low priorityCheck the review seal’s accessible label
What we observeddesktop: incomplete; desktop: passes; phone: incomplete; phone: passes Manual review: desktop: .grok-reviews__seal: Fix all of the following: aria-label attribute is not well supported on a div with no valid role attribute. phone: .grok-reviews__seal: Fix all of the following: aria-label attribute is not well supported on a div with no valid role attribute.
Recommended next stepReview the affected elements with appropriate keyboard, screen reader and visual checks.
How to verify itRepeat the recorded check at desktop and phone sizes; verify the affected element in its actual context.
11Needs manual verification · low priorityCheck text over gradient backgrounds
What we observeddesktop: incomplete; desktop: passes; phone: incomplete; phone: passes Manual review: desktop: span[data-brand-name=""]: Fix any of the following: Element's background color could not be determined due to a background gradient desktop: a[href$="work"][style-hover="color:#ff9f45"]: Fix any of the following: Element's background color could not be determined due to a background gradient desktop: a[href$="#principles"]: Fix any of the following: Element's background color could not be determined due to a background gradient desktop: div[data-nav-links=""] > a[href$="about"][style-hover="color:#ff9f45"]: Fix any of the following: Element's background color could not be determined due to a background gradient desktop: nav > a[data-project-interest=""][href$="#project-brief"]: Fix any of the following: Element's background color could not be determined due to a background gradient phone: nav > a[data-project-interest=""][href$="#project-brief"]: Fix any of the following: Element's background color could not be determined due to a background gradient phone: div[data-hero-copy=""] > p:nth-child(1): Fix any of the following: Element's background color could not be determined due to a background gradient phone: h1: Fix any of the following: Element's background color could not be determined due to a background gradient phone: h1 > span: Fix any of the following: Element's background color could not be determined due to a background gradient phone: p[data-hero-lede=""]: Fix any of the following: Element's background color could not be determined due to a background gradient
Recommended next stepReview the affected elements with appropriate keyboard, screen reader and visual checks.
How to verify itRepeat the recorded check at desktop and phone sizes; verify the affected element in its actual context.

Sample based on one saved desktop and phone scan. No AI design review was run. Forms and purchases were not submitted; actual search visibility was not measured. Read the inspection limits.