Seoloupe: a phone-and-desktop teardown

TL;DRWhat jumped out

Of everything we found on this scan, this is the one to start with: Google Analytics tracking broken. 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.

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.1s (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.7 MB across 39 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.

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 66 mobile / 99 desktop, SEO 100, Accessibility 88, Best Practices 96.

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

22 of 59 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 130x17 "SeoLoupe Logo"
• a 328x17 "Buy Once"
• a 328x17 "Upgrade"
• a 328x17 "Upgrade"
• a 150x17 "SeoLoupe Logo"
• a 105x17 "Features"
• a 105x17 "How it Works"
• a 105x17 "Pricing"

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. Google Analytics tracking brokenBothDev afternoon
2. 3 form fields have no labelBothVaries
3. Some text is low-contrast and hard to readBothVaries
4. Add quotations so AI engines cite this pageBothVaries
5. Broken internal linksBothVaries
6. Tiny buttons are hard to tap on mobileMobileCSS only
7. Structured data on the page is brokenBothVaries
8. Click activity may be invisible inside the Facebook in-app browserBothVaries
9. 11 interactive elements have no stable, accessible identityBothDev afternoon
10. Images have no width or height set (layout is stable for now)BothCSS only
11. Links to this page will look bare when sharedBothVaries
12. No advertising pixel detectedBothDev afternoon
13. No email capture or newsletter detectedBothVaries
14. Unused JavaScript is being downloadedBothVaries
15. Unused CSS is being downloadedBothVaries
16. No Organization or WebSite schemaBothVaries

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 9, 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 (harvv.com), a behavioral UX analytics platform. Last updated July 9, 2026.