Zong Com: a 8-load mobile teardown
We ran 8 synthetic mobile visits to https://www.zong.com.pk/ and recorded what a real iPhone would experience, then cross-checked against real Chrome users in the field. 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. 161 of 229 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 161 of 229 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 | Page shifts under the visitor's finger as it loads Real Chrome visitors see 0.43 of layout shift on this page. Google's bar for "good" is anything under 0.10, and this is above it. Usually it's images, ads, or fonts loading in without their space reserved. | real-user field data |
| 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 |
| High | Main content is slow to appear on phones For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 4.1 seconds to show up. Google's "good" threshold is 2.5 seconds, and this misses it. That number is also one of the signals Google uses to decide where to rank your page in search. | real-user field data |
| Medium | Page is heavy and slow on mobile data Each visit downloads about 6.8 megabytes — roughly 286 KB of images and 2277 KB of JavaScript across 174 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 | Some text is too small to read on phones 103 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) | 945 ms | Lab |
| FCP (lab median) | 1.1s | Lab |
| LCP (lab median) | 1.2s | Lab |
| Page weight (median) | 6.8 MB | Watch |
| Real LCP (p75, url) | 4.1 s | Poor |
| Real INP (p75) | 278 ms | Needs work |
| Real CLS (p75) | 0.43 | Poor |
Google Lighthouse (lab, mobile): Performance 21, SEO 85, Accessibility 87, Best Practices 73.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience.
03Tiny buttons are hard to tap on mobile
161 of 229 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 86x18 "Online Shop"
- a 86x18 "My Zong App"
- a 86x18 "Recharge"
- a 86x18 "Join Zong 5G"
- a 86x18 "Prepaid"
- a 86x18 "Postpaid"
- a 86x18 "Calculator"
- a 247x23 "MONTHLY PRO MAX PLUS"
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 | Zong 5G Pakistan | Telecommunications | 5G In Affordable Price (62 chars) |
| Meta description | 147 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | 1 block(s) |
| 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 |
|---|---|---|
| Tiny buttons are hard to tap on mobile | Varies | 161 of 229 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and … |
| Page shifts under the visitor's finger as it loads | Varies | Real Chrome visitors see 0.43 of layout shift on this page. Google's bar for "good" is anything under 0.10, and this is above it. Usually… |
| 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… |
| Main content is slow to appear on phones | Varies | For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 4.1 seconds to show up. Google's "good" thre… |
| Page is heavy and slow on mobile data | Varies | Each visit downloads about 6.8 megabytes — roughly 286 KB of images and 2277 KB of JavaScript across 174 separate downloads. On a fast co… |
| Some text is too small to read on phones | Varies | 103 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 s… |
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 zong.com.pk 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, except the CrUX rows, which are real Chrome users. 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.
- This page rotates its content load to load, which is itself a reason a single-shot audit of it is unreliable.
Prepared by Harvv. Generated 2026-05-25T17:40:53.061Z.