What your site is actually doing.

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

## Context
- Site: https://pornhub.com/
- Mobile LCP (lab median): 388 ms
- Desktop LCP (lab median): 366 ms
- Page weight (median): 2.5 MB
- Tap targets under 44px: 47% (60 of 127)
- 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.8s (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.
- 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: 60 of 127 tappable items on this page (47%) 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. 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 89x16 "Cookie Notice", a 101x16 "Lexis Star Show", a 65x16 "Pillow Talk", a 74x16 "Pornhub TV", a 344x22 "Get Ready with me : Asa Akir", a 82x16 "Holly Randall", a 53x16 "Pornhub", a 344x22 "Amateur Couple’s First Time "
How we know: median across loads

### 2. [HIGH] A floating widget is covering a clickable element
Category: Conversion, Accessibility (WCAG)
Why it matters: 7 clickable elements are sitting underneath a fixed overlay (div.modalMTubes over button), 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: button under div.modalMTubes, a "LIVE CAMS" under div.modalMTubes, a "VOD" under div.modalMTubes, a "SEXY CHAT" under div.modalMTubes, a "FLING HOOKUPS 🔥" under div.modalMTubes, a "Pornhub Cares" under div.modalMTubes

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

### 4. [HIGH] Some links cannot be followed by Google
Category: SEO
Why it matters: Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.

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

### 6. [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 1 pages from your sitemap, a partial crawl rather than your full site.)

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

### 8. [MEDIUM] The page has no main heading
Why it matters: There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.

### 9. [MEDIUM] 2 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: name="email" (input) placeholder="Email", name="password" (input) placeholder="Password"

### 10. [MEDIUM] 1 input uses the wrong type attribute
Category: Conversion
Why it matters: Mobile keyboards adapt to the input type (email shows @ key, tel shows numeric pad). Generic type="text" gets a generic keyboard and visitors mis-type. Switch to the correct type.
Exact elements found: name="email" → use type="email"

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

### 12. [MEDIUM] 21 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.globalCookieBanner__close) (no accessible name), (button.gtm-event-age-verification) (no accessible name), (button.gtm-event-age-verification) (no accessible name), (div.moreActionKebabMenuButton) (no accessible name), (div.moreActionKebabMenuButton) (no accessible name), (div.moreActionKebabMenuButton) (no accessible name), (div.moreActionKebabMenuButton) (no accessible name), (div.moreActionKebabMenuButton) (no accessible name)

### 13. [MEDIUM] No XML sitemap found
Why it matters: No sitemap.xml at the standard location and none listed in robots.txt. A sitemap tells search engines every page you want indexed; without it they rely on link discovery and may miss pages.

### 14. [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); X-Content-Type-Options: nosniff (stops MIME-type sniffing attacks). 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.

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

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

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

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

### 19. [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 76 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://pornhub.com/",
  "generated_at": "2026-08-21T19:25:47.983Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 388,
    "desktop_lcp_ms": 366,
    "mobile_ttfb_ms": 171,
    "mobile_fcp_ms": 352,
    "page_weight_kb": 2611
  },
  "finding_count": 19,
  "findings": [
    {
      "severity": "high",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "60 of 127 tappable items on this page (47%) 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. 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": "sampled",
      "evidence": [
        "a 89x16 \"Cookie Notice\"",
        "a 101x16 \"Lexis Star Show\"",
        "a 65x16 \"Pillow Talk\"",
        "a 74x16 \"Pornhub TV\"",
        "a 344x22 \"Get Ready with me : Asa Akir\"",
        "a 82x16 \"Holly Randall\"",
        "a 53x16 \"Pornhub\"",
        "a 344x22 \"Amateur Couple’s First Time \""
      ]
    },
    {
      "severity": "high",
      "title": "A floating widget is covering a clickable element",
      "detail": "7 clickable elements are sitting underneath a fixed overlay (div.modalMTubes over button), 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": [
        "button under div.modalMTubes",
        "a \"LIVE CAMS\" under div.modalMTubes",
        "a \"VOD\" under div.modalMTubes",
        "a \"SEXY CHAT\" under div.modalMTubes",
        "a \"FLING HOOKUPS 🔥\" under div.modalMTubes",
        "a \"Pornhub Cares\" under div.modalMTubes"
      ]
    },
    {
      "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": "Some links cannot be followed by Google",
      "detail": "Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "crawlable",
      "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": "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 1 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": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 2.5 megabytes, roughly 1883 KB of images and 568 KB of JavaScript across 170 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": "The page has no main heading",
      "detail": "There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose.",
      "device": "both",
      "tags": [],
      "topic": "h1",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "2 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": [
        "name=\"email\" (input) placeholder=\"Email\"",
        "name=\"password\" (input) placeholder=\"Password\""
      ]
    },
    {
      "severity": "medium",
      "title": "1 input uses the wrong type attribute",
      "detail": "Mobile keyboards adapt to the input type (email shows @ key, tel shows numeric pad). Generic type=\"text\" gets a generic keyboard and visitors mis-type. Switch to the correct type.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "form_input_type",
      "confidence": "measured",
      "evidence": [
        "name=\"email\" → use type=\"email\""
      ]
    },
    {
      "severity": "medium",
      "title": "Click activity may be invisible inside the Facebook in-app browser",
      "detail": "Patterns on this page (34 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": "21 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.globalCookieBanner__close) (no accessible name)",
        "(button.gtm-event-age-verification) (no accessible name)",
        "(button.gtm-event-age-verification) (no accessible name)",
        "(div.moreActionKebabMenuButton) (no accessible name)",
        "(div.moreActionKebabMenuButton) (no accessible name)",
        "(div.moreActionKebabMenuButton) (no accessible name)",
        "(div.moreActionKebabMenuButton) (no accessible name)",
        "(div.moreActionKebabMenuButton) (no accessible name)"
      ]
    },
    {
      "severity": "medium",
      "title": "No XML sitemap found",
      "detail": "No sitemap.xml at the standard location and none listed in robots.txt. A sitemap tells search engines every page you want indexed; without it they rely on link discovery and may miss pages.",
      "device": "both",
      "tags": [],
      "topic": "missing_sitemap",
      "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); X-Content-Type-Options: nosniff (stops MIME-type sniffing attacks). 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": "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": "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 177 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 76 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    }
  ]
}