Titanaxesolutions: a 8-load mobile teardown
We ran 8 synthetic mobile visits to https://titanaxesolutions.com/ 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. 19 of 32 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 19 of 32 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 9 of 9 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 |
| Medium | Page is heavy and slow on mobile data Each visit downloads about 3.5 megabytes — roughly 2744 KB of images and 0 KB of JavaScript across 23 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 |
| 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 22 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) | 214 ms | Lab |
| FCP (lab median) | 490 ms | Lab |
| LCP (lab median) | 772 ms | Lab |
| Page weight (median) | 3.5 MB | Watch |
Google Lighthouse (lab, mobile): Performance 48, SEO 92, Accessibility 94, Best Practices 100.
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
19 of 32 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:
- button 40x40 "Open menu"
- a 165x20 "Learn More About Us"
- a 95x20 "Learn More"
- a 95x20 "Learn More"
- a 95x20 "Learn More"
- a 139x20 "View All Services"
- a 117x16 "Explore Solutions"
- a 117x16 "Explore Solutions"
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 - TitanAxe Solutions Ltd | TitanAxe Solutions Ltd (54 chars) |
| Meta description | 268 chars |
| H1 | 1 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | None |
| 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 | 19 of 32 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and th… |
| Images without sizes set make the page jump as it loads | Varies | 9 of 9 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… |
| Page is heavy and slow on mobile data | Varies | Each visit downloads about 3.5 megabytes — roughly 2744 KB of images and 0 KB of JavaScript across 23 separate downloads. On a fast conne… |
| No canonical tag, so duplicate URLs split the page's ranking | Varies | When the same content is reachable at multiple URLs (think tracking parameters or session IDs), Google can split your ranking signal acro… |
| Some text is too small to read on phones | Varies | 22 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 sm… |
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 titanaxesolutions.com 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 25, 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-25T17:55:56.813Z.