Website audit scorecard for chrisallard.ca
The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.
Submitted
https://www.chrisallard.ca/
Final URL
https://www.chrisallard.ca
Created
Jul 8, 2026, 6:43 PM
Safe fetch
61 ms
67
out of 100
89
out of 100
102/114 rule points
76
out of 100
58/76 rule points
32
out of 100
30/94 rule points
70
out of 100
77/110 rule points
Category point breakdown
Biggest score-losing checks
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
axe found 8 violation rule(s), including 5 serious or critical rule(s). Top rules: image-alt (2), color-contrast (17), link-in-text-block (4), link-name (6), list (1).
Detected 8 image(s) missing alt text out of 132.
Detected labels or accessible names for 19 of 40 form control(s).
Add common public security headers
-18 rule ptsWhat failed
Several basic browser protection headers were not visible.
Evidence
Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-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.
Copyable agent prompt
Fix rendered axe accessibility violations
-18 rule ptsWhat failed
The rendered page has accessibility rule violations detected by axe-core.
Evidence
axe found 8 violation rule(s), including 5 serious or critical rule(s). Top rules: image-alt (2), color-contrast (17), link-in-text-block (4), link-name (6), list (1).
Priority
Priority 5: fix before sharing the page publicly.
Why it matters
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
How to fix it
Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Copyable agent prompt
Label public form fields
-14 rule ptsWhat failed
Some form controls do not have a detectable label or accessible name.
Evidence
Detected labels or accessible names for 19 of 40 form control(s).
Priority
Priority 7: fix during launch polish.
Why it matters
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
How to fix it
Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Publish a valid sitemap.xml
-12 rule ptsWhat failed
The sitemap file was not reachable or did not look like valid sitemap XML.
Evidence
sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Why it matters
A sitemap helps search engines discover the landing page and related public pages sooner.
How to fix it
Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
Add meaningful image alt text
-14 rule ptsWhat failed
One or more images are missing alt text.
Evidence
Detected 8 image(s) missing alt text out of 132.
Priority
Priority 11: fix during launch polish.
Why it matters
People using screen readers may miss product context, trust signals, or calls to action.
How to fix it
Add concise alt text for informative images and use empty alt text only for decorative images.
Copyable agent prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
sitemap.xml validity
-12 rule ptssitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Common security headers
-18 rule ptsDetected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Rendered axe accessibility violations
-18 rule ptsaxe found 8 violation rule(s), including 5 serious or critical rule(s). Top rules: image-alt (2), color-contrast (17), link-in-text-block (4), link-name (6), list (1).
Image alt text
-14 rule ptsDetected 8 image(s) missing alt text out of 132.
Form labels
-14 rule ptsDetected labels or accessible names for 19 of 40 form control(s).
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Text density
-10 rule ptsDetected about 1865 visible word(s).
Rendered layout ergonomics
-9 rule ptsHorizontal overflow: 0px. Small tap targets: 42.
Spacing consistency
-7 rule ptsDetected 2 spacing class/style signal(s).
Showing failed checks.
Failed checks
These checks need attention.
sitemap.xml validity
0/12sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Failed: earned 0 of 12 points.
Priority: Priority 7: fix during launch polish.
Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.
Copyable agent prompt
Common security headers
0/18Detected 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Failed: earned 0 of 18 points.
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.
Copyable agent prompt
Image alt text
0/14Detected 8 image(s) missing alt text out of 132.
Failed: earned 0 of 14 points.
Priority: Priority 11: fix during launch polish.
Why it matters: People using screen readers may miss product context, trust signals, or calls to action.
Fix: Add concise alt text for informative images and use empty alt text only for decorative images.
Copyable agent prompt
Form labels
0/14Detected labels or accessible names for 19 of 40 form control(s).
Failed: earned 0 of 14 points.
Priority: Priority 7: fix during launch polish.
Why it matters: Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Fix: Connect each input to a visible label or an accurate aria-label/aria-labelledby value.
Copyable agent prompt
Semantic buttons and links
0/10Detected 0 semantic control(s) out of 1.
Failed: earned 0 of 10 points.
Priority: Priority 17: lower-risk cleanup after urgent launch blockers.
Why it matters: Non-semantic controls can be hard to use with keyboards and screen readers.
Fix: Use button for actions and anchor links for navigation, with clear accessible names.
Copyable agent prompt
Basic contrast
0/825 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.
Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
Copyable agent prompt
Rendered axe accessibility violations
0/18axe found 8 violation rule(s), including 5 serious or critical rule(s). Top rules: image-alt (2), color-contrast (17), link-in-text-block (4), link-name (6), list (1).
Failed: earned 0 of 18 points.
Priority: Priority 5: fix before sharing the page publicly.
Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Fix: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
Copyable agent prompt
Text density
0/10Detected about 1865 visible word(s).
Failed: earned 0 of 10 points.
Priority: Priority 21: lower-risk cleanup after urgent launch blockers.
Why it matters: Too little copy can leave visitors confused; too much copy can bury the value proposition.
Fix: Add concise sections for value, proof, how it works, and next steps, then remove repetitive copy.
Copyable agent prompt
Spacing consistency
0/7Detected 2 spacing class/style signal(s).
Failed: earned 0 of 7 points.
Priority: Priority 25: lower-risk cleanup after urgent launch blockers.
Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
Fix: Use consistent section padding, gaps, and margins across repeated content blocks.
Copyable agent prompt
Runtime console health
0/7Detected 3 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.
Copyable agent prompt
Rendered layout ergonomics
0/9Horizontal overflow: 0px. Small tap targets: 42.
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.
Copyable agent prompt
Share preview
chrisallard.ca website audit report
Needs fixes before launch: 67/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.