Skip to content

Demo data

Demo Scan Result

This is what a report looks like. Nothing on this page was produced by a live scan.

Scan your own site

Demo data — example findings for a fictional website (demo-shop.example.com).

66/ 100
Scoring v3.0

Website Health

1 verified problem should be fixed before your next release, plus 4 smaller issues. 1 finding needs manual review.

6unique issues ·7locations5verified1uncertain
Website
demo-shop.example.com(opens in a new tab)
Status
Completed
Date
Oct 1, 10:00 AM
Duration
41s
Pages examined
3
Checks completed
8/8

Universal AI Fix Prompt

One repair prompt for all verified issues — with evidence, reproduction steps, expected behaviour and tests. Free, and works with any coding AI.

Works with ChatGPT, Claude, Cursor, Gemini, Lovable, Replit, Bolt, Copilot

Fix these first 1

HighImportant feature may breakVerified

A list on this page can crash

What happened?
Uncaught TypeError: Cannot read properties of undefined (reading 'map')
Why does it matter?
A list or section may stop loading for some visitors and stay empty or broken.
How certain are we?
Verified. Proven by measured evidence.
How can it be fixed?
Check that the data exists before rendering it and show a safe loading or empty state.Possible cause (not confirmed in your code): The page tries to read data before it is available.
Page /

Smaller verified issues 4

MediumUsers may notice a problemVerified2 pages

Pricing link leads to a missing page

What happened?
The link target answers HTTP 404.
Why does it matter?
Visitors who click “Pricing” get a 404 page.
How certain are we?
Verified. Proven by measured evidence.
How can it be fixed?
Update the link or restore /pricing.Possible cause (not confirmed in your code): The link points to /pricing, which doesn't exist in the deployed site.
Page /+1 more
MediumUsers may notice a problemVerified

Email field is difficult to use with screen readers

What happened?
The field has no associated label (placeholder text alone is not a label).
Why does it matter?
People using accessibility tools may not know what this field is for.
How certain are we?
Verified. Proven by measured evidence.
How can it be fixed?
Add a visible <label for="…"> (or an aria-label) that says what to enter.Possible cause (not confirmed in your code): The field has no label connected to it — a placeholder alone isn't announced reliably.
Page /
MediumUsers may notice a problemVerifiedMobile

Page scrolls sideways on phones

What happened?
The document is 512px wide in a 390px viewport.
Why does it matter?
On mobile, visitors can swipe the page left and right and content gets cut off.
How certain are we?
Verified. Proven by measured evidence.
How can it be fixed?
Limit the element's width (max-width: 100%), let rows wrap, and avoid fixed pixel widths.Possible cause (not confirmed in your code): An element is wider than the phone screen.
Page /
LowImprovement recommendedVerified

Google has no summary for this page

What happened?
No meta description.
Why does it matter?
Search results show a random snippet of text instead of your pitch.
How certain are we?
Verified. Proven by measured evidence.
How can it be fixed?
Add a meta description of about 120–160 characters that describes the page.Possible cause (not confirmed in your code): The page has no meta description.
Page /products

Needs review 1

MediumUsers may notice a problemNeeds review

The page reports an error in the background

What happened?
console.error: Analytics: consent not given, events dropped
Why does it matter?
Visitors may not notice anything yet, but something on the page isn't working as intended.
How certain are we?
Needs review. console.error is often used for logging; a logged message alone does not prove that something on the page is broken. Investigate before changing code.
How can it be fixed?
Open the browser console on this page, reproduce the error and fix the code shown in the technical details.Possible cause (not confirmed in your code): JavaScript on the page throws an error that isn't handled.
Page /products

Retest after your fix

  1. 1Fix these issues
  2. 2Deploy your changes
  3. 3Run scan again
Scan your own site

Compared with your previous scan

Before

54

Now

66

+12

3 issues fixed · 4 remaining · 1 new

What was checked8/8 complete
  • Homepage loadsChecked · 1.2 s
  • Page structureChecked · 180 ms
  • Console & networkChecked · 38.2 s
  • Internal linksChecked · 12/12 · 3.4 s
  • Internal pagesChecked · 2/2 · 4.1 s
  • Accessibility & SEOChecked · 3/3 · 20 ms
  • Mobile layoutChecked · 2.6 s
  • Load performanceChecked · 3/3 · 40.1 s
Pages examined 3

Loaded in Chromium — desktop 1440×900 and mobile 390×844. Load times are single synthetic measurements from Scaneryx's scanner (cold cache).

  • 200

    /

    Demo Shop

    1.24s
  • 200

    /products

    Products

    0.98s
  • 200

    /about

    About

    0.76s