What your site is actually doing.

Audit of https://invincibowl.com/, run August 19, 2026. 13 issues were found. I want them fixed.

## Context
- Site: https://invincibowl.com/
- Mobile LCP (lab median): 332 ms
- Desktop LCP (lab median): 248 ms
- Page weight (median): 8.8 MB
- Tap targets under 44px: 28% (27 of 95)
- Evidence base: 6 mobile + 3 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: Real Chrome visitors see the main content in 1.0s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Layout stays put as it loads: Real visitors see only 0.00 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- 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] 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.)

### 2. [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.

### 3. [HIGH] Some buttons have no accessible name
Category: Accessibility (WCAG), Tracking
Why it matters: A button with only an icon and no label is announced as "button" by screen readers, giving no idea what it does.

### 4. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 27 of 95 tappable items on this page (28%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend 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: button 20x20 "Search our site", a 42x21 (no visible label), a 65x21 (no visible label), a 32x21 (no visible label), a 78x21 (no visible label), a 74x21 (no visible label), a 84x21 (no visible label), a 83x21 (no visible label)

### 5. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 8.8 megabytes, roughly 200 KB of images and 1976 KB of JavaScript across 371 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.
How we know: median across loads

### 6. [MEDIUM] Social share image is served over insecure HTTP
Category: SEO
Why it matters: The Open Graph image is an http:// URL. Facebook, iMessage, Discord, LinkedIn and others often refuse to render an insecure preview image, so shared links can appear with no image even though one is set. Serve it over https.

### 7. [MEDIUM] Click activity may be invisible inside the Facebook in-app browser
Category: Tracking
Why it matters: Patterns on this page (65 custom-element tags) tend to suppress click events inside Android Webview and iOS in-app browsers. Visitors arriving from Meta ads may register as zero-interaction sessions even when they're actively using the page. Add a server-side landing tracker so you don't lose that audience entirely.

### 8. [MEDIUM] 8 interactive elements have no stable, accessible identity
Category: Accessibility (WCAG), Tracking
Why it matters: These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.
Exact elements found: (button.menu-drawer__close-button) (no accessible name), (button.menu-drawer__close-button) (no accessible name), (mini-cart.cart-drawer) (no accessible name), (button.image-comparison__button) (no accessible name), (button.list-social__link) (no accessible name), "Menu" (div.dock__item) (div/span used as a button, no role), "Search" (div.dock__item) (div/span used as a button, no role), "Cart" (div.dock__item) (div/span used as a button, no role)

### 9. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 21 of 27 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.00, 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: logo_image_508f23fc216ce8e535ea0716c57926fc.png "Logo", Stag_hande_vert_70x70.jpg "Wood Pipes", PoleScreens_Composite_SQ_70x70.jpg "Screens for Downstem", Pipe_Side_Blue_SQ_0eec57ad-6f8e-467c-b487-f05ca51c2bc4_70x70.jpg "Invincipipe", Ultrasonic-Open1_70x70.jpg "Sonic Cleaning Bath", Bowl-Screens_Composite_SQ_70x70.jpg "Screens for Bong Bowl an"

### 10. [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 984 KiB.

### 11. [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 22 KiB.

### 12. [LOW] The page loads from a lot of third-party services
Why it matters: Around 41 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: a stronger HSTS policy (max-age at least 180 days plus includeSubDomains). 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.

## 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://invincibowl.com/",
  "generated_at": "2026-08-21T19:25:47.523Z",
  "evidence_base": {
    "mobile_loads": 6,
    "desktop_loads": 3,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 332,
    "desktop_lcp_ms": 248,
    "mobile_ttfb_ms": 22,
    "mobile_fcp_ms": 332,
    "page_weight_kb": 9011
  },
  "finding_count": 13,
  "findings": [
    {
      "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": "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": "high",
      "title": "Some buttons have no accessible name",
      "detail": "A button with only an icon and no label is announced as \"button\" by screen readers, giving no idea what it does.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "a11y_names",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "27 of 95 tappable items on this page (28%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels Apple and Google recommend 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": [
        "button 20x20 \"Search our site\"",
        "a 42x21 (no visible label)",
        "a 65x21 (no visible label)",
        "a 32x21 (no visible label)",
        "a 78x21 (no visible label)",
        "a 74x21 (no visible label)",
        "a 84x21 (no visible label)",
        "a 83x21 (no visible label)"
      ]
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 8.8 megabytes, roughly 200 KB of images and 1976 KB of JavaScript across 371 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Social share image is served over insecure HTTP",
      "detail": "The Open Graph image is an http:// URL. Facebook, iMessage, Discord, LinkedIn and others often refuse to render an insecure preview image, so shared links can appear with no image even though one is set. Serve it over https.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "og_image_insecure",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Click activity may be invisible inside the Facebook in-app browser",
      "detail": "Patterns on this page (65 custom-element tags) tend to suppress click events inside Android Webview and iOS in-app browsers. Visitors arriving from Meta ads may register as zero-interaction sessions even when they're actively using the page. Add a server-side landing tracker so you don't lose that audience entirely.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "webview",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "8 interactive elements have no stable, accessible identity",
      "detail": "These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "untrackable_elements",
      "confidence": "measured",
      "evidence": [
        "(button.menu-drawer__close-button) (no accessible name)",
        "(button.menu-drawer__close-button) (no accessible name)",
        "(mini-cart.cart-drawer) (no accessible name)",
        "(button.image-comparison__button) (no accessible name)",
        "(button.list-social__link) (no accessible name)",
        "\"Menu\" (div.dock__item) (div/span used as a button, no role)",
        "\"Search\" (div.dock__item) (div/span used as a button, no role)",
        "\"Cart\" (div.dock__item) (div/span used as a button, no role)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "21 of 27 images don't declare width and height. Your layout currently stays stable (measured Cumulative Layout Shift is 0.00, 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": [
        "logo_image_508f23fc216ce8e535ea0716c57926fc.png \"Logo\"",
        "Stag_hande_vert_70x70.jpg \"Wood Pipes\"",
        "PoleScreens_Composite_SQ_70x70.jpg \"Screens for Downstem\"",
        "Pipe_Side_Blue_SQ_0eec57ad-6f8e-467c-b487-f05ca51c2bc4_70x70.jpg \"Invincipipe\"",
        "Ultrasonic-Open1_70x70.jpg \"Sonic Cleaning Bath\"",
        "Bowl-Screens_Composite_SQ_70x70.jpg \"Screens for Bong Bowl an\""
      ]
    },
    {
      "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 984 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 22 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page loads from a lot of third-party services",
      "detail": "Around 41 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: a stronger HSTS policy (max-age at least 180 days plus includeSubDomains). 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": []
    }
  ]
}