Speed Insights
Grade N/A
Not captured
https://wpmultitool.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
94
out of 100
100
out of 100
92/92 rule points
92
out of 100
70/76 rule points
100
out of 100
94/94 rule points
85
out of 100
94/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 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
Priority
Priority 5: fix before sharing the page publicly.
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: 56.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Fix runtime browser errors
Why 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 8 console error(s) and 0 uncaught page error(s) during render.
Priority
Priority 15: fix during launch polish.
Fix 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.
No failed checks in this category.
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.
No failed checks in this category.
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.
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 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy. Failed: earned 12 of 18 points from partial coverage.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Runtime console health
Why 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 8 console error(s) and 0 uncaught page error(s) during render. Failed: earned 0 of 7 points.
Priority
Priority 15: 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: 56. Failed: earned 0 of 9 points.
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.
