Voxsolutions: a phone-and-desktop teardown
We loaded https://voxsolutions.co/ 8 times on a simulated iPhone and 4 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. 88 of 128 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 2.4s (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.
- 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 88 of 128 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 loadsBoth 187 of 287 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 | 4 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. | identical every load |
| Medium | Click activity may be invisible inside the Facebook in-app browserBoth Patterns on this page (shadow-DOM markers) tend to suppress click events inside Android Webview and iOS in-app browsers. Visitors arriving from Meta ads may register as zero-interaction sessions even when they're actively using the page. Add a server-side landing tracker (or the Harvv pixel) so you don't lose that audience entirely. | 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 | Some text is too small to read on phonesMobile 61 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 | 2 form fields missing autocomplete hintBoth Browsers can autofill name, email, phone, address from the user's saved profile only when you tell them which field is which via autocomplete="email", autocomplete="name", etc. Faster checkout, fewer typos. | identical every load |
| Low | 9 generic CTA links/buttons ("Click here", "Learn more", "Submit")Both Screen-reader users hear a list of "click here, click here, learn more" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination ("See pricing", "Read the case study"). | identical every load |
| 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 |
"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) | 483 ms | 487 ms | Lab |
| FCP (lab median) | 784 ms | 800 ms | Lab |
| LCP (lab median) | 912 ms | 894 ms | Good |
| Page weight (median) | 1.5 MB | 1.5 MB | OK |
| Real LCP (p75, origin) | 2.4 s | Good | |
| Real INP (p75) | 94 ms | Good | |
| Real CLS (p75) | 0.00 | Good | |
Google Lighthouse (lab): Performance 87 mobile / 100 desktop, SEO 92, Accessibility 90, 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
88 of 128 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 8 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 120x26 "VOX SOLUTIONS"
- button 43x43 "Search"
- button 40x40 "Toggle navigation"
- button 36x36 "Toggle submenu"
- button 36x36 "Toggle submenu"
- button 36x36 "Toggle submenu"
- button 36x36 "Toggle submenu"
- a 342x40 "TrueSignal"
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 | VOX Solutions | The Multi-Vertical Monetisation Platform (56 chars) |
| Meta description | 188 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
- Images without sizes set make the page jump as it loadsBothCSS only
- 4 form fields have no labelBothVaries
- Click activity may be invisible inside the Facebook in-app browserBothVaries
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- Some text is too small to read on phonesMobileCSS only
- 2 form fields missing autocomplete hintBothVaries
- 9 generic CTA links/buttons ("Click here", "Learn more", "Submit")BothVaries
- 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 voxsolutions.co 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
- 8 mobile + 4 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 24, 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 24, 2026.