Eco Host: a 4-load mobile teardown
We loaded https://eco-host.net/ 4 times on a simulated iPhone and wrote down what a real shopper would see. 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: Images without sizes set make the page jump as it loads. 43 of 43 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.
Below: every finding ranked by impact, the speed numbers compared against real visitors, what a one-off scan still cannot tell you, and a short list of what to fix first.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Images without sizes set make the page jump as it loads 43 of 43 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 |
| 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 12 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) | 29 ms | Lab |
| FCP (lab median) | 258 ms | Lab |
| LCP (lab median) | 1.6s | Lab |
| Page weight (median) | 0.1 MB | OK |
Google Lighthouse (lab, mobile): Performance 49, SEO 91, Accessibility 93, 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
2 of 15 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:
- button 134x42 "Create Account"
- button 134x42 "Log In"
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 | Eco — Recycle. Earn. Level Up. (30 chars) |
| Meta description | 109 chars |
| H1 | 1 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | None |
| Open Graph | Incomplete |
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 |
|---|---|---|
| Images without sizes set make the page jump as it loads | Varies | 43 of 43 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make ro… |
| 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 | 12 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 this report cannot tell you
Everything above is from the outside, looking at the page from one simulated device. 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 eco-host.net 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 simulated mobile loads of one URL from a headless Safari profile (iPhone viewport), June 15, 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 15, 2026.