Website review, no card needed

tridem-pharma.com logo

tridem-pharma.com website review

Visit site (opens in a new tab)Reviewed 30 October 202646 issues · 81 checks

This review found 46 issues worth fixing on tridem-pharma.com, 13 of them high impact, across 81 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
2.8 s1.6 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.4 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
131 ms85 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026106 ms
May 16, 2026110 ms
May 23, 202696 ms
May 30, 202699 ms
Jun 6, 202693 ms
Jun 13, 202694 ms
Jun 20, 2026101 ms
Jun 27, 2026111 ms
Jul 4, 2026118 ms
Jul 11, 2026126 ms
Jul 18, 2026117 ms
Jul 25, 2026119 ms
Aug 1, 2026115 ms
Aug 8, 2026125 ms
Aug 15, 2026125 ms
Aug 22, 2026111 ms
Aug 29, 2026111 ms
Sep 5, 202691 ms
Sep 12, 202690 ms
Sep 19, 202698 ms
Sep 26, 2026108 ms
Oct 3, 2026111 ms
Oct 10, 2026110 ms
Oct 17, 2026103 ms
Oct 24, 202698 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 tridem-pharma.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tridem-pharma.com at 0.8 s0.8 s
  2. tridem-pharma.com at 1.7 s1.7 s
  3. tridem-pharma.com at 2.5 s2.5 s
  4. tridem-pharma.com at 3.3 s3.3 s
  5. tridem-pharma.com at 4.2 s4.2 s
  6. tridem-pharma.com at 5.0 s5.0 s
  7. tridem-pharma.com at 5.9 s5.9 s
  8. tridem-pharma.com at 6.7 s6.7 s

Speed

5 to fix67
  • Use efficient cache lifetimes

    3.3 s · 3.5 MB

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

  • Improve image delivery

    1.1 s · 1.9 MB

    13 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 608 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Baidu Analytics and alicdn.com), adding 20 KiB and 36 ms of main-thread time.

  • Reduce unused JavaScript

    25 KiB

    About 25 KiB of JavaScript is downloaded but never used on this page.

  • Minify JavaScript

    17 KiB

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 783 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

8 to fix50
  • 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.

  • Speed Index: 10.7 s

    10.7 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • Time to Interactive: 7.4 s

    7.4 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • 28 images without width and height

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

  • Total Blocking Time: 279 ms

    279 ms

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

4 to fix58
  • Page weight: 3.6 MB in 45 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 45 requests on a phone: images 3.4 MB (28), scripts 101 KiB (7) and stylesheets 34 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (2.6 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.

  • 7 images below the first screen load straight away

    7 images further down the page (919 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    301 KiB

    5 images are downloaded at several times the size a phone draws them, for example mo_index-kv2.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 301 KiB.

  • About 1.0 g of CO₂ per visit

    1.01 g

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

Accessibility

9 to fixGoogle 7586
  • 2 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 14 images without alt text

    14 images have no alt text, which hurts accessibility and image search.

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

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

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

9 to fixGoogle 7566
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Tridem Pharma | A Global Outsourcing Solution for Pharmaceutical Groups”.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“A GLOBAL OUTSOURCING SOLUTION FOR PHARMACEUTICAL …”, “1986” and “35”). 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.tridem-pharma.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at tridem-pharma.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 13 internal links, 0 external

    The homepage links to 13 pages on tridem-pharma.com and 0 external pages.

1 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Tridem Pharma provides a one-stop service to bring pharmaceutical & healthcare products from all over the world to Afri…”.

AI search readiness

1 to fix81
  • 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://www.tridem-pharma.com/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.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix86
  • 10 pages share a title

    /, https://www.tridem-pharma.com/services.html, https://www.tridem-pharma.com/about/index.html, https://www.tridem-pharma.com/news/detail-1043.html, https://www.tridem-pharma.com/news/detail-41.html and https://www.tridem-pharma.com/news/detail-37.html and 4 others all use the title “Tridem Pharma | A Global Outsourcing Solution for Pharmaceutical Grou…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.tridem-pharma.com/services.html, https://www.tridem-pharma.com/about/index.html, https://www.tridem-pharma.com/news/detail-1043.html, https://www.tridem-pharma.com/news/detail-41.html, https://www.tridem-pharma.com/news/detail-37.html and https://www.tridem-pharma.com/news/detail-33.html and 3 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.tridem-pharma.com/news/detail-1043.html, https://www.tridem-pharma.com/news/detail-41.html, https://www.tridem-pharma.com/news/detail-37.html, https://www.tridem-pharma.com/news/detail-33.html, https://www.tridem-pharma.com/news/detail-31.html and https://www.tridem-pharma.com/news/detail-28.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.tridem-pharma.com/news/index.html 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.

5 checks passed
  • Linked pages load

    All 9 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 9 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8191
  • 5 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

5 to fix20
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 451 words of visible text.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on tridem-pharma.com, including 13 speed issues, 9 SEO issues and 5 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