Website review, no card needed

imedpharma.com logo

imedpharma.com website review

Visit site (opens in a new tab)Reviewed 20 October 202641 issues · 88 checks

This review found 41 issues worth fixing on imedpharma.com, 18 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
6.5 s3.8 sMay 2Oct 174.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.5 s
May 9, 20264.4 s
May 16, 20264.2 s
May 23, 20264.2 s
May 30, 20264.1 s
Jun 6, 20264.4 s
Jun 13, 20265.0 s
Jun 20, 20265.4 s
Jun 27, 20265.7 s
Jul 4, 20266.0 s
Jul 11, 20266.1 s
Jul 18, 20266.2 s
Jul 25, 20266.2 s
Aug 1, 20266.1 s
Aug 8, 20266.1 s
Aug 15, 20265.8 s
Aug 22, 20265.4 s
Aug 29, 20265.1 s
Sep 5, 20264.9 s
Sep 12, 20265.0 s
Sep 19, 20265.1 s
Sep 26, 20265.1 s
Oct 3, 20264.8 s
Oct 10, 20264.8 s
Oct 17, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
97 ms87 msMay 2Oct 1795 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202692 ms
May 9, 202695 ms
May 16, 202695 ms
May 23, 202692 ms
May 30, 202691 ms
Jun 6, 202693 ms
Jun 13, 202692 ms
Jun 20, 202693 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202695 ms
Jul 18, 202696 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202694 ms
Aug 15, 202695 ms
Aug 22, 202692 ms
Aug 29, 202692 ms
Sep 5, 202692 ms
Sep 12, 202688 ms
Sep 19, 202689 ms
Sep 26, 202688 ms
Oct 3, 202688 ms
Oct 10, 202692 ms
Oct 17, 202695 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 imedpharma.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. imedpharma.com at 2.0 s2.0 s
  2. imedpharma.com at 4.0 s4.0 s
  3. imedpharma.com at 6.0 s6.0 s
  4. imedpharma.com at 8.1 s8.1 s
  5. imedpharma.com at 10.1 s10.1 s
  6. imedpharma.com at 12.1 s12.1 s
  7. imedpharma.com at 14.1 s14.1 s
  8. imedpharma.com at 16.1 s16.1 s

Speed

12 to fix43
  • Improve image delivery

    8.1 s · 1.6 MB

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

  • Render-blocking requests

    8.4 s

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

  • Reduce unused JavaScript

    1.1 s · 859 KiB

    About 859 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.

  • Mobile performance score: 43

    43/100

    Your mobile performance score is 43 (desktop: 48). 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 Tag Manager, Google Maps and Google CDN and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 580 KiB

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

  • Google Tag Manager adds 570 ms

    570 ms

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

  • Reduce unused CSS

    300 ms · 92 KiB

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

  • Main-thread work: 3.2 s

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

  • Google Maps adds 171 ms

    171 ms

    Google Maps costs a phone 171 ms of main-thread work and 383 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.

  • 1,737 HTML elements

    The page has 1,737 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google CDN adds 111 ms

    111 ms

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

  • 13 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    20 KiB

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

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.8 s

    5.8 s

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

  • Real-user FCP: 5.6 s

    5.6 s

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

  • Real-user TTFB: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

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

  • Speed Index: 23.2 s

    23.2 s

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

  • Time to Interactive: 26.5 s

    26.5 s

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

  • First Contentful Paint: 7.5 s

    7.5 s

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

  • Total Blocking Time: 470 ms

    470 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

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

  • 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

2 to fix55
  • Page weight: 12.2 MB in 225 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 225 requests on a phone: images 9.2 MB (31), scripts 1.9 MB (79) and fonts 800 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 4.2 MB together. On a phone connection a single image that size takes seconds.

  • 1 image below the first screen load straight away

    1 image further down the page (166 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.5 g of CO₂ per visit

    3.46 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8992
  • 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.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 23 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 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 7786
  • No H1 headline

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

  • 8 links crawlers can't follow

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

  • 4 links with vague text

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

  • 117 internal links, 10 external

    The homepage links to 117 pages on imedpharma.com and 10 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “I-MED Pharma is a leader in dry eye diagnosis and management. Find dry eye products, diagnostic tools, eye health suppl…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “I-MED Pharma - Specializing In Dry Eye Relief Solutions”.

  • Canonical URL set

    The canonical URL is https://imedpharma.com/.

  • 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://imedpharma.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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 (1,590 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://imedpharma.com/fr declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    https://imedpharma.com/about-i-med-pharma and https://imedpharma.com/advisory-board are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://imedpharma.com/about-i-med-pharma, https://imedpharma.com/leadership-team, https://imedpharma.com/advisory-board and https://imedpharma.com/what-makes-us-unique have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://imedpharma.com/fr, https://imedpharma.com/about-i-med-pharma, https://imedpharma.com/leadership-team, https://imedpharma.com/advisory-board and https://imedpharma.com/what-makes-us-unique have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://imedpharma.com/fr, https://imedpharma.com/leadership-team and https://imedpharma.com/what-makes-us-unique took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    5 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 a title

    All 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replace')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Thin social proof

    Social proof on the homepage: 41 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 724 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy Now” and “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Buy Now” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

  • Phone number on the homepage

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

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies (measured from a US location before any click).

  • 24 other companies contacted

    Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 imedpharma.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
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 imedpharma.com, including 21 speed issues, 3 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

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