Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for nickradford.dev
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
Nickradford.dev
Final URL
https://nickradford.dev
Created
Jul 1, 2026, 10:50 PM
Safe fetch
274 ms
Four-score result
Close to ready (Needs polish): 27 passed, 9 failed, and 0 unknown. Strongest area: Security. Weakest area: Design.
Overall
74
out of 100
SEO / AEO
72
out of 100
66/92 rule points
Security
82
out of 100
62/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
71
out of 100
78/110 rule points
Why this scored this way
Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.
Category point breakdown
SEO / AEO66/92
Security62/76
Accessibility68/94
Design78/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-command-name (1), color-contrast (32), list (1), landmark-unique (1).
high
Security
Common security headersDetected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
high
Design
Visible primary CTADetected 0 CTA candidate(s).
high
SEO / AEO
sitemap.xml reachabilityHTTP 404 returned for sitemap_xml.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
6 opportunities
9 insights
1
fail
high
Security
Priority 5
Add common public security headers
-14 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
How to fix it
Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
2
fail
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-command-name (1), color-contrast (32), list (1), landmark-unique (1).
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
3
fail
high
Design
Priority 4
Make the primary CTA obvious
-14 rule ptsWhat failed
The page does not have a detectable call to action.
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: fix before sharing the page publicly.
Why it matters
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
How to fix it
Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
4
fail
high
SEO / AEO
Priority 7
Publish sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable.
Evidence
HTTP 404 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
5
fail
high
SEO / AEO
Priority 12
Add basic structured data
-10 rule ptsWhat failed
No JSON-LD schema was detected on the page.
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
Why it matters
Structured data gives search and answer engines explicit facts about your product.
How to fix it
Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
Unknown and not detected states
FreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.
0 unknown
Safe public scans cannot see private cookies, authenticated content, browser-rendered state, or reliable contrast values unless they are present in static public markup.This scan did not produce unknown checks. If a future page has partial public data, the report will show those checks here instead of guessing.
Score aggregation details
Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.
72/100
8 pass, 3 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
high
sitemap.xml reachability
-12 rule ptsHTTP 404 returned for sitemap_xml.
high
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
low
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
82/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-14 rule ptsDetected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
72/100
6 pass, 2 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
high
Rendered axe accessibility violations
-18 rule ptsaxe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-command-name (1), color-contrast (32), list (1), landmark-unique (1).
medium
Basic contrast
-8 rule pts25 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
71/100
8 pass, 3 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
high
Visible primary CTA
-14 rule ptsDetected 0 CTA candidate(s).
medium
Readability signals
-9 rule ptsAverage sentence length is about 38 word(s).
medium
Visual hierarchy
-9 rule ptsDetected 1 hierarchy signal(s) from headings, CTA, and emphasized text.
Full check list
Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.
Showing failed checks.
Failed checks
These checks need attention.
fail
high
SEO / AEO
sitemap.xml reachability
0/12HTTP 404 returned for sitemap_xml.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add /sitemap.xml with your public URLs and confirm it returns HTTP 200.
fail
low
SEO / AEO
LLM-readable file
0/4HTTP 404 returned for llms_txt.
Failed: earned 0 of 4 points.
Priority: Priority 24: lower-risk cleanup after urgent launch blockers.
Why it matters: A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
Fix: Add /llms.txt or /.well-known/llms.txt with the product name, audience, value proposition, and key public links.
fail
high
SEO / AEO
Schema presence
0/10Detected 0 JSON-LD schema block(s).
Failed: earned 0 of 10 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Structured data gives search and answer engines explicit facts about your product.
Fix: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
fail
high
Security
Common security headers
4/18Detected 1 of 5 common public security headers. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 4 of 18 points from partial coverage.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Fix: Configure headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
fail
medium
Accessibility
Basic contrast
0/825 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Failed: earned 0 of 8 points.
Priority: Priority 20: lower-risk cleanup after urgent launch blockers.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
fail
high
Accessibility
Rendered axe accessibility violations
0/18axe found 4 violation rule(s), including 3 serious or critical rule(s). Top rules: aria-command-name (1), color-contrast (32), list (1), landmark-unique (1).
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
fail
high
Design
Visible primary CTA
0/14Detected 0 CTA candidate(s).
Failed: earned 0 of 14 points.
Priority: Priority 4: fix before sharing the page publicly.
Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
fail
medium
Design
Readability signals
0/9Average sentence length is about 38 word(s).
Failed: earned 0 of 9 points.
Priority: Priority 23: lower-risk cleanup after urgent launch blockers.
Why it matters: Launch visitors often skim; long sentences make the offer harder to understand.
Fix: Shorten long sentences, use direct language, and break dense paragraphs into smaller sections.
fail
medium
Design
Visual hierarchy
0/9Detected 1 hierarchy signal(s) from headings, CTA, and emphasized text.
Failed: earned 0 of 9 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Hierarchy tells visitors what to read first and what action to take next.
Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
Safe fetch metadata
Public headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Landing page
Step 1HTTP 2002 captured header(s)Checked: https://nickradford.dev
Next/final: https://nickradford.dev
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2002 captured header(s)Checked: https://nickradford.dev
Next/final: https://nickradford.dev
Content type: text/html; charset=utf-8
Content hash: e14a718c6a2f58cbca97b4af1727e309032bf05a061e1f2f850a75fe3135ab04
robots.txt
Step 3HTTP 2002 captured header(s)Checked: https://nickradford.dev/robots.txt
Next/final: https://nickradford.dev/robots.txt
Content type: text/plain; charset=utf-8
Content hash: a4f903467d1516d5f0c5042b26f9d3df9349d1075057dbec586bd4138981b35a
sitemap.xml
Step 4HTTP 4042 captured header(s)Checked: https://nickradford.dev/sitemap.xml
Next/final: https://nickradford.dev/sitemap.xml
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for sitemap_xml.
llms.txt
Step 5HTTP 4042 captured header(s)Checked: https://nickradford.dev/llms.txt
Next/final: https://nickradford.dev/llms.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for llms_txt.
Security probe
Step 6HTTP 4042 captured header(s)Checked: https://nickradford.dev/.env
Next/final: https://nickradford.dev/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4042 captured header(s)Checked: https://nickradford.dev/.git/config
Next/final: https://nickradford.dev/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 8HTTP 4033 captured header(s)Checked: https://nickradford.dev/wp-config.php
Next/final: https://nickradford.dev/wp-config.php
Content type: text/html; charset=UTF-8
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 9HTTP 4042 captured header(s)Checked: https://nickradford.dev/backup.zip
Next/final: https://nickradford.dev/backup.zip
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Captured public headers
content-type
text/html; charset=utf-8
strict-transport-security
max-age=63072000
Public report link
Markdown export
Share the website audit report
Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.
Share preview
nickradford.dev website audit report
Close to ready: 74/100 overall, with prioritized fixes for SEO, security, accessibility, and design.
Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.
Rescan same URL
Rerun the full deterministic scanner for nickradford.dev without re-entering the URL. The previous report stays saved so the next result can be compared against it.