Website review, no card needed
pharmaniaga.com website review
Visit site (opens in a new tab)Reviewed 27 October 202632 issues · 66 checks
This review found 32 issues worth fixing on pharmaniaga.com, 15 of them high impact, across 66 checks. The most urgent: page weight: 14.5 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.2 s |
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.2 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 5.9 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 4.8 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.7 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 5.2 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 149 ms |
| May 16, 2026 | 148 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 148 ms |
| Jul 18, 2026 | 150 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 141 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 144 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.3 s
5.3 sReal visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 149 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 143 ms
143 msReal visitors wait 143 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.2 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 14.5 MB
14.5 MBYour homepage downloads 14.5 MB on a phone, 9.5 MB of it images (65%). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.1 MB) 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.
About 4.1 g of CO₂ per visit
4.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.11 g of CO₂e: 493.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
34 text elements with low contrast
34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA toggle fields must have an accessible name (2 elements)
ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 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.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 13 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (13 characters)
Your title is only 13 characters: “Pharmaniaga |”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
114 internal links, 11 external
The homepage links to 114 pages on pharmaniaga.com and 11 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://pharmaniaga.com/.
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://pharmaniaga.com/wp-sitemap.xml.
AI search readiness
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.
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 (777 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages without a meta description
https://pharmaniaga.com/about-us/who-we-are, https://pharmaniaga.com/about-us/corporate-policies, https://pharmaniaga.com/about-us/corporate-structure, https://pharmaniaga.com/milestones, https://pharmaniaga.com/about-us/awards-recognitions and https://pharmaniaga.com/standards-certifications and 7 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://pharmaniaga.com/customer-care, whose canonical is https://pharmaniaga.com/services/customer-care. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages slow to respond
https://pharmaniaga.com/about-us/who-we-are, https://pharmaniaga.com/about-us/corporate-policies, https://pharmaniaga.com/about-us/corporate-structure, https://pharmaniaga.com/milestones, https://pharmaniaga.com/about-us/awards-recognitions and https://pharmaniaga.com/standards-certifications and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
5 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
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 13 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 (Internal Server Error)”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 580 words of copy
The homepage carries about 580 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “DOWNLOAD REPORT HERE”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 6 phone links and 6 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
11 other companies contacted
Loading the homepage contacts 11 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 pharmaniaga.com, 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
- Analytics
- Google Analytics
- Hosting
- TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malay
Company
- Founded
- 1994
- Headquarters
- Shah Alam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on pharmaniaga.com, including 4 speed issues, 5 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.