Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for nicklaunches.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://nicklaunches.com/
Final URL
https://nicklaunches.com
Created
Jul 3, 2026, 4:28 AM
Safe fetch
352 ms
Four-score result
Close to ready (Needs polish): 27 passed, 9 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Security.
Overall
71
out of 100
SEO / AEO
100
out of 100
92/92 rule points
Security
45
out of 100
34/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
67
out of 100
74/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 / AEO92/92
Security34/76
Accessibility68/94
Design74/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (74), region (5).
critical
Security
Sensitive file probesA small allowlist probe returned a public success response.
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
Security
Mixed content indicatorsDetected 2 insecure asset or link reference(s).
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
4 opportunities
9 insights
1
fail
critical
Security
Priority 1
Remove exposed sensitive files
-16 rule ptsWhat failed
A small public allowlist probe found a sensitive-looking file path.
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Why it matters
Publicly exposed config or backup files can leak implementation details or secrets.
How to fix it
Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
2
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.
3
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (74), region (5).
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.
4
fail
high
Security
Priority 4
Remove insecure page resources
-12 rule ptsWhat failed
The page references insecure HTTP assets or links from an HTTPS page.
Evidence
Detected 2 insecure asset or link reference(s).
Priority
Priority 4: fix before sharing the page publicly.
Why it matters
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
How to fix it
Change public asset, link, and form URLs from http:// to https:// where the destination supports it.
5
fail
medium
Design
Priority 13
Fix rendered layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 166.
Priority
Priority 13: fix during launch polish.
Why it matters
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
How to fix it
Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
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.
100/100
11 pass, 0 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
45/100
3 pass, 3 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
critical
Sensitive file probes
-16 rule ptsA small allowlist probe returned a public success response.
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.
high
Mixed content indicators
-12 rule ptsDetected 2 insecure asset or link reference(s).
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (74), region (5).
medium
Basic contrast
-8 rule pts1 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.28.
67/100
7 pass, 4 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Text density
-10 rule ptsDetected about 2391 visible word(s).
medium
Rendered speed signals
-10 rule ptsDOMContentLoaded: 3338ms. Load complete: 3725ms. First contentful paint: 668ms. Resources: 209. Scripts: 18. Images: 3. Third-party origins: 76. Transfer: not available.
medium
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 166.
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
Security
Mixed content indicators
0/12Detected 2 insecure asset or link reference(s).
Failed: earned 0 of 12 points.
Priority: Priority 4: fix before sharing the page publicly.
Why it matters: Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Fix: Change public asset, link, and form URLs from http:// to https:// where the destination supports it.
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
critical
Security
Sensitive file probes
0/16A small allowlist probe returned a public success response.
Failed: earned 0 of 16 points.
Priority: Priority 1: fix before sharing the page publicly.
Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
fail
medium
Accessibility
Basic contrast
0/81 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.28.
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (74), region (5).
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
medium
Design
Text density
0/10Detected about 2391 visible word(s).
Failed: earned 0 of 10 points.
Priority: Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 3338ms. Load complete: 3725ms. First contentful paint: 668ms. Resources: 209. Scripts: 18. Images: 3. Third-party origins: 76. Transfer: not available.
Failed: earned 0 of 10 points.
Priority: Priority 14: fix during launch polish.
Why it matters: Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Fix: Reduce render-blocking scripts/styles, compress and size images, defer non-critical JavaScript, reduce third-party tags, and keep above-the-fold content quick to paint.
fail
low
Design
Runtime console health
0/7Detected 2 console error(s) and 0 uncaught page error(s) during render.
Failed: earned 0 of 7 points.
Priority: Priority 15: fix during launch polish.
Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
fail
medium
Design
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 166.
Failed: earned 0 of 9 points.
Priority: Priority 13: fix during launch polish.
Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Fix: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
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 2003 captured header(s)Checked: https://nicklaunches.com
Next/final: https://nicklaunches.com
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2002 captured header(s)Checked: https://nicklaunches.com
Next/final: https://nicklaunches.com
Content type: text/html; charset=utf-8
Content hash: bad294d428323a46bf8419f4aeb9553f7d4240c5e10f197a8542f813a8af070e
robots.txt
Step 3HTTP 2003 captured header(s)Checked: https://nicklaunches.com/robots.txt
Next/final: https://nicklaunches.com/robots.txt
Content type: text/plain; charset=utf-8
Content hash: f1b8b02b79ff78479fdd0fed2fe007df15634538b0316327a24f3d04cd57eb4c
sitemap.xml
Step 4HTTP 2002 captured header(s)Checked: https://nicklaunches.com/sitemap.xml
Next/final: https://nicklaunches.com/sitemap.xml
Content type: application/xml
Content hash: e80e0d70864c0df43b1fb136ff6c9cdbc720e7f19c81587dbad071273c99004f
llms.txt
Step 5HTTP 2002 captured header(s)Checked: https://nicklaunches.com/llms.txt
Next/final: https://nicklaunches.com/llms.txt
Content type: text/plain; charset=utf-8
Content hash: df723273eb27e545efcb4db7b340d6afc25c48bb910aff18526ac3f2187bcd46
Security probe
Step 6HTTP 4042 captured header(s)Checked: https://nicklaunches.com/.env
Next/final: https://nicklaunches.com/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 3082 captured header(s)Checked: https://nicklaunches.com/.git/config
Next/final: https://nicklaunches.com/.git/config
Content type: text/html
Content hash: c7444bcc63fee501ed5c88d939f9f5a5c2d2404bd960cf8423b034eb40a96a5a
Security probe
Step 8HTTP 4031 captured header(s)Checked: https://nicklaunches.com/wp-config.php
Next/final: https://nicklaunches.com/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://nicklaunches.com/backup.zip
Next/final: https://nicklaunches.com/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
content-length
719283
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
nicklaunches.com website audit report
Close to ready: 71/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 nicklaunches.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.