Trynina: a 8-load mobile teardown
We ran 8 synthetic mobile visits to https://trynina.co/ and recorded what a real iPhone would experience. No login, no insider access, no pixel installed. Here is what repeated page loads already reveal, separated by how we know it.
TL;DRThe headline read
Of everything we found on this scan, this is the one to start with: Tiny buttons are hard to tap on mobile. 13 of 17 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: the full table of findings tagged by confidence, the lab and field timings side by side, what a single external scan still cannot see, and a short prioritized fix list.
01Findings, highest-impact first
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobile 13 of 17 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 | Google Analytics tracking broken The Google Analytics request failed to complete on every one of the 8 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 3.2 megabytes — roughly 2121 KB of images and 434 KB of JavaScript across 63 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 | Search-result title is leaving room on the table Google gives you about 60 characters of headline space in search results. This page is using 11. Adding the value proposition or a relevant keyword gives someone one more reason to click. | 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: lab and field side by side
| Metric | Value | Read |
|---|---|---|
| TTFB (lab median) | 10 ms | Lab |
| FCP (lab median) | 150 ms | Lab |
| LCP (lab median) | 182 ms | Lab |
| Page weight (median) | 3.2 MB | Watch |
Google Lighthouse (lab, mobile): Performance 28, SEO 92, Accessibility 100, 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
13 of 17 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 1x1 "Skip to content"
- button 24x24 "Open menu"
- a 108x38 "Get Started"
- a 111x42 "Book Demo"
- a 111x42 "Book Demo"
- a 111x42 "Book Demo"
- a 289x38 "Get Started"
- a 289x38 "Get Started"
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 | Home - Nina (11 chars) |
| Meta description | Missing |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | 1 block(s) |
| Open Graph | Title + image |
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 | 13 of 17 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and th… |
| Google Analytics tracking broken | Varies | The Google Analytics request failed to complete on every one of the 8 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 3.2 megabytes — roughly 2121 KB of images and 434 KB of JavaScript across 63 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 … |
| Search-result title is leaving room on the table | Varies | Google gives you about 60 characters of headline space in search results. This page is using 11. Adding the value proposition or a releva… |
06What a single scan cannot see
Everything above is from the outside, looking at the page from one synthetic device. The questions that decide revenue need real visitors. With the Harvv pixel installed (a 16 KB script, zero personal data, no engineering project), within about 72 hours you'd know which buttons real customers tapped and missed, the real rate at which Google Analytics is missing visits, and exactly where mobile shoppers stalled and left. The teardown shows you where to look. The pixel shows you how often it happens, and to whom.
Drop the Harvv pixel on trynina.co and we will turn this teardown into measured behavior: which taps miss, where sessions stall, and the real drop rates. Free to start.
Add the pixel free07Method & limits, stated plainly
- 8 synthetic mobile loads of one URL from a headless Safari profile (iPhone viewport), May 23, 2026. Enough to separate stable defects from noise, not a full-site crawl.
- Lab, not field for the timing numbers (no field data available for this run). Real devices on real networks run slower.
- Friction is inferred, not measured. We can prove a target is small. We cannot, from the outside, prove how often it causes a mis-tap. That needs the pixel.
Prepared by Harvv. Generated 2026-05-23T17:57:48.111Z.