Website review, no card needed

alphapharmacies.co.za logo

alphapharmacies.co.za website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 89 checks

This review found 41 issues worth fixing on alphapharmacies.co.za, 14 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
8.5 s4.4 sMay 2Oct 174.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20267.2 s
May 9, 20267.9 s
May 16, 20268.0 s
May 23, 20268.0 s
May 30, 20267.8 s
Jun 6, 20267.6 s
Jun 13, 20267.8 s
Jun 20, 20267.8 s
Jun 27, 20267.6 s
Jul 4, 20267.4 s
Jul 11, 20266.6 s
Jul 18, 20266.5 s
Jul 25, 20266.2 s
Aug 1, 20266.0 s
Aug 8, 20265.6 s
Aug 15, 20265.3 s
Aug 22, 20265.7 s
Aug 29, 20265.8 s
Sep 5, 20265.8 s
Sep 12, 20265.8 s
Sep 19, 20265.7 s
Sep 26, 20265.4 s
Oct 3, 20265.4 s
Oct 10, 20265.2 s
Oct 17, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
275 ms152 msMay 2Oct 17167 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026195 ms
May 9, 2026232 ms
May 16, 2026259 ms
May 23, 2026261 ms
May 30, 2026258 ms
Jun 6, 2026246 ms
Jun 13, 2026236 ms
Jun 20, 2026233 ms
Jun 27, 2026222 ms
Jul 4, 2026199 ms
Jul 11, 2026188 ms
Jul 18, 2026175 ms
Jul 25, 2026170 ms
Aug 1, 2026174 ms
Aug 8, 2026173 ms
Aug 15, 2026175 ms
Aug 22, 2026181 ms
Aug 29, 2026173 ms
Sep 5, 2026174 ms
Sep 12, 2026170 ms
Sep 19, 2026168 ms
Sep 26, 2026166 ms
Oct 3, 2026168 ms
Oct 10, 2026169 ms
Oct 17, 2026167 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 alphapharmacies.co.za (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alphapharmacies.co.za at 0.6 s0.6 s
  2. alphapharmacies.co.za at 1.1 s1.1 s
  3. alphapharmacies.co.za at 1.7 s1.7 s
  4. alphapharmacies.co.za at 2.2 s2.2 s
  5. alphapharmacies.co.za at 2.8 s2.8 s
  6. alphapharmacies.co.za at 3.4 s3.4 s
  7. alphapharmacies.co.za at 3.9 s3.9 s
  8. alphapharmacies.co.za at 4.5 s4.5 s

Speed

10 to fix39
  • Reduce unused JavaScript

    6.2 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

  • Render-blocking requests

    3.2 s

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

  • Mobile performance score: 39

    39/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 2.0 MB and 1.3 s of main-thread time.

  • Improve image delivery

    850 ms · 246 KiB

    2 images could be 246 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • Use efficient cache lifetimes

    650 ms · 248 KiB

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

  • Reduce unused CSS

    600 ms · 86 KiB

    About 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Google CDN adds 548 ms

    548 ms

    Google CDN costs a phone 548 ms of main-thread work and 1.1 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.

  • Google Tag Manager adds 516 ms

    516 ms

    Google Tag Manager costs a phone 516 ms of main-thread work and 498 KiB 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.

  • Main-thread work: 3.1 s

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

  • 14 long tasks on the main thread

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Legacy JavaScript

    33 KiB

    Polyfills for old browsers add 33 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 252 ms

    252 ms

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

Core Web Vitals

10 to fix67
  • 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: 5.2 s

    5.2 s

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

  • Largest Contentful Paint: 21.6 s

    21.6 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • Total Blocking Time: 722 ms

    722 ms

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 149 ms

    149 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Tap response (INP) got 21% faster for real visitors

    -21%

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

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

    -33%

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

  • Cumulative Layout Shift: 0.03

    0.03

    The layout barely moves while loading (CLS 0.03, good is under 0.1).

Images and page weight

4 to fix35
  • Page weight: 4.3 MB in 119 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 119 requests on a phone: scripts 2.2 MB (65), images 1.2 MB (12) and other files 352 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Alpha-52_Win-R100-000-1.png weighs 529 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (818 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.

  • 1 image far larger than shown

    26 KiB

    1 image is downloaded at several times the size a phone draws it, for example Alpha-52_Win-R100-000-1.png at 1,200 px wide, shown at 390 px. Resized copies would save about 26 KiB.

  • About 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.5 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

6 to fixGoogle 9092
  • 10 text elements with low contrast

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

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

    All page content should be contained by landmarks: 12 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • No H1 headline

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 35 internal links, 14 external

    The homepage links to 35 pages on alphapharmacies.co.za and 14 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Welcome to Alpha Pharm Community Care Pharmacies where we put YOU the patient first as our primary focus and offer exce…”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Home - Alpha Pharmacies Community Pharmacies”.

  • Canonical URL set

    The canonical URL is https://www.alphapharmacies.co.za/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.alphapharmacies.co.za/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.alphapharmacies.co.za/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.

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

  • Text is in the HTML

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

Other pages

5 to fix76
  • 3 pages share a title

    https://www.alphapharmacies.co.za/about-alpha-pharm, https://www.alphapharmacies.co.za/index.php/about and https://www.alphapharmacies.co.za/about all use the title “About - Alpha Pharmacies”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.alphapharmacies.co.za/blogs, https://www.alphapharmacies.co.za/services, https://www.alphapharmacies.co.za/alpha-clin-clinic, https://www.alphapharmacies.co.za/alpha-doc, https://www.alphapharmacies.co.za/faq and https://www.alphapharmacies.co.za/legal and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.alphapharmacies.co.za/about-alpha-pharm, https://www.alphapharmacies.co.za/index.php/about and https://www.alphapharmacies.co.za/about use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.alphapharmacies.co.za/index.php/about, whose canonical is https://www.alphapharmacies.co.za/about-alpha-pharm. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://www.alphapharmacies.co.za/about-alpha-pharm, https://www.alphapharmacies.co.za/blogs, https://www.alphapharmacies.co.za/promotions, https://www.alphapharmacies.co.za/location-finder, https://www.alphapharmacies.co.za/services and https://www.alphapharmacies.co.za/alphaclin-bookings and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.alphapharmacies.co.za/promotions, https://www.alphapharmacies.co.za/services and https://www.alphapharmacies.co.za/contacts have 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.

  • 14 internal pages checked

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

3 checks passed
  • Linked pages load

    All 14 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css?family&subset=&ver=1.2.0' from origin 'https://www.alphap…”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 306 words of copy

    The homepage carries about 306 words of visible text.

  • Urgency cues

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Book an appointment”, “Contact” and “Learn more”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.

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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 alphapharmacies.co.za, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on alphapharmacies.co.za, including 20 speed issues, 2 SEO issues and 1 conversion gap. 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