meditech-pharma.com website review

Your mobile performance score is 87 (desktop: 78). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, iubenda and Clarity and others), adding 1.2 MB and 627 ms of main-thread time.

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

JSDelivr CDN costs a phone 0 ms of main-thread work and 542 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.

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

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

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 15 characters: “Meditech | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 115 pages on meditech-pharma.com and 8 external pages.

/, https://www.meditech-pharma.com/fr-be, https://www.meditech-pharma.com/fr-fr, https://www.meditech-pharma.com/es-es, https://www.meditech-pharma.com/de-de and https://www.meditech-pharma.com/en-au and 1 other all use the title “Meditech | Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.meditech-pharma.com/fr-be and https://www.meditech-pharma.com/fr-fr use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97212764&tm=gtm002&Ver=2&mid=b874d36a-05e8-4f05-bcfc-237440f21af2&bo=1&sid=54c926c0ccf611f1b66de7f17978d540&vid=54c955b0ccf611f180c7234dda3e053a&vids=1&msclkid=N&pi=91.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 676 words of visible text.

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

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

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