Website review, no card needed

wilsons.pk logo

wilsons.pk website review

Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 89 checks

This review found 44 issues worth fixing on wilsons.pk, 21 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
4.1 s3.2 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.8 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.8 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20264.0 s
Jul 11, 20263.8 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.5 s
Aug 29, 20263.4 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.6 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
119 ms101 msMay 16Oct 31110 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026112 ms
May 30, 2026113 ms
Jun 6, 2026115 ms
Jun 13, 2026115 ms
Jun 20, 2026117 ms
Jun 27, 2026113 ms
Jul 4, 2026112 ms
Jul 11, 2026110 ms
Jul 18, 2026105 ms
Jul 25, 2026107 ms
Aug 1, 2026105 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026105 ms
Aug 29, 2026107 ms
Sep 5, 2026113 ms
Sep 12, 2026114 ms
Sep 19, 2026113 ms
Sep 26, 2026113 ms
Oct 3, 2026111 ms
Oct 10, 2026106 ms
Oct 17, 2026106 ms
Oct 24, 2026110 ms
Oct 31, 2026110 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 wilsons.pk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wilsons.pk at 0.9 s0.9 s
  2. wilsons.pk at 1.9 s1.9 s
  3. wilsons.pk at 2.8 s2.8 s
  4. wilsons.pk at 3.8 s3.8 s
  5. wilsons.pk at 4.7 s4.7 s
  6. wilsons.pk at 5.6 s5.6 s
  7. wilsons.pk at 6.6 s6.6 s
  8. wilsons.pk at 7.5 s7.5 s

Speed

10 to fix31
  • Use efficient cache lifetimes

    3.3 s · 2.1 MB

    116 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Render-blocking requests

    3.4 s

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

  • Improve image delivery

    2.0 s · 693 KiB

    7 images could be 693 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 400 KiB

    About 400 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 4.7 s

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

  • Reduce unused JavaScript

    1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page.

  • 5 third-party services on the page

    5 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Cloudflare and others), adding 3.3 MB and 977 ms of main-thread time.

  • YouTube adds 943 ms

    943 ms

    YouTube costs a phone 943 ms of main-thread work and 2.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Font display

    750 ms

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

  • Minify CSS

    150 ms · 34 KiB

    34 KiB could be saved by minifying CSS.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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.

1 checks passed
  • Server response: 209 ms

    209 ms

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

Core Web Vitals

11 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 LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 0.26

    0.26

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Speed Index: 15.9 s

    15.9 s

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

  • Time to Interactive: 33.4 s

    33.4 s

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

  • Cumulative Layout Shift: 0.951

    0.951

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

  • Largest Contentful Paint: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Total Blocking Time: 236 ms

    236 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

1 checks passed
  • Real-user INP: 136 ms

    136 ms

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

Images and page weight

3 to fix50
  • Page weight: 6.4 MB in 172 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 172 requests on a phone: scripts 3.1 MB (73), images 1.3 MB (22) and fonts 1.2 MB (14). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1,004 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 5 images far larger than shown

    355 KiB

    5 images are downloaded at several times the size a phone draws them, for example NjVlMDgwYTI5NV81OQ.png at 512 px wide, shown at 60 px. Resized copies would save about 355 KiB.

  • About 1.8 g of CO₂ per visit

    1.82 g

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

1 checks passed
  • Images load when needed

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

Accessibility

7 to fixGoogle 8692
  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 79 internal links, 11 external

    The homepage links to 79 pages on wilsons.pk and 11 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Building a healthier future on our legacy”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Wilson’s Pharmaceuticals – Total Commitment for good health”.

  • Canonical URL set

    The canonical URL is https://wilsons.pk/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://wilsons.pk/wp-sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://wilsons.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (763 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 2 pages share a title

    https://wilsons.pk/contact-us and https://wilsons.pk/contact all use the title “Contact Us – Wilson’s Pharmaceuticals”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://wilsons.pk/about, https://wilsons.pk/facility, https://wilsons.pk/faqs, https://wilsons.pk/career, https://wilsons.pk/blogs and https://wilsons.pk/products and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://wilsons.pk/contact, whose canonical is https://wilsons.pk/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://wilsons.pk/about, https://wilsons.pk/facility, https://wilsons.pk/faqs, https://wilsons.pk/career, https://wilsons.pk/blogs and https://wilsons.pk/products and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://wilsons.pk/facility, https://wilsons.pk/faqs, https://wilsons.pk/products, https://wilsons.pk/partnership and https://wilsons.pk/contact-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7796
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 317 words of copy

    The homepage carries about 317 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact” and “call: +55 (9900) 666 22”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 wilsons.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Cloudflare

Company

Headquarters
Islamabad

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on wilsons.pk, including 21 speed issues, 3 SEO issues 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