Aerthom: a phone-and-desktop teardown
We loaded https://aerthom.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. 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. 17 of 29 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.5s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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.
- Accessible to most visitors. Lighthouse accessibility is 96/100, so screen-reader and contrast basics are largely handled.
- 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 17 of 29 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 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. | identical every load |
| High | Some text is low-contrast and hard to readBoth Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. | identical every load |
| High | JavaScript errors were logged during loadBoth Errors in the console often mean a feature silently broke: a button that does nothing, analytics that did not fire, a form that will not submit. | identical every load |
| Medium | Page is heavy and slow on mobile dataBoth Each visit downloads about 4.1 megabytes — roughly 63 KB of images and 320 KB of JavaScript across 50 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 | The page has no main headingBoth There is no <h1>. Search engines and screen readers use the H1 to understand what the page is about. Add exactly one that states the page's purpose. | identical every load |
| Low | Search-result title is leaving room on the tableBoth Google gives you about 60 characters of headline space in search results. This page is using 7. Adding the value proposition or a relevant keyword gives someone one more reason to click. | identical every load |
| 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. | identical every load |
| Low | Links to this page will look bare when sharedBoth The page is missing its Open Graph title and image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no title and image. A flat grey link gets far fewer clicks than one with an image and headline. | 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 |
| Low | Unused JavaScript is being downloadedBoth 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 153 KiB. | identical every load |
| Low | Unused CSS is being downloadedBoth Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 15 KiB. | identical every load |
| Low | Some links do not describe where they goBoth Links like "click here" or "read more" tell screen-reader users and search engines nothing about the destination. Lighthouse measured: 1 link found. | 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) | 51 ms | 45 ms | Lab |
| FCP (lab median) | 538 ms | 540 ms | Lab |
| LCP (lab median) | 538 ms | 540 ms | Good |
| Page weight (median) | 4.1 MB | 3.3 MB | Watch |
Google Lighthouse (lab): Performance 63 mobile / 97 desktop, SEO 92, Accessibility 96, Best Practices 92.
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
17 of 29 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 49x25 "Skip to main content"
- a 117x26 "Aerthom - Go to homepage"
- button 20x20 "Search"
- button 20x20 "Cart"
- button 18x18 "Open menu"
- a 260x39 ""
- a 260x39 ""
- button 35x844 "Close"
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 | Aerthom (7 chars) |
| Meta description | 16 chars |
| H1 | 0 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | 1 block(s) |
| Open Graph | Incomplete |
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
- Google Analytics tracking brokenBothDev afternoon
- Some text is low-contrast and hard to readBothVaries
- JavaScript errors were logged during loadBothDev afternoon
- Page is heavy and slow on mobile dataBothSmall
- The page has no main headingBothVaries
- Search-result title is leaving room on the tableBoth1 line
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- Links to this page will look bare when sharedBoth1 line
- No email capture or newsletter detectedBothVaries
- No visible contact details (email or phone)BothVaries
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- Some links do not describe where they goBothVaries
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 aerthom.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 17, 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.
- 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 17, 2026.