Loading scan status...
completed
HTTP 200
1 redirects
31 checks
Website audit scorecard for prismclassroom.com
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, 11:56 AM
Safe fetch
386 ms
Four-score result
Close to ready (Strong): 26 passed, 5 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Design.
Overall
85
out of 100
SEO / AEO
100
out of 100
92/92 rule points
Security
92
out of 100
70/76 rule points
Accessibility
79
out of 100
54/68 rule points
Design
68
out of 100
57/84 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
Security70/76
Accessibility54/68
Design57/84
Biggest score-losing checks
high
Accessibility
Form labelsDetected labels or accessible names for 42 of 44 form control(s).
medium
Design
Text densityDetected about 1858 visible word(s).
medium
Design
Trust signalsDetected 0 trust-signal keyword occurrence(s).
low
Design
Spacing consistencyDetected 0 spacing class/style signal(s).
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
5 opportunities
6 insights
1
fail
high
Accessibility
Priority 7
Label public form fields
-14 rule ptsWhat failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 42 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.
2
fail
high
Security
Priority 5
Add common public security headers
-6 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-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
medium
Design
Priority 16
Add trust signals
-10 rule ptsWhat 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.
4
fail
medium
Design
Priority 21
Balance landing page copy
-10 rule ptsWhat failed
The page has too little or too much detectable text for a useful launch page.
Evidence
Detected about 1858 visible word(s).
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.
How to fix it
Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
5
fail
low
Design
Priority 25
Make spacing more consistent
-7 rule ptsWhat failed
The page exposes few consistent spacing signals in class or inline styles.
Evidence
Detected 0 spacing class/style signal(s).
Priority
Priority 25: lower-risk cleanup after urgent launch blockers.
Why it matters
Consistent spacing helps the page feel deliberate and easier to scan.
How to fix it
Use consistent section padding, gaps, and margins across repeated content blocks.
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.
92/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-6 rule ptsDetected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
79/100
5 pass, 1 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 2 high, 4 medium, 0 low.
high
Form labels
-14 rule ptsDetected labels or accessible names for 42 of 44 form control(s).
68/100
5 pass, 3 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 4 medium, 1 low.
medium
Text density
-10 rule ptsDetected about 1858 visible word(s).
medium
Trust signals
-10 rule ptsDetected 0 trust-signal keyword occurrence(s).
low
Spacing consistency
-7 rule ptsDetected 0 spacing class/style signal(s).
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
Common security headers
12/18Detected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
Failed: earned 12 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
high
Accessibility
Form labels
0/14Detected labels or accessible names for 42 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.
fail
medium
Design
Text density
0/10Detected about 1858 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
Trust signals
0/10Detected 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.
fail
low
Design
Spacing consistency
0/7Detected 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.
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.
Redirect
Step 1HTTP 3072 captured header(s)Checked: https://prismclassroom.com
Next/final: https://www.prismclassroom.com/
Content type: text/html
Landing page
Step 2HTTP 2005 captured header(s)Checked: https://www.prismclassroom.com
Next/final: https://www.prismclassroom.com
Content type: text/html; charset=utf-8
Landing page
Step 3HTTP 2005 captured header(s)Checked: https://www.prismclassroom.com
Next/final: https://www.prismclassroom.com
Content type: text/html; charset=utf-8
Content hash: 2416a44ef20adcac8adcea66a56236e5acabd5fdb780bf097864025234427c46
robots.txt
Step 4HTTP 2006 captured header(s)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
sitemap.xml
Step 5HTTP 2006 captured header(s)Checked: https://www.prismclassroom.com/sitemap.xml
Next/final: https://www.prismclassroom.com/sitemap.xml
Content type: application/xml
Content hash: 1e2081c954f2855775c8c2bd96d93e16b319eac4690611a78c703302905ca19a
llms.txt
Step 6HTTP 2006 captured header(s)Checked: https://www.prismclassroom.com/llms.txt
Next/final: https://www.prismclassroom.com/llms.txt
Content type: text/plain; charset=utf-8
Content hash: 97ea473a9bd70c736378c926575894fe0e4698cbd89ef97e1727fae75dda5586
Security probe
Step 7HTTP 4045 captured header(s)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.
Security probe
Step 8HTTP 4045 captured header(s)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.
Security probe
Step 9HTTP 4031 captured header(s)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.
Security probe
Step 10HTTP 4045 captured header(s)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
referrer-policy
strict-origin-when-cross-origin
x-frame-options
SAMEORIGIN
x-content-type-options
nosniff
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
prismclassroom.com website audit report
Close to ready: 85/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 prismclassroom.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.