Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://daniellaunches.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
76
out of 100
91
out of 100
96/106 rule points
66
out of 100
50/76 rule points
72
out of 100
68/94 rule points
74
out of 100
81/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 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.
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), region (6).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Remove insecure page resources
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 4 insecure asset or link reference(s).
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Add basic structured data
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
Fix Prompt
Fix 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: 52.
Priority
Priority 13: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 2 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, 6 high, 3 medium, 2 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.
Schema presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Mixed content indicators
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 4 insecure asset or link reference(s). Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
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 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.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
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
17 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (16), region (6). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Trust signals
Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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: 2307ms. Load complete: 2308ms. First contentful paint: 532ms. Resources: 84. Scripts: 21. Images: 15. Third-party origins: 17. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)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: 52. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
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.
