Zong Com: a phone-and-desktop teardown
We loaded https://www.zong.com.pk/ 4 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each, then cross-checked it against real Chrome users from Google's field data. 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: 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.
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 1.3s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- 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 | Page shifts under the visitor's finger as it loadsBoth 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. paste into Claude, Cursor, or ChatGPT | real-user field data |
| 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 | Main content is slow to appear on phonesBoth For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 4.4 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. paste into Claude, Cursor, or ChatGPT | real-user field data |
| 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 links cannot be followed by GoogleBothSEO Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed. paste into Claude, Cursor, or ChatGPT | |
| High | JavaScript errors were logged during loadBothConversionTracking 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. paste into Claude, Cursor, or ChatGPT | |
| High | Add quotations so AI engines cite this pageBothAI SearchSEO Generative engines (ChatGPT, Perplexity, AI Overviews) lift sourced, attributed quotes almost verbatim, and quotations are the single strongest citation lever (studies measure roughly +41%). Add 1-2 attributed expert quotes or blockquotes to the pages below. (Found across a sample of 1 pages from your sitemap, a partial crawl rather than your full site.) paste into Claude, Cursor, or ChatGPT | |
| Medium | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 69 of 229 tappable items on this page (30%) measure under 24 pixels on their shorter side, below the WCAG minimum, and well under the 44 pixels 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 | |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 6.7 megabytes, roughly 237 KB of images and 2241 KB of JavaScript across 175 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 | The server is slow to respondBothPerformance The first byte took about 1.1 seconds to arrive across 4 loads on a clean connection. Everything else on the page waits behind that. It usually points at slow server-side rendering, an overloaded host, or a missing cache. 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 | |
| Medium | 7 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 | |
| Low | Some text is too small to read on phonesMobileAccessibility (WCAG)Conversion 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. paste into Claude, Cursor, or ChatGPT | median across loads |
| Low | Links to this page will look bare when sharedBoth The page is missing its Open Graph image, so when someone shares it on Facebook, LinkedIn, iMessage, or Slack the preview has no image. A flat grey link gets far fewer clicks than one with an image and headline. paste into Claude, Cursor, or ChatGPT | |
| Low | The page loads from a lot of third-party servicesBoth Around 30 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 | 40 generic CTA links/buttons ("Click here", "Learn more", "Submit")BothAccessibility (WCAG)Conversion Screen-reader users hear a list of "click here, click here, learn more" with no context. Sighted users learn nothing about where the link goes from the label alone. Rewrite each CTA to describe the destination ("See pricing", "Read the case study"). The exact elements we found: paste into Claude, Cursor, or ChatGPT | |
| Low | No email capture or newsletter detectedBothConversion No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. If capturing visitors is relevant to this site, an email signup builds an owned audience you keep regardless of ad costs. Not every site needs one. paste into Claude, Cursor, or ChatGPT | |
| 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 1,283 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | Unused CSS is being downloadedBothPerformance Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 184 KiB. paste into Claude, Cursor, or ChatGPT | |
| Low | Headings skip levelsBothAccessibility (WCAG) Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on. 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) | 1.1s | 843 ms | Lab |
| FCP (lab median) | 1.2s | 946 ms | Lab |
| LCP (lab median) | 1.3s | 1.5s | Good |
| Page weight (median) | 6.7 MB | 7.1 MB | Watch |
| Real LCP (p75, url) | 4.4 s | Poor | |
| Real INP (p75) | 324 ms | Needs work | |
| Real CLS (p75) | 0.43 | Poor | |
Google Lighthouse (lab): Performance 19 mobile / 45 desktop, SEO 85, Accessibility 88, 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
69 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 4 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 fix checklist
Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.
- Page shifts under the visitor's finger as it loadsBothVaries
- Google Analytics tracking brokenBothDev afternoon
- Main content is slow to appear on phonesBothSmall
- Meta Pixel (Facebook) is installed but misconfiguredBothVaries
- Some text is low-contrast and hard to readBothVaries
- Some links cannot be followed by GoogleBothVaries
- JavaScript errors were logged during loadBothDev afternoon
- Add quotations so AI engines cite this pageBothVaries
- Tiny buttons are hard to tap on mobileMobileCSS only
- Page is heavy and slow on mobile dataBothSmall
- The server is slow to respondBothSmall
- 1 form field has no labelBothVaries
- 7 interactive elements have no stable, accessible identityBothDev afternoon
- Some text is too small to read on phonesMobileCSS only
- Links to this page will look bare when sharedBothVaries
- The page loads from a lot of third-party servicesBothDev afternoon
- 40 generic CTA links/buttons ("Click here", "Learn more", "Submit")BothVaries
- No email capture or newsletter detectedBothVaries
- No visible contact details (email or phone)BothVaries
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- Headings skip levelsBothVaries
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 zong.com.pk 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), July 30, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers, except the CrUX rows, which are real Chrome users. 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.
About Harvv, the source of this teardown
Harvv is a behavioral UX analytics platform (harvv.com). A lightweight JavaScript pixel captures how real visitors behave on a site (dead clicks, rage clicks, scroll depth, Core Web Vitals, JavaScript errors, and 50+ other signals) and the engine turns them into prioritized, plain-English findings. This teardown is the outside-in version of that: the same detectors run against a public page, with no pixel installed.
How to read it. Every finding here is a reproducible, automated measurement, not an opinion: element sizes, contrast ratios, load metrics, and structured-data checks that anyone can re-run against the same URL. The method is stated in full above. Automated testing catches a subset of issues, so this is a starting point, not a certification.
Full disclosure. Harvv makes the pixel that would measure the friction these findings imply, so we have a commercial interest. That is exactly why the findings are kept to things a reader can verify independently, and why nothing here is inflated: an unreproducible claim would undermine the tool it is meant to demonstrate.
Prepared by Harvv (harvv.com), a behavioral UX analytics platform. Last updated July 30, 2026.