Website review, no card needed
jamjoompharma.com website review
Visit site (opens in a new tab)Reviewed 31 October 202645 issues · 84 checks
This review found 45 issues worth fixing on jamjoompharma.com, 20 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
68D- #103,553 of 117,751 reviewed websitesbeats 10%
- #62,454 of 66,959 online storesbeats 5%
- #2,269 of 2,702 WooCommerce storesbeats 13%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 9.5 s |
| May 16, 2026 | 9.6 s |
| May 23, 2026 | 9.7 s |
| May 30, 2026 | 9.7 s |
| Jun 6, 2026 | 9.8 s |
| Jun 13, 2026 | 9.9 s |
| Jun 20, 2026 | 10.0 s |
| Jun 27, 2026 | 10.0 s |
| Jul 4, 2026 | 10.1 s |
| Jul 11, 2026 | 10.1 s |
| Jul 18, 2026 | 10.2 s |
| Jul 25, 2026 | 10.2 s |
| Aug 1, 2026 | 10.1 s |
| Aug 8, 2026 | 10.6 s |
| Aug 15, 2026 | 11.0 s |
| Aug 22, 2026 | 12.5 s |
| Aug 29, 2026 | 13.2 s |
| Sep 5, 2026 | 12.8 s |
| Sep 12, 2026 | 13.7 s |
| Sep 19, 2026 | 13.7 s |
| Sep 26, 2026 | 13.5 s |
| Oct 3, 2026 | 13.4 s |
| Oct 10, 2026 | 13.3 s |
| Oct 17, 2026 | 13.1 s |
| Oct 24, 2026 | 13.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 126 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 114 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
How it loaded on a phone
1.9 s
3.9 s
5.8 s
7.8 s
9.7 s
11.7 s
13.6 s
15.6 s
Speed
Improve image delivery
3.9 s · 4.7 MB7 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.
Render-blocking requests
5.6 s67 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Reduce unused CSS
1.5 s · 201 KiBAbout 201 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.
Reduce unused JavaScript
1.1 s · 180 KiBAbout 180 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Document request latency
100 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
3 third-party services on the page
3 third-party services load with your homepage (JSDelivr CDN, Cloudflare CDN and Google Fonts), adding 266 KiB and 20 ms of main-thread time.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 344 ms of it running JavaScript. That is comfortably low.
Server response: 597 ms
597 msYour server sent the HTML in 597 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 16.7 s
16.7 sReal visitors wait 16.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.30
0.30For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.
Real-user FCP: 11.5 s
11.5 sReal visitors see the first content after 11.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 7.0 s
7.0 sReal visitors wait 7.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”. Most of its time is element render delay (12.2 s).
Speed Index: 25.3 s
25.3 sVisually, the page fills in at 25.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.4 s
16.4 sThe page becomes fully interactive after 16.4 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 9.5 s to 13.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 141 ms
141 msReal visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.9 MB in 145 requests
6.9 MBYour homepage downloads 6.9 MB in 145 requests on a phone: images 5.4 MB (21), fonts 618 KiB (8) and scripts 505 KiB (57). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.3 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
1.4 MB4 images are downloaded at several times the size a phone draws them, for example Untitled-design-4.png at 1,459 px wide, shown at 360 px. Resized copies would save about 1.4 MB.
5 images in older formats
5 images (4.0 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.
4 images below the first screen load straight away
4 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
1.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.97 g of CO₂e: 236.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 text elements with low contrast
11 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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 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.
Title is short (24 characters)
Your title is only 24 characters: “Jamjoom – Jamjoom Pharma”. 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.
5 H1 headlines
There are 5 <h1> headlines (“Building a Healthier Future, Locally and Globally”, “HealthCare Professionals” and “Patients”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.jamjoompharma.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at jamjoompharma.com/robots.txt, the first file search crawlers ask for.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
41 internal links, 7 external
The homepage links to 41 pages on jamjoompharma.com and 7 external pages.
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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (433 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.jamjoompharma.com/+966113224456, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
/ and https://www.jamjoompharma.com/ar all use the title “Jamjoom – Jamjoom Pharma”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://www.jamjoompharma.com/about-us, https://www.jamjoompharma.com/innovation, https://www.jamjoompharma.com/product-range, https://www.jamjoompharma.com/sustainability, https://www.jamjoompharma.com/news-insights and https://www.jamjoompharma.com/careers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.jamjoompharma.com/about-us, https://www.jamjoompharma.com/innovation, https://www.jamjoompharma.com/product-range, https://www.jamjoompharma.com/sustainability, https://www.jamjoompharma.com/news-insights and https://www.jamjoompharma.com/careers have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.jamjoompharma.com/ar 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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
26 of 26 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: “over 147 brands”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 452 words of copy
The homepage carries about 452 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us” and “Learn More”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 jamjoompharma.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Shabakahnet
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on jamjoompharma.com, including 17 speed issues, 9 SEO issues and 4 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.