Speed Insights
Grade N/A
Not captured
https://www.listbulb.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
73
out of 100
100
out of 100
92/92 rule points
66
out of 100
50/76 rule points
57
out of 100
54/94 rule points
67
out of 100
74/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
-14 rule ptsWhy 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.
Agent Prompt
Fix rendered axe accessibility violations
-18 rule ptsWhy 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 3 serious or critical rule(s). Top rules: aria-hidden-focus (4), color-contrast (3), link-in-text-block (1), region (2).
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Remove insecure page resources
-12 rule ptsWhy 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.
Agent Prompt
Label public form fields
-14 rule ptsWhy this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 3 of 4 form control(s).
Priority
Priority 7: fix during launch polish.
Agent Prompt
Fix rendered layout ergonomics
-9 rule ptsWhy 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: 112.
Priority
Priority 13: fix during launch polish.
Agent Prompt
SEO / AEO
Severity mix: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
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: 0 critical, 6 high, 3 medium, 2 low.
No failed checks in this category.
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.
Mixed content indicators
0/12Why 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.
Priority
Priority 4: fix before sharing the page publicly.
Agent Prompt
Common security headers
4/18Why 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.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Form labels
0/14Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 3 of 4 form control(s). Failed: earned 0 of 14 points.
Priority
Priority 7: fix during launch polish.
Agent Prompt
Basic contrast
0/8Why 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
11 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1. Failed: earned 0 of 8 points.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Rendered axe accessibility violations
0/18Why 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 3 serious or critical rule(s). Top rules: aria-hidden-focus (4), color-contrast (3), link-in-text-block (1), region (2). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Trust signals
0/10Why 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.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Rendered speed signals
0/10Why 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: 357ms. Load complete: 991ms. First contentful paint: 576ms. Resources: 89. Scripts: 18. Images: 62. Third-party origins: 60. Transfer: not available. Failed: earned 0 of 10 points.
Priority
Priority 14: fix during launch polish.
Agent Prompt
Runtime console health
0/7Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 1 console error(s) and 0 uncaught page error(s) during render. Failed: earned 0 of 7 points.
Priority
Priority 15: fix during launch polish.
Agent Prompt
Rendered layout ergonomics
0/9Why 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: 112. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Agent 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.
