Claude Ai: a phone-and-desktop teardown
We loaded https://claude.ai/ 6 times on a simulated iPhone and 3 more on a 1366px desktop, and wrote down what a real visitor would see on each, then cross-checked it against real Chrome users from Google's field data. No login, no insider access, no Harvv pixel needed. Here is what repeated visits already show, sorted by how we know it.
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. 132 of 143 tappable items on this page come in below 44×44 pixels, the minimum size 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.
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. The main content paints in about 1.0s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- Layout stays put as it loads. Real visitors see only 0.09 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- Search basics are in place. Lighthouse scores SEO 92/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.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobile 132 of 143 tappable items on this page come in below 44×44 pixels, the minimum size 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. | identical every load |
| High | Main content is slow to appear on phonesBoth For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 6.7 seconds to show up. Google's "good" threshold is 2.5 seconds, and this misses it. That number is also one of the signals Google uses to decide where to rank your page in search. | real-user field data |
| High | JavaScript errors were logged during loadBoth Errors in the console often mean a feature silently broke: a button that does nothing, analytics that did not fire, a form that will not submit. | identical every load |
| Medium | Page is heavy and slow on mobile dataBoth Each visit downloads about 31.5 megabytes — roughly 0 KB of images and 3692 KB of JavaScript across 126 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. | median across loads |
| Medium | The page has no main headingBoth 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. | identical every load |
| Medium | 1 potential dead-click targetBoth 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: "New" (span.inline-flex). | identical every load |
| Medium | 1 form field has no labelBoth 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. | identical every load |
| Medium | No analytics installed, so you cannot see your own trafficBoth No Google Analytics, GA4, or any analytics tag was detected. There is no way to know how many visitors arrive, where they come from, or what converts, and no data to retarget or measure a campaign against. Installing GA4 (free) is the baseline. | identical every load |
| Low | Search-result title is leaving room on the tableBoth Google gives you about 60 characters of headline space in search results. This page is using 16. Adding the value proposition or a relevant keyword gives someone one more reason to click. | identical every load |
| Low | The page loads from a lot of third-party servicesBoth Around 16 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. | median across loads |
| Low | No email capture or newsletter detectedBoth No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. Email capture plus a welcome and abandoned-cart flow is consistently the highest-ROI addition for a small store, and it is owned audience you keep regardless of ad costs. | identical every load |
| Low | No visible contact details (email or phone)Both The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer. | identical every load |
| Low | Unused JavaScript is being downloadedBoth 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 2,898 KiB. | identical every load |
"How we know": identical every load = a deterministic fact (e.g. element sizes). median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 23 ms | 24 ms | Lab |
| FCP (lab median) | 988 ms | 996 ms | Lab |
| LCP (lab median) | 988 ms | 996 ms | Good |
| Page weight (median) | 31.5 MB | 31.4 MB | Watch |
| Real LCP (p75, url) | 6.7 s | Poor | |
| Real INP (p75) | 716 ms | Poor | |
| Real CLS (p75) | 0.09 | Good | |
Google Lighthouse (lab): Performance 27 mobile / 28 desktop, SEO 92, Accessibility 100, Best Practices 77.
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
132 of 143 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 same ones came up small on every one of the 6 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- button 24x24 "Toggle menu"
- button 24x24 "Close menu"
- button 326x42 (no visible label)
- a 326x23 (no visible label)
- a 326x23 (no visible label)
- a 326x23 (no visible label)
- a 326x23 (no visible label)
- a 326x23 (no visible label)
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
| Check | Result |
|---|---|
| Title | Sign in - Claude (16 chars) |
| Meta description | 64 chars |
| H1 | 0 on page |
| Canonical | Present |
| Structured data (JSON-LD) | 1 block(s) |
| Open Graph | Title + image |
05The fix checklist
Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.
- Tiny buttons are hard to tap on mobileMobileCSS only
- Main content is slow to appear on phonesBothSmall
- JavaScript errors were logged during loadBothDev afternoon
- Page is heavy and slow on mobile dataBothSmall
- The page has no main headingBothVaries
- 1 potential dead-click targetBothCSS only
- 1 form field has no labelBothVaries
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- Search-result title is leaving room on the tableBoth1 line
- The page loads from a lot of third-party servicesBothDev afternoon
- No email capture or newsletter detectedBothVaries
- No visible contact details (email or phone)BothVaries
- Unused JavaScript is being downloadedBothVaries
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.
Drop the Harvv pixel on claude.ai and we turn this one-off scan into ongoing measured behavior: which taps miss, where sessions stall, and the real drop rates. Free to start, no card needed.
Add the pixel free07How we did this, and what it can't prove
- 6 mobile + 3 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 21, 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. Last updated June 21, 2026.