Loading scan status...
completed
HTTP 200
0 redirects
36 checks
Website audit scorecard for atsynct.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://atsynct.com
Final URL
https://atsynct.com
Created
Jun 29, 2026, 7:51 PM
Safe fetch
325 ms
Four-score result
Needs fixes before launch (Needs focused fixes): 22 passed, 14 failed, and 0 unknown. Strongest area: Security. Weakest area: Design.
Overall
65
out of 100
SEO / AEO
74
out of 100
68/92 rule points
Security
82
out of 100
62/76 rule points
Accessibility
78
out of 100
73/94 rule points
Design
25
out of 100
28/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 / AEO68/92
Security62/76
Accessibility73/94
Design28/110
Biggest score-losing checks
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
Design
Visible primary CTADetected 0 CTA candidate(s).
high
Design
Hero clarity signalsDetected 0 H1 heading(s) and 182 meta-description characters.
medium
Accessibility
Heading orderHeading levels found: none.
Recommendations
Score-losing issues ordered by remediation priority, severity, and score impact.
5 fixes
7 opportunities
9 insights
1
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.
2
fail
high
SEO / AEO
Priority 3
Add a useful meta description
-10 rule ptsWhat failed
The page does not expose a strong short summary for search and answer engines.
Evidence
Meta description is 182 characters.
Priority
Priority 3: fix before sharing the page publicly.
Why it matters
A missing description makes previews weaker when early users share or find the page.
How to fix it
Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
3
fail
high
Design
Priority 4
Make the primary CTA obvious
-14 rule ptsWhat failed
The page does not have a detectable call to action.
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: fix before sharing the page publicly.
Why it matters
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
How to fix it
Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
4
fail
high
Design
Priority 6
Clarify the hero promise
-13 rule ptsWhat failed
The hero area does not provide enough clear product context.
Evidence
Detected 0 H1 heading(s) and 182 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.
5
fail
medium
SEO / AEO
Priority 9
Use one clear H1 and ordered headings
-8 rule ptsWhat failed
The page heading structure is either missing a single main heading or skips heading levels.
Evidence
Detected 0 H1 heading(s) and 0 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.
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.
74/100
8 pass, 3 fail, 0 unknown
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
high
Meta description
-10 rule ptsMeta description is 182 characters.
medium
Heading structure
-8 rule ptsDetected 0 H1 heading(s) and 0 total headings.
medium
Internal link basics
-6 rule ptsDetected 0 internal link(s).
82/100
5 pass, 1 fail, 0 unknown
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
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.
78/100
6 pass, 2 fail, 0 unknown
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
medium
Heading order
-11 rule ptsHeading levels found: none.
medium
Landmark presence
-10 rule ptsDetected 1 landmark element(s) or roles.
25/100
3 pass, 8 fail, 0 unknown
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
high
Visible primary CTA
-14 rule ptsDetected 0 CTA candidate(s).
high
Hero clarity signals
-13 rule ptsDetected 0 H1 heading(s) and 182 meta-description characters.
medium
Text density
-10 rule ptsDetected about 10 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
high
SEO / AEO
Meta description
0/10Meta description is 182 characters.
Failed: earned 0 of 10 points.
Priority: Priority 3: fix before sharing the page publicly.
Why it matters: A missing description makes previews weaker when early users share or find the page.
Fix: Add a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
fail
medium
SEO / AEO
Heading structure
0/8Detected 0 H1 heading(s) and 0 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.
fail
medium
SEO / AEO
Internal link basics
0/6Detected 0 internal link(s).
Failed: earned 0 of 6 points.
Priority: Priority 16: lower-risk cleanup after urgent launch blockers.
Why it matters: Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Fix: Add clear public links such as pricing, docs, contact, privacy, terms, or product detail pages where appropriate.
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
medium
Accessibility
Heading order
0/11Heading levels found: none.
Failed: earned 0 of 11 points.
Priority: Priority 13: fix during launch polish.
Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Fix: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
fail
medium
Accessibility
Landmark presence
0/10Detected 1 landmark element(s) or roles.
Failed: earned 0 of 10 points.
Priority: Priority 18: lower-risk cleanup after urgent launch blockers.
Why it matters: Landmarks make the page easier to navigate for assistive technology and keyboard users.
Fix: Use semantic elements such as header, nav, main, and footer around the appropriate page areas.
fail
high
Design
Visible primary CTA
0/14Detected 0 CTA candidate(s).
Failed: earned 0 of 14 points.
Priority: Priority 4: fix before sharing the page publicly.
Why it matters: Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Fix: Add one prominent CTA above the fold with action-oriented text such as Start, Join, Try, Book, or Get started.
fail
high
Design
Hero clarity signals
0/13Detected 0 H1 heading(s) and 182 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.
fail
medium
Design
Text density
0/10Detected about 10 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 2 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.
fail
medium
Design
Visual hierarchy
0/9Detected 0 hierarchy signal(s) from headings, CTA, and emphasized text.
Failed: earned 0 of 9 points.
Priority: Priority 12: fix during launch polish.
Why it matters: Hierarchy tells visitors what to read first and what action to take next.
Fix: Create a clear H1, supportive section headings, emphasized proof, and one visually prominent primary CTA.
fail
medium
Design
Rendered speed signals
0/10DOMContentLoaded: 415ms. Load complete: 731ms. First contentful paint: 524ms. Resources: 41. Scripts: 24. Images: 3. Third-party origins: 2. 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
medium
Design
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 7.
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 2002 captured header(s)Checked: https://atsynct.com
Next/final: https://atsynct.com
Content type: text/html; charset=utf-8
Landing page
Step 2HTTP 2002 captured header(s)Checked: https://atsynct.com
Next/final: https://atsynct.com
Content type: text/html; charset=utf-8
Content hash: aefc5250620f2bb6deeb08f71581db1389e3c9feeb93385d2ac46ddc653062a8
robots.txt
Step 3HTTP 2003 captured header(s)Checked: https://atsynct.com/robots.txt
Next/final: https://atsynct.com/robots.txt
Content type: text/plain; charset=utf-8
Content hash: 270d584883477478bc54841594a5ff01678208551ab18f57a8f2cb26f3b1d72c
sitemap.xml
Step 4HTTP 2002 captured header(s)Checked: https://atsynct.com/sitemap.xml
Next/final: https://atsynct.com/sitemap.xml
Content type: application/xml
Content hash: c5e2f94499e0471db9cedd75fe4e1f5d8cbf92850afc1cb657d5398c6b660bc5
llms.txt
Step 5HTTP 2002 captured header(s)Checked: https://atsynct.com/llms.txt
Next/final: https://atsynct.com/llms.txt
Content type: text/plain; charset=utf-8
Content hash: d42e35c0389c59bd1f04599ec814244938fe3239446a0929bf4445185762f540
Security probe
Step 6HTTP 4042 captured header(s)Checked: https://atsynct.com/.env
Next/final: https://atsynct.com/.env
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 7HTTP 4042 captured header(s)Checked: https://atsynct.com/.git/config
Next/final: https://atsynct.com/.git/config
Content type: text/html; charset=utf-8
Fetch result: HTTP 404 returned for security_probe.
Security probe
Step 8HTTP 4031 captured header(s)Checked: https://atsynct.com/wp-config.php
Next/final: https://atsynct.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://atsynct.com/backup.zip
Next/final: https://atsynct.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
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
atsynct.com website audit report
Needs fixes before launch: 65/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 atsynct.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.