Speed Insights
Grade A
97% performance
https://nonna.digital
LCP
700ms
Largest paint
TBT
99ms
Blocking time
CLS
0.000
Layout shift
78
out of 100
84
out of 100
93/111 rule points
82
out of 100
62/76 rule points
61
out of 100
57/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Fix rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 4 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), heading-order (1), landmark-one-main (1), region (35).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
No complex menus or confusing buttons. Just tap your loved one's photo to start a video call instantly.
High-quality video calls that work perfectly even on slower internet connections.
Connect up to 20 family members in a secure, private network designed for your family.
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Fix Prompt
Write a clear page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 75 characters.
Priority
Priority 8: fix during launch polish.
Fix Prompt
Use one clear H1 and ordered headings
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 20 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Fix heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 4, 4, 4.
Priority
Priority 13: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 75 characters. Failed: earned 0 of 10 points.
Priority
Priority 8: fix during launch polish.
Fix Prompt
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 20 total headings. Failed: earned 0 of 8 points.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 4 of 18 points from partial coverage.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2, 4, 4, 4. Failed: earned 0 of 11 points.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Basic contrast
Why this needs attention
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Low contrast makes a launch page feel less polished and can exclude users with low vision.
Recommended correction
Evidence
23 of 76 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.47. Failed: earned 0 of 8 points.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
simple & loving
1K+
1-Tap
Shown for your region. Final billing and taxes are handled in the app store.
Fix Prompt
Rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 4 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (14), heading-order (1), landmark-one-main (1), region (35). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
No complex menus or confusing buttons. Just tap your loved one's photo to start a video call instantly.
High-quality video calls that work perfectly even on slower internet connections.
Connect up to 20 family members in a secure, private network designed for your family.
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Fix Prompt
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 615ms. Load complete: 0ms. First contentful paint: 500ms. Resources: 45. Scripts: 8. Images: 0. Third-party origins: 30. Transfer: not available. Failed: earned 0 of 10 points.
Priority
Priority 14: fix during launch polish.
Fix Prompt
Rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. Small tap targets: 32. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Affected elements
Features
How it Works
Pricing
Featured on IndieHunt
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
The exact URL appears in the fetched sitemap with lastmod 2026-08-05T09:39:07.686Z.
Structured data
Semantic schema score 90/100. Detected 1 JSON-LD block(s), 0 parse error(s), 4 graph node(s), and types ImageObject, Organization, SoftwareApplication, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 76/100 for “Video calls madesimple & lovingfor Nonna!”. Title/H1 token overlap is 20%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 80/100 from 250 main-content words, 2 concise answer block(s), 0 question heading(s), 3 definition(s), 2 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected home page role.
Published or updated date
Freshness metadata is contextual for the detected home page role.
Supporting-source links
Supporting sources are contextual for the detected home page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 76 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://nonna.digital/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
GPTBotModel training
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ClaudeBotModel training
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
Google-ExtendedData-use policy control
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
BingbotSearch and discovery
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 99% parity
PerplexityBotAI search
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 99% parity
Applebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
meta-externalagentModel training
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
AmazonbotModel training
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 8
Probe: reachable · HTTP 200 · 100% parity
CCBotModel training
Robots: allowed by * allow: / · line 8
Probe: not tested for this control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
The image refreshes from FreeScan after a completed rescan. Clicking it always opens the newest public report saved for this exact scanned URL.
Scan evidence is included as untrusted data. The implementation brief instructs agents to verify findings before editing and to avoid destructive or speculative changes.
