What your site is actually doing.

Audit of https://www.zong.com.pk/, run August 30, 2026. 20 issues were found. I want them fixed.

## Context
- Site: https://www.zong.com.pk/
- Mobile LCP (lab median): 1176 ms
- Desktop LCP (lab median): 1478 ms
- Page weight (median): 7.0 MB
- Tap targets under 44px: 30% (69 of 229)
- Evidence base: 4 mobile + 2 desktop loads + Google CrUX field data

## Already working, do not change these
- Speed is good: The main content paints in about 1.2s 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.
- Layout holds on phone and desktop: Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.

## Issues, most damaging first

### 1. [HIGH] Meta Pixel (Facebook) is installed but misconfigured
Category: Tracking
Why it matters: 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.

### 2. [HIGH] Some links cannot be followed by Google
Category: SEO
Why it matters: Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.

### 3. [HIGH] Add quotations so AI engines cite this page
Category: AI Search, SEO
Why it matters: 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.)

### 4. [HIGH] Google Analytics tracking broken
Category: Tracking, Conversion
Why it matters: 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.

### 5. [HIGH] Page shifts under the visitor's finger as it loads
Why it matters: Real Chrome visitors see 0.48 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.
How we know: real-user field data

### 6. [HIGH] Some text is low-contrast and hard to read
Category: Accessibility (WCAG)
Why it matters: Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.

### 7. [MEDIUM] Tiny buttons are hard to tap on mobile
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 69 of 229 tappable items on this page (30%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) 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.
Exact elements found: 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"

### 8. [MEDIUM] Page is heavy and slow on mobile data
Category: Performance
Why it matters: Each visit downloads about 7.0 megabytes, roughly 338 KB of images and 2331 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.
How we know: median across loads

### 9. [MEDIUM] The server is slow to respond
Category: Performance
Why it matters: The first byte took about 0.9 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.
How we know: median across loads

### 10. [MEDIUM] 1 form field has no label
Category: Accessibility (WCAG), Conversion, Tracking
Why it matters: 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.
Exact elements found: name="g-recaptcha-response" (textarea)

### 11. [MEDIUM] Main content is slow to appear on phones
Why it matters: For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 3.8 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.
How we know: real-user field data

### 12. [MEDIUM] 7 interactive elements have no stable, accessible identity
Category: Accessibility (WCAG), Tracking
Why it matters: 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.
Exact elements found: "clear results" (div.gsc-clear-button) (div/span used as a button, no role), (div.gsc-results-close-btn) (no accessible name), (a) (no accessible name), "clear results" (div.gsc-clear-button) (div/span used as a button, no role), (div.gsc-results-close-btn) (no accessible name), (img.pushDataLayer) (no accessible name), (span.close-button) (no accessible name)

### 13. [LOW] Unused JavaScript is being downloaded
Category: Performance
Why it matters: 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,268 KiB.

### 14. [LOW] Unused CSS is being downloaded
Category: Performance
Why it matters: Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 165 KiB.

### 15. [LOW] The page loads from a lot of third-party services
Why it matters: 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.
How we know: median across loads

### 16. [LOW] No email capture or newsletter detected
Category: Conversion
Why it matters: No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.

### 17. [LOW] Links to this page will look bare when shared
Why it matters: 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.

### 18. [LOW] 40 generic CTA links/buttons ("Click here", "Learn more", "Submit")
Category: Accessibility (WCAG), Conversion
Why it matters: 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").
Exact elements found: "Read More" (a), "Read More" (a), "Read More" (a), "Read More" (a), "Read More" (a)

### 19. [LOW] Headings skip levels
Category: Accessibility (WCAG)
Why it matters: Skipping a heading level breaks the document outline that screen readers and search engines rely on. On this page the outline jumps to an H4 without the level above it, at "Choose an option". Lighthouse flagged 1 heading out of order.

### 20. [LOW] Some text is too small to read on phones
Affects: mobile only
Category: Accessibility (WCAG), Conversion
Why it matters: 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.
How we know: median across loads

## How to respond
Work through the issues in order. For each one give me the specific change that fixes it: real code or real copy, not advice. Keep changes minimal and match the existing style of the site.
Where several issues share one root cause, say so and fix it once rather than patching each symptom.
If an issue cannot be fixed without seeing more of the code, say exactly which file or selector you need instead of guessing.

{
  "generated_by": "Harvv",
  "report_url": "https://www.zong.com.pk/",
  "generated_at": "2026-08-30T03:42:57.027Z",
  "evidence_base": {
    "mobile_loads": 4,
    "desktop_loads": 2,
    "field_data": true,
    "lighthouse": true
  },
  "performance": {
    "mobile_lcp_ms": 1176,
    "desktop_lcp_ms": 1478,
    "mobile_ttfb_ms": 882,
    "mobile_fcp_ms": 1030,
    "page_weight_kb": 7119
  },
  "finding_count": 20,
  "findings": [
    {
      "severity": "high",
      "title": "Meta Pixel (Facebook) is installed but misconfigured",
      "detail": "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.",
      "device": "both",
      "tags": [
        "Tracking"
      ],
      "topic": "tracker_misconfig:Meta Pixel (Facebook)",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Some links cannot be followed by Google",
      "detail": "Links that are not real anchors with an href cannot be crawled, so the pages they point to may never get indexed.",
      "device": "both",
      "tags": [
        "SEO"
      ],
      "topic": "crawlable",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Add quotations so AI engines cite this page",
      "detail": "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.)",
      "device": "both",
      "tags": [
        "AI Search",
        "SEO"
      ],
      "topic": "geo",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Google Analytics tracking broken",
      "detail": "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.",
      "device": "both",
      "tags": [
        "Tracking",
        "Conversion"
      ],
      "topic": "tracking",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Page shifts under the visitor's finger as it loads",
      "detail": "Real Chrome visitors see 0.48 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.",
      "device": "both",
      "tags": [],
      "topic": null,
      "confidence": "field",
      "evidence": []
    },
    {
      "severity": "high",
      "title": "Some text is low-contrast and hard to read",
      "detail": "Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "contrast",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "Tiny buttons are hard to tap on mobile",
      "detail": "69 of 229 tappable items on this page (30%) measure under 24 pixels on their shorter side, below the 24px floor WCAG 2.5.8 sets for accessibility and well under the platform minimums (Apple recommends 44pt, Android 48dp) 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.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tap_targets",
      "confidence": "measured",
      "evidence": [
        "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\""
      ]
    },
    {
      "severity": "medium",
      "title": "Page is heavy and slow on mobile data",
      "detail": "Each visit downloads about 7.0 megabytes, roughly 338 KB of images and 2331 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.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "page_weight",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "The server is slow to respond",
      "detail": "The first byte took about 0.9 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.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "ttfb",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "1 form field has no label",
      "detail": "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.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion",
        "Tracking"
      ],
      "topic": "form_labels",
      "confidence": "measured",
      "evidence": [
        "name=\"g-recaptcha-response\" (textarea)"
      ]
    },
    {
      "severity": "medium",
      "title": "Main content is slow to appear on phones",
      "detail": "For the slowest quarter of real Chrome visitors, the largest visible item on this page takes 3.8 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.",
      "device": "both",
      "tags": [],
      "topic": null,
      "confidence": "field",
      "evidence": []
    },
    {
      "severity": "medium",
      "title": "7 interactive elements have no stable, accessible identity",
      "detail": "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.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Tracking"
      ],
      "topic": "untrackable_elements",
      "confidence": "measured",
      "evidence": [
        "\"clear results\" (div.gsc-clear-button) (div/span used as a button, no role)",
        "(div.gsc-results-close-btn) (no accessible name)",
        "(a) (no accessible name)",
        "\"clear results\" (div.gsc-clear-button) (div/span used as a button, no role)",
        "(div.gsc-results-close-btn) (no accessible name)",
        "(img.pushDataLayer) (no accessible name)",
        "(span.close-button) (no accessible name)"
      ]
    },
    {
      "severity": "low",
      "title": "Unused JavaScript is being downloaded",
      "detail": "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,268 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_js",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Unused CSS is being downloaded",
      "detail": "Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 165 KiB.",
      "device": "both",
      "tags": [
        "Performance"
      ],
      "topic": "unused_css",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "The page loads from a lot of third-party services",
      "detail": "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.",
      "device": "both",
      "tags": [],
      "topic": "third_party",
      "confidence": "sampled",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "No email capture or newsletter detected",
      "detail": "No email input field was found in the page, and no email-marketing tag (Klaviyo, Mailchimp, Substack, ConvertKit, Beehiiv, MailerLite, ActiveCampaign, Omnisend, Brevo, Drip or Buttondown) was detected. A form that loads after JavaScript runs, or one behind a popup or a separate page, will not be visible to this check. 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.",
      "device": "both",
      "tags": [
        "Conversion"
      ],
      "topic": "no_email_capture",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Links to this page will look bare when shared",
      "detail": "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.",
      "device": "both",
      "tags": [],
      "topic": "og_tags",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "40 generic CTA links/buttons (\"Click here\", \"Learn more\", \"Submit\")",
      "detail": "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\").",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "link_text",
      "confidence": "measured",
      "evidence": [
        "\"Read More\" (a)",
        "\"Read More\" (a)",
        "\"Read More\" (a)",
        "\"Read More\" (a)",
        "\"Read More\" (a)"
      ]
    },
    {
      "severity": "low",
      "title": "Headings skip levels",
      "detail": "Skipping a heading level breaks the document outline that screen readers and search engines rely on. On this page the outline jumps to an H4 without the level above it, at \"Choose an option\". Lighthouse flagged 1 heading out of order.",
      "device": "both",
      "tags": [
        "Accessibility (WCAG)"
      ],
      "topic": "heading_order",
      "confidence": "measured",
      "evidence": []
    },
    {
      "severity": "low",
      "title": "Some text is too small to read on phones",
      "detail": "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.",
      "device": "mobile",
      "tags": [
        "Accessibility (WCAG)",
        "Conversion"
      ],
      "topic": "tiny_text",
      "confidence": "sampled",
      "evidence": []
    }
  ]
}