Website audit scorecard for notefy.pro
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
notefy.pro
Final URL
https://notefy.pro
Created
Jul 26, 2026, 8:37 PM
Safe fetch
428 ms
71
out of 100
79
out of 100
84/106 rule points
55
out of 100
42/76 rule points
66
out of 100
62/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
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.
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: image-alt (1), color-contrast (3), landmark-one-main (1), meta-viewport (1), region (76).
A small allowlist probe returned a public success response.
Detected 1 image(s) missing alt text out of 15.
Remove exposed sensitive files
-16 rule 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.
Copyable agent prompt
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.
Copyable agent prompt
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: image-alt (1), color-contrast (3), landmark-one-main (1), meta-viewport (1), region (76).
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.
Copyable agent prompt
Publish a valid sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable or did not look like valid sitemap XML.
Evidence
sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
Add meaningful image alt text
-14 rule ptsWhat failed
One or more images are missing alt text.
Evidence
Detected 1 image(s) missing alt text out of 15.
Priority
Priority 11: fix during launch polish.
Why it matters
People using screen readers may miss product context, trust signals, or calls to action.
How to fix it
Add concise alt text for informative images and use empty alt text only for decorative images.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 2 low.
sitemap.xml validity
-12 rule ptssitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Schema presence
-10 rule ptsDetected 0 JSON-LD schema block(s).
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Sensitive file probes
-16 rule ptsA small allowlist probe returned a public success response.
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.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: image-alt (1), color-contrast (3), landmark-one-main (1), meta-viewport (1), region (76).
Image alt text
-14 rule ptsDetected 1 image(s) missing alt text out of 15.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Rendered speed signals
-10 rule ptsDOMContentLoaded: 1654ms. Load complete: 1655ms. First contentful paint: 1208ms. Resources: 27. Scripts: 10. Images: 11. Third-party origins: 14. Transfer: not available.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 35px. Small tap targets: 8.
Showing failed checks.
Failed checks
These checks need attention.
sitemap.xml validity
0/12sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
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.
Copyable agent prompt
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.
Copyable agent prompt
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.
Copyable agent prompt
Image alt text
0/14Detected 1 image(s) missing alt text out of 15.
Failed: earned 0 of 14 points.
Priority: Priority 11: fix during launch polish.
Why it matters: People using screen readers may miss product context, trust signals, or calls to action.
Fix: Add concise alt text for informative images and use empty alt text only for decorative images.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 5 violation rule(s), including 2 serious or critical rule(s). Top rules: image-alt (1), color-contrast (3), landmark-one-main (1), meta-viewport (1), region (76).
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.
Copyable agent prompt
Rendered speed signals
0/10DOMContentLoaded: 1654ms. Load complete: 1655ms. First contentful paint: 1208ms. Resources: 27. Scripts: 10. Images: 11. Third-party origins: 14. 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.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 35px. Small tap targets: 8.
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.
Copyable agent prompt
Share preview
notefy.pro website audit report
Close to ready: 71/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.