Pornhub: a phone-and-desktop teardown

TL;DRWhat jumped out

Of everything we found on this scan, this is the one to start with: Tiny buttons are hard to tap on mobile. 61 of 126 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.

Below: what's already working, every finding ranked by impact and tagged with the screen it affects, the speed numbers on phone and desktop, and a checklist of what to fix first.

00What's already working

Start here so the problems below are in context. These held up across the test loads:

• Speed is good. Real Chrome visitors see the main content in 1.9s (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.

01Findings, ranked by what hurts conversion most

Accessibility findings are automated checks against Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2. They flag potential barriers and legal risk, not a certification or a determination of compliance with the ADA, Section 508, or EN 301 549. Automated testing catches only a subset of issues; a full conformance review needs manual and assistive-technology testing by a qualified reviewer.

"How we know": unlabeled = a deterministic fact, identical on every load (e.g. element sizes). Most findings are this kind, so we only mark the exceptions: median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.

Structural and AI-search checks crawl up to 8 pages from your sitemap (a sample, not your full site). "Broken" means a link returned 404, 410, or 5xx, or did not respond; access-controlled pages (401, 403) are not counted.

02Performance: phone, desktop, and real visitors

Google Lighthouse (lab): Performance 63 mobile / 95 desktop, SEO 85, Accessibility 83, Best Practices 81.

Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience.

03Tiny buttons are hard to tap on mobile

61 of 126 tappable items on this page come in below 44×44 pixels, the size Apple and Google both recommend for reliable tapping on a phone.

The buttons measuring below the minimum on this scan:

• a 89x16 "Cookie Notice"
• a 107x16 "Quarantine Qribs"
• a 344x22 "Quarantine Qribs - Valentina"
• a 74x16 "Pornhub TV"
• a 344x22 "Get Ready with me : Asa Akir"
• a 101x16 "Lexis Star Show"
• a 74x16 "Pornhub TV"
• a 53x16 "Pornhub"

The fix is CSS-only on most sites: add padding around the icon (don't just change the icon size) so the actual tap area is at least 44×44 pixels. No redesign, no new assets.

04Technical SEO & structured data

05The fix checklist

Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.

1. Tiny buttons are hard to tap on mobileMobileCSS only
2. A floating widget is covering a clickable elementBothCSS only
3. Google Analytics tracking brokenBothDev afternoon
4. Some links cannot be followed by GoogleBothVaries
5. Some buttons have no accessible nameBothVaries
6. Add quotations so AI engines cite this pageBothVaries
7. Page is heavy and slow on mobile dataBothSmall
8. The page has no main headingBothVaries
9. 2 form fields have no labelBothVaries
10. 1 input uses the wrong type attributeBothVaries
11. Click activity may be invisible inside the Facebook in-app browserBothVaries
12. 22 interactive elements have no stable, accessible identityBothDev afternoon
13. Security headers are missing or weakBothVaries
14. Some text is too small to read on phonesMobileCSS only
15. Links to this page will look bare when sharedBoth1 line
16. No advertising pixel detectedBothDev afternoon
17. No email capture or newsletter detectedBothVaries
18. Unused JavaScript is being downloadedBothVaries
19. Unused CSS is being downloadedBothVaries
20. Sitemap not listed in robots.txtBothVaries

Effort is a rough read from the outside: "CSS only" means no new assets or backend work, "1 line" means a single tag, "Dev afternoon" means a developer needs to touch tracking or scripts.

06What this report cannot tell you

Everything above is from the outside, looking at the page on a simulated phone and desktop. The questions that actually decide revenue need real visitors. Install the Harvv pixel (one script tag, 16 KB, zero personal data, no engineering project) and within about 72 hours you'd know which buttons real customers tapped and missed, how often Google Analytics is missing visits, and exactly where mobile shoppers stalled and left. This report shows you where to look. The pixel shows you how often it happens, and to whom.

07How we did this, and what it can't prove

• 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), July 18, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
• Lab numbers, not real-user numbers, except the CrUX rows, which are real Chrome users. Real devices on real networks run slower.
• Friction is inferred, not counted. We can prove a button is small. We can't, from the outside, count how often it causes a missed tap. That requires the pixel on a live page.
• This page rotates its content load to load, which is on its own a reason a single-shot scan can't be the last word on it.

Prepared by Harvv (harvv.com), a behavioral UX analytics platform. Last updated July 18, 2026.