Cluely: a phone-and-desktop teardown
We loaded https://cluely.com/ 4 times on a simulated iPhone and 2 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. 43 of 51 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:
- 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.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 43 of 51 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 5.0 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 | 3 form fields have no labelBothAccessibility (WCAG)ConversionTracking | identical every load |
| High | 6 interactive elements have no stable, accessible identityBothAccessibility (WCAG)Tracking 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. | identical every load |
| High | Meta Pixel (Facebook) is installed but misconfiguredBothTracking Meta Pixel installed but no Lead/Purchase/Checkout event fires on this page, only PageView. Your Meta ad sessions can't be optimized for conversions until you track at least one downstream event. | identical every load |
| High | Some text is low-contrast and hard to readBothAccessibility (WCAG) Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. | identical every load |
| High | Some buttons have no accessible nameBothAccessibility (WCAG)Tracking A button with only an icon and no label is announced as "button" by screen readers, giving no idea what it does. | identical every load |
| High | Broken internal linksBothSEOConversion 1 internal link target returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.) The exact examples we found:
| identical every load |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 2.1 megabytes, roughly 798 KB of images and 156 KB of JavaScript across 64 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 | No analytics installed, so you cannot see your own trafficBothTracking 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 | Some text is too small to read on phonesMobileAccessibility (WCAG)Conversion 37 chunks of text come in under 12 pixels on this page. Most visitors don't zoom, they just skim past anything that small. Bumping the smallest body text to 14 pixels makes the page read without effort. | median across loads |
| Low | Search-result title will be cut offBothSEO The title is 76 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped. | identical every load |
| Low | No email capture or newsletter detectedBothConversion 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 | Unused JavaScript is being downloadedBothPerformance 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 200 KiB. | identical every load |
| Low | No llms.txt fileBothSEO No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site. | identical every load |
| Low | No Organization or WebSite schemaBothSEO 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.) | identical every load |
| Low | No HSTS (Strict-Transport-Security)BothSEO No Strict-Transport-Security header on any crawled page. HSTS forces browsers to always use https for your domain, preventing protocol-downgrade and cookie-hijacking attacks. Add it to your server or CDN response headers. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.) | identical every load |
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": 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.
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
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 26 ms | 26 ms | Lab |
| FCP (lab median) | 248 ms | 240 ms | Lab |
| LCP (lab median) | 3.2s | 408 ms | Needs work |
| Page weight (median) | 2.1 MB | 6.2 MB | Watch |
| Real LCP (p75, url) | 5.0 s | Poor | |
| Real INP (p75) | 344 ms | Needs work | |
| Real CLS (p75) | 0.00 | Good | |
Google Lighthouse (lab): Performance 69 mobile / 74 desktop, SEO 100, Accessibility 86, Best Practices 100.
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
43 of 51 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 4 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 84x22 "Cluely"
- button 24x24 "Open menu"
- button 193x40 "Get the desktop app"
- button 68x31 "Hide"
- button 31x31 "Stop session"
- button 66x29 "Assist"
- button 134x29 "What should I say?"
- button 51x21 "Smart"
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 | Cluely - Live AI Meeting Assistant | Real-Time Meeting Notes and AI Insights (76 chars) |
| Meta description | 176 chars |
| H1 | 1 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
- 3 form fields have no labelBothVaries
- 6 interactive elements have no stable, accessible identityBothDev afternoon
- Meta Pixel (Facebook) is installed but misconfiguredBothVaries
- Some text is low-contrast and hard to readBothVaries
- Some buttons have no accessible nameBothVaries
- Broken internal linksBothVaries
- Page is heavy and slow on mobile dataBothSmall
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- Some text is too small to read on phonesMobileCSS only
- Search-result title will be cut offBoth1 line
- No email capture or newsletter detectedBothVaries
- Unused JavaScript is being downloadedBothVaries
- No llms.txt fileBothVaries
- No Organization or WebSite schemaBothVaries
- No HSTS (Strict-Transport-Security)BothVaries
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 cluely.com 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
- 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 29, 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.
Prepared by Harvv. Last updated June 29, 2026.