What your site is actually doing.

Audit of https://thecarycompany.com/, run August 29, 2026. 14 issues were found. I want them fixed.

## Context
- Site: https://thecarycompany.com/
- Mobile LCP (lab median): 352 ms
- Desktop LCP (lab median): 382 ms
- Page weight (median): 2.7 MB
- Tap targets under 44px: 14% (6 of 44)
- Evidence base: 4 mobile + 2 desktop loads

## Already working, do not change these
- Speed is good: The main content paints in about 0.4s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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 92/100. The fundamentals Google looks for are present.
- Accessible to most visitors: Lighthouse accessibility is 92/100, so screen-reader and contrast basics are largely handled.
- 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] 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.

### 3. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 2.7 megabytes, roughly 392 KB of images and 1869 KB of JavaScript across 487 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

### 4. [MEDIUM] 34 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: "Account" (span.skip-link) (div/span used as a button, no role), "Toggle Nav" (span.action) (div/span used as a button, no role), (a.skip-link) (no accessible name), (span.skip-link) (no accessible name), "Search Keyword, SKU, Product ID" (span.skip-link) (div/span used as a button, no role), (span.skip-link) (no accessible name), (div.action) (no accessible name), (span.action) (no accessible name)

### 5. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 30 of 31 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: logo.svg "The Cary Company", loader-1.gif "<?= /* @escapeNotVerifie", inventory-pails.jpg, inventory-pails-mobile.jpg, drums.jpg "Drums", plastic-bottles.jpg "Plastic bottles"

### 6. [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 668 KiB.

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

### 8. [LOW] The page loads from a lot of third-party services
Why it matters: Around 28 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

### 9. [LOW] Links to this page will look bare when shared
Why it matters: The page is missing its Open Graph title and image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no title and image. A flat grey link gets far fewer clicks than one with an image and headline.

### 10. [LOW] 2 potential dead-click targets
Category: Conversion, Accessibility (WCAG), Tracking
Why it matters: Elements styled like buttons but with no anchor, no <button> wrapper, no role="button", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: "Account" (span.skip-link), "Search Keyword, SKU, Product ID" (span.skip-link).
Exact elements found: "Account" (span.skip-link), "Search Keyword, SKU, Product ID" (span.skip-link)

### 11. [LOW] No llms.txt file
Category: SEO
Why it matters: No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.

### 12. [LOW] No Organization or WebSite schema
Category: SEO
Why it matters: No site-wide Organization or WebSite structured data found on any crawled page. This is the schema that tells Google and AI engines who you are (name, logo, social profiles) for the knowledge panel and brand recognition in AI answers. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)

### 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: Content-Security-Policy (the main defense against injected and cross-site scripts); 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.

### 14. [LOW] Some links do not describe where they go
Category: Accessibility (WCAG), Conversion
Why it matters: Links like "click here" or "read more" tell screen-reader users and search engines nothing about the destination. Lighthouse measured: 1 link found.

## 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://thecarycompany.com/",
  "generated_at": "2026-08-29T03:43:03.019Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": false,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 352,
    "desktop_lcp_ms": 382,
    "mobile_ttfb_ms": 187,
    "mobile_fcp_ms": 310,
    "page_weight_kb": 2720
  },
  "finding_count": 14,
  "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": "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": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 2.7 megabytes, roughly 392 KB of images and 1869 KB of JavaScript across 487 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": "34 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": [
        "\"Account\" (span.skip-link) (div/span used as a button, no role)",
        "\"Toggle Nav\" (span.action) (div/span used as a button, no role)",
        "(a.skip-link) (no accessible name)",
        "(span.skip-link) (no accessible name)",
        "\"Search Keyword, SKU, Product ID\" (span.skip-link) (div/span used as a button, no role)",
        "(span.skip-link) (no accessible name)",
        "(div.action) (no accessible name)",
        "(span.action) (no accessible name)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "30 of 31 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": [
        "logo.svg \"The Cary Company\"",
        "loader-1.gif \"<?= /* @escapeNotVerifie\"",
        "inventory-pails.jpg",
        "inventory-pails-mobile.jpg",
        "drums.jpg \"Drums\"",
        "plastic-bottles.jpg \"Plastic bottles\""
      ]
    },
    {
      "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 668 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 224 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 28 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": "Links to this page will look bare when shared",
      "detail": "The page is missing its Open Graph title and image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no title and image. A flat grey link gets far fewer clicks than one with an image and headline.",
      "device": "both",
      "tags": [],
      "topic": "og_tags",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "2 potential dead-click targets",
      "detail": "Elements styled like buttons but with no anchor, no <button> wrapper, no role=\"button\", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: \"Account\" (span.skip-link), \"Search Keyword, SKU, Product ID\" (span.skip-link).",
      "device": "both",
      "tags": [
        "Conversion",
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "dead_clicks",
      "confidence": "measured",
      "evidence": [
        "\"Account\" (span.skip-link)",
        "\"Search Keyword, SKU, Product ID\" (span.skip-link)"
      ]
    },
    {
      "severity": "low",
      "title": "No llms.txt file",
      "detail": "No /llms.txt. Optional: some AI tools read this file (Anthropic, Vercel, Stripe, Cloudflare and Hugging Face publish one, and AI coding assistants use it to find docs), so adding one is a cheap courtesy to them. Google has said in writing that Google Search and its AI features do not use llms.txt, so do not expect a search-ranking or AI Overviews benefit from it.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_llms_txt",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No Organization or WebSite schema",
      "detail": "No site-wide Organization or WebSite structured data found on any crawled page. This is the schema that tells Google and AI engines who you are (name, logo, social profiles) for the knowledge panel and brand recognition in AI answers. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.)",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "missing_org_schema",
      "confidence": "measured",
      "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: Content-Security-Policy (the main defense against injected and cross-site scripts); 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": []
    },
    {
      "severity": "low",
      "title": "Some links do not describe where they go",
      "detail": "Links like \"click here\" or \"read more\" tell screen-reader users and search engines nothing about the destination. Lighthouse measured: 1 link found.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "link_text",
      "confidence": "measured",
      "evidence": []
    }
  ]
}