Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for promptjoy.app
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://promptjoy.app/
Final URL
https://promptjoy.app
Created
Jun 29, 2026, 3:45 AM
Safe fetch
157 ms
Four-score result
Close to ready (Needs polish): 31 passed, 5 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Accessibility.
Overall
84
out of 100
SEO / AEO
100
out of 100
82/82 rule points
Security
79
out of 100
60/76 rule points
Accessibility
72
out of 100
68/94 rule points
Design
85
out of 100
94/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 / AEO82/82
Security60/76
Accessibility68/94
Design94/110
Biggest score-losing checks
high
Accessibility
Rendered axe accessibility violationsaxe found 2 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5).
critical
Security
Sensitive file probesA small allowlist probe returned a public success response.
medium
Design
Rendered layout ergonomicsHorizontal overflow: 0px. Small tap targets: 18.
medium
Accessibility
Basic contrast4 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
7 opportunities
9 insights
1
critical
Security
Priority 1
Remove exposed sensitive files
-16 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
high
Accessibility
Priority 5
Fix rendered axe accessibility violations
-18 ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 2 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (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.
3
medium
Design
Priority 13
Fix rendered layout ergonomics
-9 ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 18.
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.
4
low
Design
Priority 15
Fix runtime browser errors
-7 ptsWhat failed
The rendered page produced console or uncaught JavaScript errors.
Evidence
Detected 1 console error(s) and 0 uncaught page error(s) during render.
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.
How to fix it
Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
5
medium
Accessibility
Priority 20
Improve detectable color contrast
-8 ptsWhat failed
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Evidence
4 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
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.
How to fix it
Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
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, 3 high, 6 medium, 2 low.
No failed checks in this category.
79/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
critical
Sensitive file probes
-16 ptsA small allowlist probe returned a public success response.
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 ptsaxe found 2 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (5).
medium
Basic contrast
-8 pts4 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
85/100
9 pass, 2 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
medium
Rendered layout ergonomics
-9 ptsHorizontal overflow: 0px. Small tap targets: 18.
low
Runtime console health
-7 ptsDetected 1 console error(s) and 0 uncaught page error(s) during render.
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
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/84 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 2 violation rule(s), including 2 serious or critical rule(s). Top rules: button-name (1), color-contrast (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
low
Design
Runtime console health
0/7Detected 1 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: 18.
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 2006 captured header(s)Checked: https://promptjoy.app
Next/final: https://promptjoy.app
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2006 captured header(s)Checked: https://promptjoy.app
Next/final: https://promptjoy.app
Content type: text/html; charset=utf-8
Content hash: dd5d6070be8880ec5cecc6f80787d7ada548dc103c81b3bd74732aa0d27dccee
robots.txt
Step 3HTTP 3076 captured header(s)Checked: https://promptjoy.app/robots.txt
Next/final: https://promptjoy.app/robots.txt
Content type: text/html
Content hash: af6ce320d3a273a4839d41ed852cf0110c344deaa92de4540fd2c5202a5ddb49
sitemap.xml
Step 4HTTP 3076 captured header(s)Checked: https://promptjoy.app/sitemap.xml
Next/final: https://promptjoy.app/sitemap.xml
Content type: text/html
Content hash: f420d397cab3b93102cece399cc07c73f9d59e2c0385f3f5bb9cf58422cb576d
llms.txt
Step 5HTTP 3076 captured header(s)Checked: https://promptjoy.app/llms.txt
Next/final: https://promptjoy.app/llms.txt
Content type: text/html
Content hash: faaa6116a2e7260662056144f8e985c3d80a9261fa5765224bf72029524f923d
Security probe
Step 6HTTP 3076 captured header(s)Checked: https://promptjoy.app/.env
Next/final: https://promptjoy.app/.env
Content type: text/html
Content hash: c043fa5286f7b2504cdf6bb3429a578eee583c5e604727d60ba7b53fedb33cfe
Security probe
Step 7HTTP 3076 captured header(s)Checked: https://promptjoy.app/.git/config
Next/final: https://promptjoy.app/.git/config
Content type: text/html
Content hash: 392ca49921e8b2cc60d073e6fe68283576ae751509e93a9c5decefe3bb87b413
Security probe
Step 8HTTP 3076 captured header(s)Checked: https://promptjoy.app/wp-config.php
Next/final: https://promptjoy.app/wp-config.php
Content type: text/html
Content hash: 47aa9d49afd0f55d70d1ee39ba4d9226534ccdbfb85435d9cd2cb695b669a4e6
Security probe
Step 9HTTP 3076 captured header(s)Checked: https://promptjoy.app/backup.zip
Next/final: https://promptjoy.app/backup.zip
Content type: text/html
Content hash: 97fa1b149c373734f29bfea8ec8f9c5f7013d4441e30236306cde209e0a8f863
Captured public headers
content-type
text/html; charset=utf-8
referrer-policy
strict-origin-when-cross-origin
permissions-policy
camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()
x-content-type-options
nosniff
content-security-policy
default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https: wss:; media-src 'self' data: blob: https:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' https://buildhop.io https://www.buildhop.io; upgrade-insecure-requests
strict-transport-security
max-age=63072000; includeSubDomains; preload
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
promptjoy.app website audit report
Close to ready: 84/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 promptjoy.app without re-entering the URL. The previous report stays saved so the next result can be compared against it.