What your site is actually doing.

Audit of https://whitewolfmarketing.com/, run August 26, 2026. 15 issues were found. I want them fixed.

## Context
- Site: https://whitewolfmarketing.com/
- Mobile LCP (lab median): 1812 ms
- Desktop LCP (lab median): 1952 ms
- Page weight (median): 1.5 MB
- Tap targets under 44px: 42% (24 of 57)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 1.8s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- Light page weight: The page is about 1.5 MB across 180 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- No JavaScript errors on load: Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- Search basics are in place: Lighthouse scores SEO 100/100. The fundamentals Google looks for are present.
- Layout holds on phone and desktop: Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

## Issues, most damaging first

### 1. [HIGH] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 24 of 57 tappable items on this page (42%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.
Exact elements found: a 1x1 "Skip to content", a 270x21 "Brand Strategy", a 270x21 "Website Development", a 270x21 "SEO & Organic", a 270x21 "Paid Media", a 270x21 "Social Media", a 270x21 "Content & Editorial", a 270x21 "Automation & Systems"

### 2. [HIGH] A floating widget is covering a clickable element
Category: Conversion, Accessibility (WCAG)
Why it matters: 3 clickable elements are sitting underneath a fixed overlay (div.e-con-inner over a "Social Media"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.
Exact elements found: a "Social Media" under div.e-con-inner, a "Automation & Systems" under div.elementor-widget-container, a "Instagram" under div.cky-notice

### 3. [HIGH] Meta Pixel (Facebook) is installed but misconfigured
Category: Tracking
Why it matters: Meta Pixel installed but no Lead/Purchase/Checkout event fires on this page, only PageView. Your Meta ad sessions can't be optimized for conversions until you track at least one downstream event.

### 4. [HIGH] Add quotations so AI engines cite this page
Category: AI Search, SEO
Why it matters: Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

### 5. [HIGH] Google Analytics tracking broken
Category: Tracking, Conversion
Why it matters: The Google Analytics request failed to complete on every one of the 4 test loads. If real visitors hit the same failure, GA is missing those visits and the dashboard has no way to flag it. Conversion numbers, audience counts, and channel attribution are all undercounting. Worth checking the tag loading order and any consent banner that might be blocking the request.

### 6. [HIGH] Some text is low-contrast and hard to read
Category: Accessibility (WCAG)
Why it matters: Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.

### 7. [MEDIUM] AI search crawlers are blocked
Category: SEO
Why it matters: Your robots.txt blocks 8 AI crawlers (gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.
Exact examples found: gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent

### 8. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 52 of 52 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.
Exact elements found: revisit.svg "Revisit consent button", close.svg, whitewolf-logo-dark.png, whitewolf-logo-dark.png, 6076026909aca.png "Client logo", ACGC.png "Client logo"

### 9. [LOW] Unused JavaScript is being downloaded
Category: Performance
Why it matters: Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 375 KiB.

### 10. [LOW] Unused CSS is being downloaded
Category: Performance
Why it matters: Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 315 KiB.

### 11. [LOW] The page is heavy to download
Category: Performance
Why it matters: Total page weight is high. On a phone with patchy data, that is extra seconds of blank screen before the page is usable. Lighthouse measured: Total size was 2,862 KiB.

### 12. [LOW] The page loads from a lot of third-party services
Why it matters: Around 25 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.
How we know: median across loads

### 13. [LOW] Security headers are missing or weak
Category: Security
Why it matters: The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: HSTS (Strict-Transport-Security, which forces HTTPS on return visits). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.

### 14. [LOW] Headings skip levels
Category: Accessibility (WCAG)
Why it matters: Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on.

### 15. [LOW] Some text is too small to read on phones
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 18 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.
How we know: median across loads

## How to respond
Work through the issues in order. For each one give me the specific change that fixes it: real code or real copy, not advice. Keep changes minimal and match the existing style of the site.
Where several issues share one root cause, say so and fix it once rather than patching each symptom.
If an issue cannot be fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.

{
  "generated_by": "Harvv",
  "report_url": "https://whitewolfmarketing.com/",
  "generated_at": "2026-08-26T03:46:38.531Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 1812,
    "desktop_lcp_ms": 1952,
    "mobile_ttfb_ms": 550,
    "mobile_fcp_ms": 1020,
    "page_weight_kb": 1499
  },
  "finding_count": 15,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "24 of 57 tappable items on this page (42%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tap_targets",
      "confidence": "measured",
      "evidence": [
        "a 1x1 \"Skip to content\"",
        "a 270x21 \"Brand Strategy\"",
        "a 270x21 \"Website Development\"",
        "a 270x21 \"SEO & Organic\"",
        "a 270x21 \"Paid Media\"",
        "a 270x21 \"Social Media\"",
        "a 270x21 \"Content & Editorial\"",
        "a 270x21 \"Automation & Systems\""
      ]
    },
    {
      "severity": "high",
      "title": "A floating widget is covering a clickable element",
      "detail": "3 clickable elements are sitting underneath a fixed overlay (div.e-con-inner over a \"Social Media\"), so a visitor who tries to tap them hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons.",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)"
      ],
      "topic": "obscured_control",
      "confidence": "measured",
      "evidence": [
        "a \"Social Media\" under div.e-con-inner",
        "a \"Automation & Systems\" under div.elementor-widget-container",
        "a \"Instagram\" under div.cky-notice"
      ]
    },
    {
      "severity": "high",
      "title": "Meta Pixel (Facebook) is installed but misconfigured",
      "detail": "Meta Pixel installed but no Lead/Purchase/Checkout event fires on this page, only PageView. Your Meta ad sessions can't be optimized for conversions until you track at least one downstream event.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "tracker_misconfig:Meta Pixel (Facebook)",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Add quotations so AI engines cite this page",
      "detail": "Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "AI Search",
        "SEO"
      ],
      "topic": "geo",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Google Analytics tracking broken",
      "detail": "The Google Analytics request failed to complete on every one of the 4 test loads. If real visitors hit the same failure, GA is missing those visits and the dashboard has no way to flag it. Conversion numbers, audience counts, and channel attribution are all undercounting. Worth checking the tag loading order and any consent banner that might be blocking the request.",
      "device": "both",
      "tags": [
        "Tracking",
        "Conversion"
      ],
      "topic": "tracking",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Some text is low-contrast and hard to read",
      "detail": "Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "contrast",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "AI search crawlers are blocked",
      "detail": "Your robots.txt blocks 8 AI crawlers (gptbot, google-extended, claudebot, ccbot, bytespider, applebot-extended, amazonbot, meta-externalagent). Those engines (ChatGPT, Perplexity, Google AI Overviews, Claude) cannot read your site, so your content cannot be cited or shown in AI search.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "ai_crawler_blocked",
      "confidence": "measured",
      "evidence": [
        "gptbot",
        "google-extended",
        "claudebot",
        "ccbot",
        "bytespider",
        "applebot-extended",
        "amazonbot",
        "meta-externalagent"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "52 of 52 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0, which is fine), most likely because space is reserved another way (CSS), so this is not causing visible jumps today. It is still worth setting explicit dimensions or a CSS aspect-ratio so a slow connection or a future style change cannot reintroduce shift.",
      "device": "both",
      "tags": [
        "Performance",
        "SEO"
      ],
      "topic": "image_dims",
      "confidence": "measured",
      "evidence": [
        "revisit.svg \"Revisit consent button\"",
        "close.svg",
        "whitewolf-logo-dark.png",
        "whitewolf-logo-dark.png",
        "6076026909aca.png \"Client logo\"",
        "ACGC.png \"Client logo\""
      ]
    },
    {
      "severity": "low",
      "title": "Unused JavaScript is being downloaded",
      "detail": "Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 375 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused CSS is being downloaded",
      "detail": "Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 315 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page is heavy to download",
      "detail": "Total page weight is high. On a phone with patchy data, that is extra seconds of blank screen before the page is usable. Lighthouse measured: Total size was 2,862 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page loads from a lot of third-party services",
      "detail": "Around 25 separate outside domains load on this page (analytics, ads, chat widgets, fonts). Each one is a connection that can be slow, fail, or change behavior outside your control.",
      "device": "both",
      "tags": [],
      "topic": "third_party",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Security headers are missing or weak",
      "detail": "The server response is missing browser-hardening headers that protect visitors and are a standard security and agency checklist item. Missing or weak here: HSTS (Strict-Transport-Security, which forces HTTPS on return visits). These are set at the server, CDN, or host level (most platforms expose them in settings or a config file) and do not change how the site looks or performs.",
      "device": "both",
      "tags": [
        "Security"
      ],
      "topic": "security_headers",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Headings skip levels",
      "detail": "Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Some text is too small to read on phones",
      "detail": "18 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tiny_text",
      "confidence": "sampled",
      "evidence": []
    }
  ]
}