Website review, no card needed

callcourier.com.pk logo

callcourier.com.pk website review

Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 76 checks

This review found 31 issues worth fixing on callcourier.com.pk, 15 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
11.3 s1.3 sMay 9Oct 245.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 202610.1 s
May 16, 20268.4 s
May 23, 20265.8 s
May 30, 20264.3 s
Jun 6, 20263.1 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20262.8 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.8 s
Aug 29, 20263.1 s
Sep 5, 20263.6 s
Sep 12, 20264.0 s
Sep 19, 20264.5 s
Sep 26, 20265.2 s
Oct 3, 20265.7 s
Oct 10, 20266.1 s
Oct 17, 20266.0 s
Oct 24, 20265.9 s
Real-visitor tap response (INP)75th percentile, phones
263 ms90 msMay 9Oct 24243 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026154 ms
May 16, 2026128 ms
May 23, 2026120 ms
May 30, 2026115 ms
Jun 6, 2026112 ms
Jun 13, 2026114 ms
Jun 20, 2026122 ms
Jun 27, 2026131 ms
Jul 4, 2026144 ms
Jul 11, 2026161 ms
Jul 18, 2026128 ms
Jul 25, 2026115 ms
Aug 1, 2026111 ms
Aug 8, 2026110 ms
Aug 15, 2026111 ms
Aug 22, 2026118 ms
Aug 29, 2026133 ms
Sep 5, 2026176 ms
Sep 12, 2026202 ms
Sep 19, 2026215 ms
Sep 26, 2026220 ms
Oct 3, 2026221 ms
Oct 10, 2026227 ms
Oct 17, 2026236 ms
Oct 24, 2026243 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of callcourier.com.pk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. callcourier.com.pk at 0.4 s0.4 s
  2. callcourier.com.pk at 0.8 s0.8 s
  3. callcourier.com.pk at 1.1 s1.1 s
  4. callcourier.com.pk at 1.5 s1.5 s
  5. callcourier.com.pk at 1.9 s1.9 s
  6. callcourier.com.pk at 2.3 s2.3 s
  7. callcourier.com.pk at 2.6 s2.6 s
  8. callcourier.com.pk at 3.0 s3.0 s

Speed

9 to fix30
  • Render-blocking requests

    5.3 s

    28 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.

  • Reduce unused JavaScript

    3.1 s · 514 KiB

    About 514 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Font display

    2.6 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.6 s).

  • Use efficient cache lifetimes

    1.8 s · 217 KiB

    5 files are served with short cache lifetimes, so returning visitors download them again (217 KiB).

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    600 ms · 1.0 MB

    9 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Avoid multiple page redirects

    901 ms

    The page goes through 1 redirect before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 470 KiB and 263 ms of main-thread time.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user CLS: 0.79

    0.79

    For real visitors the layout shifts by 0.79 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 27.4 s

    27.4 s

    Your largest element takes 27.4 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Time to Interactive: 28.3 s

    28.3 s

    The page becomes fully interactive after 28.3 s. Good is under 3.8 s.

  • Cumulative Layout Shift: 0.897

    0.897

    The layout shifts by 0.897 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 5.0 s

    5.0 s

    The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 2.8 s

    2.8 s

    Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 70% slower for real visitors

    +70%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 154 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 5.8 s

    5.8 s

    Visually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 298 ms

    298 ms

    Scripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.

2 checks passed
  • Real-user INP: 154 ms

    154 ms

    Real visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 36% faster for real visitors

    -36%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 10.1 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix70
  • Page weight: 7.6 MB in 159 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 159 requests on a phone: other files 3.2 MB (29), images 2.4 MB (38) and scripts 1.5 MB (54). Under 2 MB keeps phones on slow connections fast.

  • About 2.1 g of CO₂ per visit

    2.15 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.15 g of CO₂e: 257.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10097
  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10090
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 13 internal links, 16 external

    The homepage links to 13 pages on callcourier.com.pk and 16 external pages.

7 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “We are a group of dedicated, highly professional staff within the field of courier services.”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Call Courier is Now PostEx – Pakistan Courier Service”.

  • Canonical URL set

    The canonical URL is https://callcourier.com.pk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://callcourier.com.pk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://callcourier.com.pk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

100
  • 1 page with very little text

    https://callcourier.com.pk/tracking has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 16 small tap targets

    16 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 133 words

    The homepage has only about 133 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Track Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 10 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at callcourier.com.pk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on callcourier.com.pk, including 21 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25