Redo: a phone-and-desktop teardown
We loaded https://redo.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. 31 of 34 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. 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
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobile 31 of 34 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. paste into Claude, Cursor, or ChatGPT | |
| High | Images without sizes set make the page jump as it loadsBoth 93 of 96 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make room. The visitor goes to tap one thing and ends up tapping another, and the cause is invisible to them. paste into Claude, Cursor, or ChatGPT | |
| High | Google Analytics tracking brokenBoth 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. paste into Claude, Cursor, or ChatGPT | |
| High | 16 potential dead-click targetsBoth 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: "Returns & Claims" (div.rp-product-btn), "AI Sales & Support" (div.rp-product-btn), "Conversion Optimization" (div.rp-product-btn). paste into Claude, Cursor, or ChatGPT | |
| High | 3 form fields have 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. paste into Claude, Cursor, or ChatGPT | |
| High | Meta Pixel (Facebook) is installed but misconfiguredBoth 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. paste into Claude, Cursor, or ChatGPT | |
| Medium | Page is heavy and slow on mobile dataBoth Each visit downloads about 5.1 megabytes — roughly 3219 KB of images and 1261 KB of JavaScript across 191 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. paste into Claude, Cursor, or ChatGPT | median across loads |
| Low | No canonical tag, so duplicate URLs split the page's rankingBoth When the same content is reachable at multiple URLs (think tracking parameters or session IDs), Google can split your ranking signal across them. A single canonical tag tells Google which version counts. paste into Claude, Cursor, or ChatGPT | |
| Low | The page has 7 top-level headingsBoth Multiple <h1> tags blur which heading is the main one. Keep one H1 and demote the rest to H2 so the page's structure is clear. paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth Around 45 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. paste into Claude, Cursor, or ChatGPT | 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. paste into Claude, Cursor, or ChatGPT | |
| 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. paste into Claude, Cursor, or ChatGPT |
"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.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 101 ms | 120 ms | Lab |
| FCP (lab median) | 484 ms | 522 ms | Lab |
| LCP (lab median) | 484 ms | 522 ms | Good |
| Page weight (median) | 5.1 MB | 5.3 MB | Watch |
| Real LCP (p75, url) | 1.9 s | Good | |
| Real INP (p75) | 146 ms | Good | |
| Real CLS (p75) | 0.00 | Good | |
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
31 of 34 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 175x39 "Operations"
- a 175x39 "Marketing"
- a 175x39 "Conversion"
- a 175x39 "Support"
- a 122x26 (no visible label)
- a 155x40 "Returns & Claims"
- a 155x40 "Warranties"
- a 155x40 "Chargebacks"
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 | Redo - Elevate your shopper experience (38 chars) |
| Meta description | 147 chars |
| H1 | 7 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | SoftwareApplication |
| 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
- Images without sizes set make the page jump as it loadsBothCSS only
- Google Analytics tracking brokenBothDev afternoon
- 16 potential dead-click targetsBothCSS only
- 3 form fields have no labelBothVaries
- Meta Pixel (Facebook) is installed but misconfiguredBothVaries
- Page is heavy and slow on mobile dataBothSmall
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- The page has 7 top-level headingsBothVaries
- 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
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 redo.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 23, 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 23, 2026.