Loading scan status...
completed
HTTP 200
0 redirects
31 checks
Website audit scorecard for drsagnikmukherjee.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://drsagnikmukherjee.com/
Final URL
https://drsagnikmukherjee.com
Created
Jul 2, 2026, 12:43 PM
Safe fetch
3638 ms
Four-score result
Close to ready (Needs polish): 25 passed, 6 failed, and 0 unknown. Strongest area: Design. Weakest area: Accessibility.
Overall
79
out of 100
SEO / AEO
85
out of 100
78/92 rule points
Security
76
out of 100
58/76 rule points
Accessibility
65
out of 100
44/68 rule points
Design
88
out of 100
74/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 / AEO78/92
Security58/76
Accessibility44/68
Design74/84
Biggest score-losing checks
high
Security
Common security headersDetected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
high
Accessibility
Form labelsDetected labels or accessible names for 16 of 19 form control(s).
high
SEO / AEO
Schema presenceDetected 0 JSON-LD schema block(s).
medium
Accessibility
Semantic buttons and linksDetected 3 semantic control(s) out of 8.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
4 opportunities
6 insights
1
fail
high
Security
Priority 5
Add common public security headers
-18 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, 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 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 16 of 19 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.
3
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.
4
fail
medium
Accessibility
Priority 17
Use semantic buttons and links
-10 rule ptsWhat failed
Interactive controls are not consistently represented as semantic buttons or links.
Evidence
Detected 3 semantic control(s) out of 8.
Priority
Priority 17: lower-risk cleanup after urgent launch blockers.
Why it matters
Non-semantic controls can be hard to use with keyboards and screen readers.
How to fix it
Use button for actions and anchor links for navigation, with clear accessible names.
5
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 2889 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.
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.
85/100
9 pass, 2 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
high
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
low
LLM-readable file
-4 rule ptsHTTP 404 returned for llms_txt.
76/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
high
Common security headers
-18 rule ptsDetected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
65/100
4 pass, 2 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 16 of 19 form control(s).
medium
Semantic buttons and links
-10 rule ptsDetected 3 semantic control(s) out of 8.
88/100
7 pass, 1 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 4 medium, 1 low.
medium
Text density
-10 rule ptsDetected about 2889 visible word(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
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
0/18Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 0 of 18 points.
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 16 of 19 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
Accessibility
Semantic buttons and links
0/10Detected 3 semantic control(s) out of 8.
Failed: earned 0 of 10 points.
Priority: Priority 17: lower-risk cleanup after urgent launch blockers.
Why it matters: Non-semantic controls can be hard to use with keyboards and screen readers.
Fix: Use button for actions and anchor links for navigation, with clear accessible names.
fail
medium
Design
Text density
0/10Detected about 2889 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.
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 2001 captured header(s)Checked: https://drsagnikmukherjee.com
Next/final: https://drsagnikmukherjee.com
Content type: text/html; charset=UTF-8
Landing page
Step 2HTTP 2001 captured header(s)Checked: https://drsagnikmukherjee.com
Next/final: https://drsagnikmukherjee.com
Content type: text/html; charset=UTF-8
Content hash: 799f17c533fcfdf4e3d75e97796d0e2736a29f60d1f35d58dc9a3d2e2261ee12
robots.txt
Step 3HTTP 2001 captured header(s)Checked: https://drsagnikmukherjee.com/robots.txt
Next/final: https://drsagnikmukherjee.com/robots.txt
Content type: text/plain; charset=utf8mb4
Content hash: 121292db6ed99afdb4bc6e1de7e519b00e47011e9b27b95f74fe0f5c139da7dc
sitemap.xml
Step 4HTTP 3012 captured header(s)Checked: https://drsagnikmukherjee.com/sitemap.xml
Next/final: https://drsagnikmukherjee.com/sitemap.xml
Content type: text/html; charset=UTF-8
llms.txt
Step 5HTTP 4041 captured header(s)Checked: https://drsagnikmukherjee.com/llms.txt
Next/final: https://drsagnikmukherjee.com/llms.txt
Content type: text/html; charset=UTF-8
Fetch result: HTTP 404 returned for llms_txt.
Security probe
Step 6HTTP 4031 captured header(s)Checked: https://drsagnikmukherjee.com/.env
Next/final: https://drsagnikmukherjee.com/.env
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 7HTTP 4031 captured header(s)Checked: https://drsagnikmukherjee.com/.git/config
Next/final: https://drsagnikmukherjee.com/.git/config
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 8HTTP 4031 captured header(s)Checked: https://drsagnikmukherjee.com/wp-config.php
Next/final: https://drsagnikmukherjee.com/wp-config.php
Content type: text/html
Fetch result: HTTP 403 returned for security_probe.
Security probe
Step 9HTTP 4041 captured header(s)Checked: https://drsagnikmukherjee.com/backup.zip
Next/final: https://drsagnikmukherjee.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
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
drsagnikmukherjee.com website audit report
Close to ready: 79/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 drsagnikmukherjee.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.