Ybrpayments: a 4-load mobile teardown
We loaded https://ybrpayments.com/ 4 times on a simulated iPhone and wrote down what a real shopper would see. 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. 6 of 11 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: every finding ranked by impact, the speed numbers compared against real visitors, what a one-off scan still cannot tell you, and a short list of what to fix first.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobile 6 of 11 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 | Images without sizes set make the page jump as it loads 13 of 13 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. | identical every load |
| High | 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. | identical every load |
| Medium | Google is writing your search snippet for you This page has no meta description, so Google grabs whatever text it finds on the page and shows that under your title in search results. Usually it's not the pitch you'd write yourself. Adding a 120–160 character summary is one of the easier wins for search click-through. | identical every load |
| Medium | Page is heavy and slow on mobile data Each visit downloads about 2.4 megabytes — roughly 2179 KB of images and 211 KB of JavaScript across 49 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 | JavaScript crashed while the page was loading 1 script error fired during page load. When a script crashes, buttons sometimes stop working, analytics stop firing, and the visitor has no warning. Worth opening the browser console to find which script failed. | median across loads |
| Low | No canonical tag, so duplicate URLs split the page's ranking 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. | identical every load |
| Low | Some text is too small to read on phones 19 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 |
"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: lab and field side by side
| Metric | Value | Read |
|---|---|---|
| TTFB (lab median) | 161 ms | Lab |
| FCP (lab median) | 522 ms | Lab |
| LCP (lab median) | 626 ms | Lab |
| Page weight (median) | 2.4 MB | Watch |
Google Lighthouse (lab, mobile): Performance 60, SEO 82, Accessibility 82, Best Practices 96.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience. Add a Google API key to light up real-user field data (CrUX) and Lighthouse scores.
03Tiny buttons are hard to tap on mobile
6 of 11 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 120x21 ""
- button 185x35 "OUR TRUSTED PARTNERS"
- a 178x20 ""
- a 55x20 "Careers"
- a 136x20 "Terms & Conditions"
- a 95x20 "Privacy Policy"
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 | Yellow Brick Road Payments - Will simplify and expand point-of-sale financing (77 chars) |
| Meta description | Missing |
| H1 | 0 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | None |
| Open Graph | Incomplete |
05The short list, in priority order
Findings ranked by impact and effort, so the team knows where to start tomorrow.
| Fix | Effort | Why it pays |
|---|---|---|
| Tiny buttons are hard to tap on mobile | Varies | 6 of 11 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and the… |
| Images without sizes set make the page jump as it loads | Varies | 13 of 13 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make ro… |
| Google Analytics tracking broken | Varies | 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 th… |
| Google is writing your search snippet for you | Varies | This page has no meta description, so Google grabs whatever text it finds on the page and shows that under your title in search results. … |
| Page is heavy and slow on mobile data | Varies | Each visit downloads about 2.4 megabytes — roughly 2179 KB of images and 211 KB of JavaScript across 49 separate downloads. On a fast con… |
| JavaScript crashed while the page was loading | Varies | 1 script error fired during page load. When a script crashes, buttons sometimes stop working, analytics stop firing, and the visitor has … |
06What this report cannot tell you
Everything above is from the outside, looking at the page from one simulated device. 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 ybrpayments.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 simulated mobile loads of one URL from a headless Safari profile (iPhone viewport), June 10, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers (no field data was available for this run). 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 10, 2026.