completed

HTTP 200

1 redirects

38 checks

witchesbrew.co Website Audit

Speed Insights

Grade A

98% performance

https://www.witchesbrew.co

From witchesbrew.co

LCP

736ms

Largest paint

TBT

55ms

Blocking time

CLS

0.002

Layout shift

Four-score result

Ready to share (Strong): 36 passed, 2 failed, and 0 unknown. Strongest area: SEO / AEO. Weakest area: Accessibility.

Overall

out of 100

SEO / AEO

100

out of 100

111/111 rule points

Security

100

out of 100

76/76 rule points

Accessibility

out of 100

76/94 rule points

Design

out of 100

101/110 rule points

Why this scored this way

Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.

Category point breakdown

SEO / AEO111/111

Security76/76

Accessibility76/94

Design101/110

Biggest score-losing checks

high

Accessibility

Rendered axe accessibility violations

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).

Affected elements

1 found

See the Menu

1.03:1 fail

Needs 4.5:1

Current colors

Pass 4.51:1

medium

Design

Rendered layout ergonomics

Horizontal overflow: 0px. Small tap targets: 19.

Affected elements

8 found

Small tap target

260x40px

Meet Godwin the Gargoyle ✦

Small tap target

264x40px

Browse the Tea Apothecary ✦

Small tap target

251x40px

Small tap target

251x40px

Tarot Readings

Recommendations

Score-losing issues ordered by remediation priority, severity, and score impact.

2 fixes

7 opportunities

9 insights

fail

high

Accessibility

Priority 5

Fix rendered axe accessibility violations

-18 rule pts

What failed

The rendered page has accessibility rule violations detected by axe-core.

Evidence

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).

Affected elements

1 found

See the Menu

1.03:1 fail

Needs 4.5:1

Current colors

Pass 4.51: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.

Agent Prompt

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve witchesbrew.co at https://www.witchesbrew.co.
- Scanner check ID: accessibility_axe_violations.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 rule points lost.
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: .gold.
- Current colors: foreground #252326 on background #26262b.
- Contrast: 1.03:1 measured; 4.5:1 required.
- Suggested foreground: #8E8C8E, which measures 4.51:1 on the current background.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Fix each reported accessibility violation at the semantic source.
- Avoid suppressing automated checks unless there is a documented false positive.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible.
- Fixes do not introduce new keyboard, label, contrast, or landmark regressions.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

The browser-rendered page has layout or tap-target issues.

Evidence

Horizontal overflow: 0px. Small tap targets: 19.

Affected elements

8 found

Small tap target

260x40px

Meet Godwin the Gargoyle ✦

Small tap target

264x40px

Browse the Tea Apothecary ✦

Small tap target

251x40px

Small tap target

251x40px

Tarot Readings

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.

Agent Prompt

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve witchesbrew.co at https://www.witchesbrew.co.
- Scanner check ID: design_rendered_layout.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 19.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### Meet Godwin the Gargoyle ✦
- Selector: div.bc-slide.on:nth-of-type(1) > div.bc-grid > div > a.bc-cta.
- Tap target size: 260x40px.
### Browse the Tea Apothecary ✦
- Selector: div.bc-slide:nth-of-type(3) > div.bc-grid.bc-grid--tea > div > a.bc-cta.
- Tap target size: 264x40px.
### Menu
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(1).
- Tap target size: 251x40px.
### Tarot Readings
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(2).
- Tap target size: 251x40px.
### Our Partners & Values
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(3).
- Tap target size: 251x40px.
### Catering
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(4).
- Tap target size: 251x40px.
### E Gift Card
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(5).
- Tap target size: 251x40px.
### Careers
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(6).
- Tap target size: 251x40px.
## Task
Use the provided context to safely complete this workflow: 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.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Constrain overflowing elements and increase small important tap targets where possible.
- Preserve layout intent while making the rendered page usable on real devices.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The rendered page has no meaningful horizontal overflow.
- Important links, buttons, inputs, and controls are comfortably tappable.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Score aggregation details

Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.

100/100

13 pass

0 fail

0 unknown

SEO / AEO

Severity mix: 1 critical, 7 high, 3 medium, 1 low.

No failed checks in this category.

100/100

6 pass

0 fail

0 unknown

Security

Severity mix: 2 critical, 3 high, 0 medium, 0 low.

No failed checks in this category.

81/100

7 pass

1 fail

0 unknown

Accessibility

Severity mix: 0 critical, 3 high, 5 medium, 0 low.

high

Rendered axe accessibility violations

-18 rule pts

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).

Affected elements

1 found

See the Menu

1.03:1 fail

Needs 4.5:1

Current colors

Pass 4.51:1

92/100

10 pass

1 fail

0 unknown

Design

Severity mix: 0 critical, 3 high, 6 medium, 2 low.

medium

Rendered layout ergonomics

-9 rule pts

Horizontal overflow: 0px. Small tap targets: 19.

Affected elements

8 found

Small tap target

260x40px

Meet Godwin the Gargoyle ✦

Small tap target

264x40px

Browse the Tea Apothecary ✦

Small tap target

251x40px

Small tap target

251x40px

Tarot Readings

Full check list

Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.

Failed checks

These checks need attention.

fail

high

Accessibility

Rendered axe accessibility violations

0/18

axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).

Affected elements

1 found

See the Menu

1.03:1 fail

Needs 4.5:1

Current colors

Pass 4.51: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.

Agent Prompt

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve witchesbrew.co at https://www.witchesbrew.co.
- Scanner check ID: accessibility_axe_violations.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 of 18 rule points lost.
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: .gold.
- Current colors: foreground #252326 on background #26262b.
- Contrast: 1.03:1 measured; 4.5:1 required.
- Suggested foreground: #8E8C8E, which measures 4.51:1 on the current background.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Fix each reported accessibility violation at the semantic source.
- Avoid suppressing automated checks unless there is a documented false positive.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible.
- Fixes do not introduce new keyboard, label, contrast, or landmark regressions.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

fail

medium

Design

Rendered layout ergonomics

0/9

Horizontal overflow: 0px. Small tap targets: 19.

Affected elements

8 found

Small tap target

260x40px

Meet Godwin the Gargoyle ✦

Small tap target

264x40px

Browse the Tea Apothecary ✦

Small tap target

251x40px

Small tap target

251x40px

Tarot Readings

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.

Agent Prompt

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve witchesbrew.co at https://www.witchesbrew.co.
- Scanner check ID: design_rendered_layout.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 19.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Affected Elements
### Meet Godwin the Gargoyle ✦
- Selector: div.bc-slide.on:nth-of-type(1) > div.bc-grid > div > a.bc-cta.
- Tap target size: 260x40px.
### Browse the Tea Apothecary ✦
- Selector: div.bc-slide:nth-of-type(3) > div.bc-grid.bc-grid--tea > div > a.bc-cta.
- Tap target size: 264x40px.
### Menu
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(1).
- Tap target size: 251x40px.
### Tarot Readings
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(2).
- Tap target size: 251x40px.
### Our Partners & Values
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(3).
- Tap target size: 251x40px.
### Catering
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(4).
- Tap target size: 251x40px.
### E Gift Card
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(5).
- Tap target size: 251x40px.
### Careers
- Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(6).
- Tap target size: 251x40px.
## Task
Use the provided context to safely complete this workflow: 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.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Constrain overflowing elements and increase small important tap targets where possible.
- Preserve layout intent while making the rendered page usable on real devices.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The rendered page has no meaningful horizontal overflow.
- Important links, buttons, inputs, and controls are comfortably tappable.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

Page-level AEO readiness

Shared eligibility and content signals that affect every search and answer agent.

85/100 ready

Index and citation eligibility

No general noindex directive was detected.

Snippet and answer controls

No general nosnippet or max-snippet:0 control was detected.

Canonical alignment

The canonical resolves to the scanned public URL.

Sitemap coverage and freshness

The exact URL appears in the fetched sitemap.

Structured data

Semantic schema score 35/100. Detected 1 JSON-LD block(s), 0 parse error(s), 7 graph node(s), and types CafeOrCoffeeShop, City, FoodEstablishment, GeoCoordinates, LocalBusiness, LocationFeatureSpecification, OpeningHoursSpecification, PostalAddress. No primary schema type matched the detected page role.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

Entity alignment scored 85/100 for “Witches Brew Coffee Co”. Title/H1 token overlap is 100%; description match detected; identity schema not detected.

Answer-ready visible text

Answerability scored 70/100 from 1288 main-content words, 6 concise answer block(s), 0 question heading(s), 15 definition(s), 0 list(s), and 0 table(s).

Authorship and accountability

Authorship is not a universal requirement for the detected home page role.

Published or updated date

Freshness metadata is contextual for the detected home page role.

Supporting-source links

Supporting sources are contextual for the detected home page role and do not affect readiness.

Rendered content availability

Rendered audit completed with 109 visible text element(s).

Synthetic search-agent reachability

8 of 8 completed search/discovery User-Agent probes returned reachable content.

Optional LLM-readable summary

https://www.witchesbrew.co/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

OpenAIChatGPT search

OAI-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

OpenAIChatGPT user fetches

ChatGPT-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity user fetches

Perplexity-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed by * allow: / · line 2

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

POLICY ALLOWED

Model training

Robots: allowed by * allow: / · line 2

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Vendor documentationDefinition checked 2026-07-30

Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.

Public report link

Markdown export

Share the website audit report

Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.

Share preview

witchesbrew.co website audit report

Ready to share: 93/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# witchesbrew.co Website Scan

Scanned URL: [https://www.witchesbrew.co](https://www.witchesbrew.co)
Report URL: /scan/witchesbrew-co-93-launch-readiness-report-f4cfe13d
Created: 2026-08-21T06:54:05.961Z

## Score Summary

- Overall: 93/100
- SEO / AEO: 100/100
- Security: 100/100
- Accessibility: 81/100
- Design: 92/100

## Launch Readiness

Ready to share (Strong).

Passed: 36. Failed: 2. Unknown: 0.
Strongest area: SEO / AEO. Weakest area: Accessibility.

## AI Crawler Access

These results combine robots.txt policy, page controls, and bounded synthetic User-Agent probes. Synthetic probes do not prove that traffic came from the vendor; training and data-use choices are neutral publisher preferences.

- **OpenAI: ChatGPT search** (OAI-SearchBot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **OpenAI: OpenAI model training** (GPTBot): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **OpenAI: ChatGPT user fetches** (ChatGPT-User): UNKNOWN; robots not_applicable; synthetic probe not_tested. ChatGPT-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic: Claude model training** (ClaudeBot): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Anthropic: Claude search** (Claude-SearchBot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Anthropic: Claude user fetches** (Claude-User): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google: Google Search and AI features** (Googlebot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Google: Gemini data use and grounding** (Google-Extended): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Microsoft: Bing and Copilot** (Bingbot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity: Perplexity search** (PerplexityBot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Perplexity: Perplexity user fetches** (Perplexity-User): UNKNOWN; robots not_applicable; synthetic probe not_tested. Perplexity-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control.
- **Apple: Siri, Spotlight, and Safari search** (Applebot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Apple: Apple foundation-model training** (Applebot-Extended): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Mistral AI: Mistral search** (MistralAI-Index): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Mistral AI: Mistral user fetches** (MistralAI-User): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Meta: Meta AI model and product data** (meta-externalagent): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Meta: Meta AI user fetches** (meta-externalfetcher): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon: Amazon model training** (Amazonbot): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.
- **Amazon: Alexa and Rufus search** (Amzn-SearchBot): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Amazon: Alexa user fetches** (Amzn-User): PASS; robots allowed; synthetic probe reachable (HTTP 200). Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity.
- **Common Crawl: Open web datasets** (CCBot): PREFERENCE; robots allowed; synthetic probe not_tested. Allowed by * allow: / on line 2. No synthetic fetch is appropriate for this policy or training control.

## Page-level AEO Readiness

Readiness: 85/100

- **Index and citation eligibility**: PASS. No general noindex directive was detected.
- **Snippet and answer controls**: PASS. No general nosnippet or max-snippet:0 control was detected.
- **Canonical alignment**: PASS. The canonical resolves to the scanned public URL.
- **Sitemap coverage and freshness**: PASS. The exact URL appears in the fetched sitemap.
- **Structured data**: UNKNOWN. Semantic schema score 35/100. Detected 1 JSON-LD block(s), 0 parse error(s), 7 graph node(s), and types CafeOrCoffeeShop, City, FoodEstablishment, GeoCoordinates, LocalBusiness, LocationFeatureSpecification, OpeningHoursSpecification, PostalAddress. No primary schema type matched the detected page role.
- **Public or paywalled content**: INFO. No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: PASS. Entity alignment scored 85/100 for “Witches Brew Coffee Co”. Title/H1 token overlap is 100%; description match detected; identity schema not detected.
- **Answer-ready visible text**: PASS. Answerability scored 70/100 from 1288 main-content words, 6 concise answer block(s), 0 question heading(s), 15 definition(s), 0 list(s), and 0 table(s).
- **Authorship and accountability**: INFO. Authorship is not a universal requirement for the detected home page role.
- **Published or updated date**: INFO. Freshness metadata is contextual for the detected home page role.
- **Supporting-source links**: INFO. Supporting sources are contextual for the detected home page role and do not affect readiness.
- **Rendered content availability**: PASS. Rendered audit completed with 109 visible text element(s).
- **Synthetic search-agent reachability**: PASS. 8 of 8 completed search/discovery User-Agent probes returned reachable content.
- **Optional LLM-readable summary**: INFO. https://www.witchesbrew.co/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. Fix rendered axe accessibility violations

- Category: Accessibility
- Status: fail
- Severity: high
- Rule points lost: 18
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1).
- 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.

### 2. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 19.
- 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.

## Opportunities

### Deepen structured data beyond basic presence

- Impact: medium
- Category: SEO / AEO
- Evidence: Detected schema types: CafeOrCoffeeShop, City, FoodEstablishment, GeoCoordinates, LocalBusiness, LocationFeatureSpecification, OpeningHoursSpecification, PostalAddress. Parse errors: 0.
- Why it matters: Search and answer systems trust explicit facts most when structured data is valid and matches visible page content.
- Next step: Validate JSON-LD and add accurate Organization, WebSite, SoftwareApplication/Product, FAQ, or Breadcrumb schema where the page content supports it.

### Add answer-ready sections for common buyer questions

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 0. Use-case signals: 0. Integration/API signals: 0.
- Why it matters: Answer engines and search visitors need concise textual answers to summarize who the product is for, how it works, what it costs, and what it connects with.
- Next step: Add short, crawlable sections for pricing or plans, ideal users, use cases, integrations, security, and how the product differs from alternatives.

### Expose important supporting pages in navigation or footer

- Impact: medium
- Category: SEO / AEO
- Evidence: Detected 2 important internal link(s): /pages/contact, /pages/contact.
- Why it matters: Internal links help visitors, crawlers, and AI answer systems discover supporting facts instead of relying on one landing page.
- Next step: Link to the most useful public pages, especially pricing, docs, contact, security, privacy, terms, and about pages where applicable.

### Make trust and proof easier to detect

- Impact: medium
- Category: Design
- Evidence: Detected 1 trust-signal keyword occurrence(s).
- Why it matters: Visitors who arrive cold from search, social, or AI citations need proof before they submit a form, start a trial, or buy.
- Next step: Add honest proof such as customer quotes, recognizable logos, security notes, usage stats, reviews, case studies, or founder credibility.

### Review snippet and preview controls

- Impact: low
- Category: SEO / AEO
- Evidence: Open Graph image was detected. Preview controls detected: 0.
- Why it matters: Preview controls can clarify how much text, image, and video content search systems may show from the page.
- Next step: Only add robots preview controls when you intentionally want to limit snippets or image/video previews; otherwise leave previews open.

### Polish rendered responsive ergonomics

- Impact: medium
- Category: Design
- Evidence: Horizontal overflow: 0px. Small tap targets: 19.
- Why it matters: Overflow and tiny controls are easy for static scans to miss but obvious to real users, especially on mobile and tablet layouts.
- Next step: Constrain wide elements, avoid fixed-width content that exceeds the viewport, and increase touch target sizes for interactive controls.

### Measure search performance with first-party data

- Impact: medium
- Category: SEO / AEO
- Evidence: robots.txt and a sitemap were reachable, so the site has the basics needed for Search Console verification and monitoring.
- Why it matters: A scan can identify technical readiness, but Search Console and analytics reveal impressions, queries, clicks, pages, and conversions over time.
- Next step: Verify the domain in Search Console, submit the sitemap, and pair query/page data with analytics events for signups, demo requests, and purchases.

## Insights

### The page appears basically crawlable

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: HTTP 200. sitemap.xml: HTTP 200. noindex check: clear.
- Interpretation: The public page satisfies the basic crawl/index path the scan can verify.
- Recommended use: Use this as the first launch gate before deeper content, ranking, or AI visibility work.

### AEO depends on normal SEO plus answerable text

- Category: SEO / AEO
- Evidence: Visible words: 1347. H1 count: 1. Audience signals: 8. CTA labels: Book a Reading, Join, Subscribe &#10022;.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

- Category: SEO / AEO
- Evidence: Title: Witches Brew Coffee Co | Witchy Coffee & Tea Cafe in New Orleans, LA. H1: Witches Brew     Coffee Co. Schema types: CafeOrCoffeeShop, City, FoodEstablishment, GeoCoordinates, LocalBusiness, LocationFeatureSpecification, OpeningHoursSpecification, PostalAddress.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### Structured data is present

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 1. Types: CafeOrCoffeeShop, City, FoodEstablishment, GeoCoordinates, LocalBusiness, LocationFeatureSpecification, OpeningHoursSpecification, PostalAddress. Parse errors: 0.
- Interpretation: The page exposes machine-readable facts, but quality still depends on whether those facts match visible content.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Accessibility
- Evidence: SEO / AEO: 100/100. Security: 100/100. Accessibility: 81/100. Design: 92/100
- Interpretation: The weakest area is Accessibility, so improvements there should have the most visible effect on readiness.
- Recommended use: Use the score mix to choose the next workstream instead of treating every issue as equally urgent.

### LLM-readable file found

- Category: SEO / AEO
- Evidence: https://www.witchesbrew.co/llms.txt returned HTTP 200.
- Interpretation: llms.txt can be a useful optional summary for agents, but it should not be treated as a guaranteed AI search ranking factor.
- Recommended use: Invest first in crawlability, helpful visible content, internal links, and accurate schema; add llms.txt as a tidy supplement.

### Rendered page experience snapshot

- Category: Design
- Evidence: Rendered text samples: 100. Contrast failures: 0. Console errors: 0. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 1020ms. Load complete: 1718ms. First contentful paint: 736ms. Resources: 42. Scripts: 1. Images: 27. Third-party origins: 7. Transfer: not available.
- Interpretation: These are lightweight browser timings from one rendered scan, so they are useful directional signals rather than real-user performance proof.
- Recommended use: Use slow timings, high script counts, heavy transfer size, and many third-party origins to choose focused speed work, then verify important changes with analytics or field data when available.

### Rendered axe accessibility snapshot

- Category: Accessibility
- Evidence: axe violations: 1. Critical: 0. Serious: 1. Top rules: color-contrast.
- Interpretation: axe-core catches common accessibility failures in the actual rendered DOM, but it is still automated coverage and not a full manual accessibility audit.
- Recommended use: Treat critical and serious axe failures as high-priority fixes, then manually review keyboard flow, focus states, screen reader meaning, and interaction states.

## Scope

FreeScan.app performs safe public checks only. It is not a penetration test, full SEO engagement, full accessibility audit, WCAG certification, backlink audit, rank tracker, or analytics platform.

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.

Rescan same URL

Rerun the full deterministic scanner for witchesbrew.co without re-entering the URL. The previous report stays saved so the next result can be compared against it.

## Role Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve witchesbrew.co at https://www.witchesbrew.co. - Scanner check ID: accessibility_axe_violations. - Fix title: Fix rendered axe accessibility violations. - Scanner check: Rendered axe accessibility violations. - Category: Accessibility. - Status: fail. - Severity: high. - Priority: 5; lower numbers are more urgent. - Score impact: 18 rule points lost. - Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1). - What needs attention: The rendered page has accessibility rule violations detected by axe-core. - Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Affected Elements ### Elements must meet minimum color contrast ratio thresholds - Source: axe rule color-contrast. - Selector: .gold. - Current colors: foreground #252326 on background #26262b. - Contrast: 1.03:1 measured; 4.5:1 required. - Suggested foreground: #8E8C8E, which measures 4.51:1 on the current background. ## Task Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Fix each reported accessibility violation at the semantic source. - Avoid suppressing automated checks unless there is a documented false positive. - Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds. - Keep keyboard, screen reader, and touch users in the verification path. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible. - Fixes do not introduce new keyboard, label, contrast, or landmark regressions. - The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions. - The change can be checked in the browser or with an accessibility audit tool when available. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions. ## Rules - Ask a clarifying question when required context is missing. - Preserve the user's intent and avoid inventing facts. - Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change. - If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior. - Keep the change narrowly scoped to this fix unless another change is required to avoid a regression. - Match the existing framework, style, design system, routing patterns, and content conventions. - Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them. - Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved. - Make changes that are easy to review and roll back. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - Verify the result with the smallest reliable test, build, browser check, or manual inspection available. ## Safety - Do not request, expose, or reproduce sensitive data. - Redact private details from examples unless the user explicitly says they are safe to include. - Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies. - Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve witchesbrew.co at https://www.witchesbrew.co. - Scanner check ID: design_rendered_layout. - Fix title: Fix rendered layout ergonomics. - Scanner check: Rendered layout ergonomics. - Category: Design. - Status: fail. - Severity: medium. - Priority: 13; lower numbers are more urgent. - Score impact: 9 rule points lost. - Evidence: Horizontal overflow: 0px. Small tap targets: 19. - What needs attention: The browser-rendered page has layout or tap-target issues. - Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Affected Elements ### Meet Godwin the Gargoyle ✦ - Selector: div.bc-slide.on:nth-of-type(1) > div.bc-grid > div > a.bc-cta. - Tap target size: 260x40px. ### Browse the Tea Apothecary ✦ - Selector: div.bc-slide:nth-of-type(3) > div.bc-grid.bc-grid--tea > div > a.bc-cta. - Tap target size: 264x40px. ### Menu - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(1). - Tap target size: 251x40px. ### Tarot Readings - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(2). - Tap target size: 251x40px. ### Our Partners & Values - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(3). - Tap target size: 251x40px. ### Catering - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(4). - Tap target size: 251x40px. ### E Gift Card - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(5). - Tap target size: 251x40px. ### Careers - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(6). - Tap target size: 251x40px. ## Task Use the provided context to safely complete this workflow: 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. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Constrain overflowing elements and increase small important tap targets where possible. - Preserve layout intent while making the rendered page usable on real devices. - Improve the actual rendered page at mobile and desktop sizes, not only the source code shape. - Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The rendered page has no meaningful horizontal overflow. - Important links, buttons, inputs, and controls are comfortably tappable. - The rendered page is visually stable and usable on mobile and desktop viewports. - The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions. ## Rules - Ask a clarifying question when required context is missing. - Preserve the user's intent and avoid inventing facts. - Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change. - If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior. - Keep the change narrowly scoped to this fix unless another change is required to avoid a regression. - Match the existing framework, style, design system, routing patterns, and content conventions. - Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them. - Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved. - Make changes that are easy to review and roll back. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - Verify the result with the smallest reliable test, build, browser check, or manual inspection available. ## Safety - Do not request, expose, or reproduce sensitive data. - Redact private details from examples unless the user explicitly says they are safe to include. - Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies. - Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve witchesbrew.co at https://www.witchesbrew.co. - Scanner check ID: accessibility_axe_violations. - Fix title: Fix rendered axe accessibility violations. - Scanner check: Rendered axe accessibility violations. - Category: Accessibility. - Status: fail. - Severity: high. - Priority: 5; lower numbers are more urgent. - Score impact: 18 of 18 rule points lost. - Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1). - What needs attention: The rendered page has accessibility rule violations detected by axe-core. - Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Affected Elements ### Elements must meet minimum color contrast ratio thresholds - Source: axe rule color-contrast. - Selector: .gold. - Current colors: foreground #252326 on background #26262b. - Contrast: 1.03:1 measured; 4.5:1 required. - Suggested foreground: #8E8C8E, which measures 4.51:1 on the current background. ## Task Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Fix each reported accessibility violation at the semantic source. - Avoid suppressing automated checks unless there is a documented false positive. - Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds. - Keep keyboard, screen reader, and touch users in the verification path. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible. - Fixes do not introduce new keyboard, label, contrast, or landmark regressions. - The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions. - The change can be checked in the browser or with an accessibility audit tool when available. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions. ## Rules - Ask a clarifying question when required context is missing. - Preserve the user's intent and avoid inventing facts. - Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change. - If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior. - Keep the change narrowly scoped to this fix unless another change is required to avoid a regression. - Match the existing framework, style, design system, routing patterns, and content conventions. - Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them. - Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved. - Make changes that are easy to review and roll back. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - Verify the result with the smallest reliable test, build, browser check, or manual inspection available. ## Safety - Do not request, expose, or reproduce sensitive data. - Redact private details from examples unless the user explicitly says they are safe to include. - Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies. - Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation. ## Inputs - Primary context: Improve witchesbrew.co at https://www.witchesbrew.co. - Scanner check ID: design_rendered_layout. - Fix title: Fix rendered layout ergonomics. - Scanner check: Rendered layout ergonomics. - Category: Design. - Status: fail. - Severity: medium. - Priority: 13; lower numbers are more urgent. - Score impact: 9 of 9 rule points lost. - Evidence: Horizontal overflow: 0px. Small tap targets: 19. - What needs attention: The browser-rendered page has layout or tap-target issues. - Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors. - Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix. - Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page. - Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything. - Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals. - Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps. ## Affected Elements ### Meet Godwin the Gargoyle ✦ - Selector: div.bc-slide.on:nth-of-type(1) > div.bc-grid > div > a.bc-cta. - Tap target size: 260x40px. ### Browse the Tea Apothecary ✦ - Selector: div.bc-slide:nth-of-type(3) > div.bc-grid.bc-grid--tea > div > a.bc-cta. - Tap target size: 264x40px. ### Menu - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(1). - Tap target size: 251x40px. ### Tarot Readings - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(2). - Tap target size: 251x40px. ### Our Partners & Values - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(3). - Tap target size: 251x40px. ### Catering - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(4). - Tap target size: 251x40px. ### E Gift Card - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(5). - Tap target size: 251x40px. ### Careers - Selector: div.foot-inner > div.foot-grid:nth-of-type(1) > div.foot-col:nth-of-type(1) > a:nth-of-type(6). - Tap target size: 251x40px. ## Task Use the provided context to safely complete this workflow: 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. First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience. Use this check-specific implementation guide: - Constrain overflowing elements and increase small important tap targets where possible. - Preserve layout intent while making the rendered page usable on real devices. - Improve the actual rendered page at mobile and desktop sizes, not only the source code shape. - Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better. - Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project. Acceptance criteria for this fix: - The rendered page has no meaningful horizontal overflow. - Important links, buttons, inputs, and controls are comfortably tappable. - The rendered page is visually stable and usable on mobile and desktop viewports. - The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors. - A fresh FreeScan rescan should show this check improved or passing after deployment. ## Output Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions. ## Rules - Ask a clarifying question when required context is missing. - Preserve the user's intent and avoid inventing facts. - Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change. - If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior. - Keep the change narrowly scoped to this fix unless another change is required to avoid a regression. - Match the existing framework, style, design system, routing patterns, and content conventions. - Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them. - Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved. - Make changes that are easy to review and roll back. - Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets. - Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology. - Verify the result with the smallest reliable test, build, browser check, or manual inspection available. ## Safety - Do not request, expose, or reproduce sensitive data. - Redact private details from examples unless the user explicitly says they are safe to include. - Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies. - Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

witchesbrew.co Website Audit

Element selector

Element selector

Element selector

Element selector

Element selector

Show 4 more

Fix rendered axe accessibility violations

Element selector

Agent Prompt

Fix rendered layout ergonomics

Element selector

Element selector

Element selector

Element selector

Show 4 more

Agent Prompt

SEO / AEO

Security

Accessibility

Rendered axe accessibility violations

Element selector

Design

Rendered layout ergonomics

Element selector

Element selector

Element selector

Element selector

Show 4 more

Failed checks

Rendered axe accessibility violations

Element selector

Agent Prompt

Rendered layout ergonomics

Element selector

Element selector

Element selector

Element selector

Show 4 more

Agent Prompt

AI crawler accessMajor AI search, user-fetch, and data-use agents checked for /, with robots evidence, synthetic reachability, and page-level AEO controls.12 pass0 fail2 unknown7 preferences

Unknown and not detected statesFreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.

Safe fetch metadataPublic headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.

witchesbrew.co Website Audit

Element selector

Element selector

Element selector

Element selector

Element selector

Show 4 more

Fix rendered axe accessibility violations

Element selector

Agent Prompt

Fix rendered layout ergonomics

Element selector

Element selector

Element selector

Element selector

Show 4 more

Agent Prompt

SEO / AEO

Security

Accessibility

Rendered axe accessibility violations

Element selector

Design

Rendered layout ergonomics

Element selector

Element selector

Element selector

Element selector

Show 4 more

Failed checks

Rendered axe accessibility violations

Element selector

Agent Prompt

Rendered layout ergonomics

Element selector

Element selector

Element selector