Trynina: a phone-and-desktop teardown
We loaded https://trynina.co/ 4 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each. 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. 25 of 36 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. The main content paints in about 0.2s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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.
This is one of several Shopify stores we tore down the same way. The same friction repeats on Forgeyourpathai, and we pulled the cross-site pattern together in the Shopify friction tax.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 25 of 36 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. The exact elements we found: paste into Claude, Cursor, or ChatGPT | |
| High | Images without sizes set make the page jump as it loadsBothPerformanceSEO 14 of 21 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. The exact images we found:
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 | 7 potential dead-click targetsBothConversionAccessibility (WCAG)Tracking 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: "Get Started" (div.wp-block-button), "pricing" (span.ns-pill), "how-to" (span.ns-pill). The exact elements we found: paste into Claude, Cursor, or ChatGPT | |
| High | 16 interactive elements have no stable, accessible identityBothAccessibility (WCAG)Tracking These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute. The exact elements we found:
paste into Claude, Cursor, or ChatGPT | |
| High | Meta Pixel (Facebook) is installed but misconfiguredBothTracking 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 | |
| High | Some text is low-contrast and hard to readBothAccessibility (WCAG) Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. paste into Claude, Cursor, or ChatGPT | |
| High | Some buttons have no accessible nameBothAccessibility (WCAG)Tracking A button with only an icon and no label is announced as "button" by screen readers, giving no idea what it does. paste into Claude, Cursor, or ChatGPT | |
| High | Broken internal linksBothSEOConversion 2 internal link targets returned an error (404/410/5xx) or did not respond. Broken links waste crawl budget, frustrate visitors, and leak ranking signal. (Found across a sample of 8 pages from your sitemap, a partial crawl rather than your full site.) The exact examples we found:
paste into Claude, Cursor, or ChatGPT | |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 2.0 megabytes, roughly 684 KB of images and 474 KB of JavaScript across 80 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 |
| Medium | JavaScript crashed while the page was loadingBothConversionTracking 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. The exact errors we found: paste into Claude, Cursor, or ChatGPT | median across loads |
| Medium | 1 form field has no labelBothAccessibility (WCAG)ConversionTracking 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. The exact elements we found: paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth Around 20 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 visible contact details (email or phone)BothConversion 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 | |
| Low | Unused JavaScript is being downloadedBothPerformance Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 107 KiB. paste into Claude, Cursor, or ChatGPT |
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
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 12 ms | 7 ms | Lab |
| FCP (lab median) | 114 ms | 116 ms | Lab |
| LCP (lab median) | 204 ms | 166 ms | Good |
| Page weight (median) | 2.0 MB | 2.0 MB | Watch |
Google Lighthouse (lab): Performance 65 mobile / 90 desktop, SEO 100, Accessibility 80, 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
25 of 36 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 1x1 "Skip to content"
- button 24x24 "Open menu"
- a 107x38 "Get Started"
- button 11x11 "Slide 1"
- button 11x11 "Slide 2"
- button 11x11 "Slide 3"
- button 11x11 "Slide 4"
- button 11x11 (no visible label)
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 | Done-For-You SEO Blog Writing Service - Nina (44 chars) |
| Meta description | 160 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
- Google Analytics tracking brokenBothDev afternoon
- 7 potential dead-click targetsBothCSS only
- 16 interactive elements have no stable, accessible identityBothDev afternoon
- Meta Pixel (Facebook) is installed but misconfiguredBothVaries
- Some text is low-contrast and hard to readBothVaries
- Some buttons have no accessible nameBothVaries
- Broken internal linksBothVaries
- Page is heavy and slow on mobile dataBothSmall
- JavaScript crashed while the page was loadingBothDev afternoon
- 1 form field has no labelBothVaries
- The page loads from a lot of third-party servicesBothDev afternoon
- No visible contact details (email or phone)BothVaries
- Unused JavaScript is being downloadedBothVaries
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 trynina.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
- 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 29, 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 29, 2026.