The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://prismclassroom.com
Final URL
https://www.prismclassroom.com
Created
Jul 3, 2026, 6:59 AM
Safe fetch
111 ms
78
out of 100
87
out of 100
80/92 rule points
82
out of 100
62/76 rule points
79
out of 100
54/68 rule points
64
out of 100
54/84 rule points
Category point breakdown
Biggest score-losing checks
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.
Detected labels or accessible names for 40 of 44 form control(s).
Detected 3 H1 heading(s) and 116 meta-description characters.
Detected 0 trust-signal keyword occurrence(s).
What 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.
What failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 40 of 44 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
What failed
The hero area does not provide enough clear product context.
Evidence
Detected 3 H1 heading(s) and 116 meta-description characters.
Priority
Priority 6: fix during launch polish.
Why it matters
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
How to fix it
Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
What failed
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 3 H1 heading(s) and 63 total headings.
Priority
Priority 9: fix during launch polish.
Why it matters
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
How to fix it
Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
What failed
The page does not expose detectable proof, customer, review, security, or credibility signals.
Evidence
Detected 0 trust-signal keyword occurrence(s).
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters
Trust signals reduce hesitation when strangers see the product for the first time.
How to fix it
Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
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.
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
Detected 3 H1 heading(s) and 63 total headings.
HTTP 404 returned for llms_txt.
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
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.
Severity mix: 0 critical, 2 high, 4 medium, 0 low.
Detected labels or accessible names for 40 of 44 form control(s).
Severity mix: 0 critical, 3 high, 4 medium, 1 low.
Detected 3 H1 heading(s) and 116 meta-description characters.
Detected 0 trust-signal keyword occurrence(s).
Detected 0 spacing class/style signal(s).
Showing failed checks.
These checks need attention.
Detected 3 H1 heading(s) and 63 total headings.
Failed: earned 0 of 8 points.
Priority: Priority 9: fix during launch polish.
Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Fix: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
HTTP 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.
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.
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.
Detected labels or accessible names for 40 of 44 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Detected 3 H1 heading(s) and 116 meta-description characters.
Failed: earned 0 of 13 points.
Priority: Priority 6: fix during launch polish.
Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Fix: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
Detected 0 trust-signal keyword occurrence(s).
Failed: earned 0 of 10 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
Fix: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
Detected 0 spacing class/style signal(s).
Failed: earned 0 of 7 points.
Priority: Priority 25: lower-risk cleanup after urgent launch blockers.
Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
Fix: Use consistent section padding, gaps, and margins across repeated content blocks.
Security and accessibility checks are basic automated public checks. They are not a complete security audit, penetration test, privacy review, or WCAG certification.
Checked: https://prismclassroom.com
Next/final: https://www.prismclassroom.com/
Content type: text/html
Checked: https://www.prismclassroom.com
Next/final: https://www.prismclassroom.com
Content type: text/html; charset=utf-8
Checked: https://www.prismclassroom.com
Next/final: https://www.prismclassroom.com
Content type: text/html; charset=utf-8
Content hash: b5745354cb2a2271fbc92610e7f9039664d22c9e49e8c890233744748dae7d95
Checked: https://www.prismclassroom.com/robots.txt
Next/final: https://www.prismclassroom.com/robots.txt
Content type: text/plain; charset=utf-8
Content hash: 899321a8ec5dcb8d836ad92c24853bb7e80c1522b359546efc53664c58b8d4d6
Checked: https://www.prismclassroom.com/sitemap.xml
Next/final: https://www.prismclassroom.com/sitemap.xml
Content type: application/xml
Content hash: 39c9fe2f6bb880f4b4574390969a2976534dcc4d7d1e4f1e660095829d36150d
Checked: https://www.prismclassroom.com/llms.txt
Next/final: https://www.prismclassroom.com/llms.txt
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for llms_txt.
Checked: https://www.prismclassroom.com/.env
Next/final: https://www.prismclassroom.com/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://www.prismclassroom.com/.git/config
Next/final: https://www.prismclassroom.com/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Checked: https://www.prismclassroom.com/wp-config.php
Next/final: https://www.prismclassroom.com/wp-config.php
Content type: text/html; charset=utf-8
Fetch result: HTTP 403 returned for security_probe.
Checked: https://www.prismclassroom.com/backup.zip
Next/final: https://www.prismclassroom.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
strict-transport-security
max-age=63072000
Share preview
prismclassroom.com website audit report
Close to ready: 78/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.