Website audit scorecard for wpmultitool.com
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://wpmultitool.com/
Final URL
https://wpmultitool.com
Created
Jul 6, 2026, 2:30 PM
Safe fetch
426 ms
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
Horizontal overflow: 0px. Small tap targets: 56.
Detected 8 console error(s) and 0 uncaught page error(s) during render.
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.
Add common public security headers
-6 rule ptsWhat failed
Several basic browser protection headers were not visible.
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.
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.
Fix rendered layout ergonomics
-9 rule ptsWhat failed
The browser-rendered page has layout or tap-target issues.
Evidence
Horizontal overflow: 0px. Small tap targets: 56.
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.
How to fix it
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.
Fix runtime browser errors
-7 rule ptsWhat failed
The rendered page produced console or uncaught JavaScript errors.
Evidence
Detected 8 console error(s) and 0 uncaught page error(s) during render.
Priority
Priority 15: fix during launch polish.
Why it matters
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
How to fix it
Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
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.
Common security headers
-6 rule ptsDetected 4 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options, referrer-policy. Missing: content-security-policy.
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.
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 56.
Runtime console health
-7 rule ptsDetected 8 console error(s) and 0 uncaught page error(s) during render.
Showing failed checks.
Failed checks
These checks need attention.
Common security headers
12/18Detected 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.
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.
Runtime console health
0/7Detected 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.
Why it matters: Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Fix: Open the page in a browser, reproduce the console errors, and fix missing assets, hydration problems, client-side exceptions, or failing third-party scripts.
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 56.
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.
Share preview
wpmultitool.com website audit report
Ready to share: 94/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.