What your site is actually doing.

Audit of https://www.seoloupe.com/, run August 9, 2026. 12 issues were found. I want them fixed.

## Context
- Site: https://www.seoloupe.com/
- Mobile LCP (lab median): 158 ms
- Desktop LCP (lab median): 174 ms
- Page weight (median): 0.6 MB
- Tap targets under 44px: 31% (22 of 70)
- Evidence base: 4 mobile + 2 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: Real Chrome visitors see the main content in 1.2s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Light page weight: The page is about 0.6 MB across 26 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- 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] Google Analytics tracking broken
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.

### 2. [HIGH] 3 form fields have no label
Category: Accessibility (WCAG), Conversion, Tracking
Why it matters: Screen readers can't announce these fields, and a sighted user who clears the placeholder can't recover the prompt. Wrap each input in <label>…</label> or add aria-label.
Exact elements found: (input) placeholder="website.com (Optional)", (input) placeholder="website.com (Optional)", (input) placeholder="website.com (Optional)"

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

### 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. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 22 of 70 tappable items on this page (31%) 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: a 130x17 "SeoLoupe Logo", a 330x17 "Buy Once", a 330x17 "Upgrade", a 330x17 "Upgrade", a 150x17 "SeoLoupe Logo", a 105x17 "Features", a 105x17 "How it Works", a 105x17 "Pricing"

### 6. [MEDIUM] Click activity may be invisible inside the Facebook in-app browser
Category: Tracking
Why it matters: Patterns on this page (15 inline onclick handlers) 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.

### 7. [MEDIUM] 15 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: (div) (no accessible name), (div) (no accessible name), "What does this tool do?" (div) (div/span used as a button, no role), "What is GEO and AEO?" (div) (div/span used as a button, no role), "Who is this tool for?" (div) (div/span used as a button, no role), "Do I need SEO experience to use it?" (div) (div/span used as a button, no role), "How does the SEO scan work?" (div) (div/span used as a button, no role), "What makes this different from other SEO" (div) (div/span used as a button, no role)

### 8. [LOW] Images have no width or height set (layout is stable for now)
Category: Performance, SEO
Why it matters: 48 of 49 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: seoloupe_logo-removebg-preview.svg "SeoLoupe Logo", icon6.png "Google Logo", icon2.png "ChatGPT logo", icon1.png "Claude logo", google-gemini-icon.e6fb2cbeb2e04a07cea631da18183c40.svg "Gemini logo", grok-logo.png "Grok logo"

### 9. [LOW] No advertising pixel detected
Category: Tracking
Why it matters: Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.

### 10. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.

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

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

## 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://www.seoloupe.com/",
  "generated_at": "2026-08-21T19:25:50.336Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 158,
    "desktop_lcp_ms": 174,
    "mobile_ttfb_ms": 20,
    "mobile_fcp_ms": 158,
    "page_weight_kb": 625
  },
  "finding_count": 12,
  "findings": [
    {
      "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": [],
      "topic": null,
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "3 form fields have no label",
      "detail": "Screen readers can't announce these fields, and a sighted user who clears the placeholder can't recover the prompt. Wrap each input in <label>…</label> or add aria-label.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion",
        "Tracking"
      ],
      "topic": "form_labels",
      "confidence": "measured",
      "evidence": [
        "(input) placeholder=\"website.com (Optional)\"",
        "(input) placeholder=\"website.com (Optional)\"",
        "(input) placeholder=\"website.com (Optional)\""
      ]
    },
    {
      "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": "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": "medium",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "22 of 70 tappable items on this page (31%) 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": [
        "a 130x17 \"SeoLoupe Logo\"",
        "a 330x17 \"Buy Once\"",
        "a 330x17 \"Upgrade\"",
        "a 330x17 \"Upgrade\"",
        "a 150x17 \"SeoLoupe Logo\"",
        "a 105x17 \"Features\"",
        "a 105x17 \"How it Works\"",
        "a 105x17 \"Pricing\""
      ]
    },
    {
      "severity": "medium",
      "title": "Click activity may be invisible inside the Facebook in-app browser",
      "detail": "Patterns on this page (15 inline onclick handlers) 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": "15 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": [
        "(div) (no accessible name)",
        "(div) (no accessible name)",
        "\"What does this tool do?\" (div) (div/span used as a button, no role)",
        "\"What is GEO and AEO?\" (div) (div/span used as a button, no role)",
        "\"Who is this tool for?\" (div) (div/span used as a button, no role)",
        "\"Do I need SEO experience to use it?\" (div) (div/span used as a button, no role)",
        "\"How does the SEO scan work?\" (div) (div/span used as a button, no role)",
        "\"What makes this different from other SEO\" (div) (div/span used as a button, no role)"
      ]
    },
    {
      "severity": "low",
      "title": "Images have no width or height set (layout is stable for now)",
      "detail": "48 of 49 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": [
        "seoloupe_logo-removebg-preview.svg \"SeoLoupe Logo\"",
        "icon6.png \"Google Logo\"",
        "icon2.png \"ChatGPT logo\"",
        "icon1.png \"Claude logo\"",
        "google-gemini-icon.e6fb2cbeb2e04a07cea631da18183c40.svg \"Gemini logo\"",
        "grok-logo.png \"Grok logo\""
      ]
    },
    {
      "severity": "low",
      "title": "No advertising pixel detected",
      "detail": "Analytics is present but no Meta/Google/TikTok ad pixel was found. If you run paid ads, conversion tracking should be installed before the next campaign so the platforms can optimize toward buyers, not clicks.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "no_ad_pixel",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_email_capture",
      "confidence": "measured",
      "evidence": []
    },
    {
      "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 75 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 30 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    }
  ]
}