mersaco.com website review

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

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

About 430 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 560 ms faster on a phone.

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

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

6 third-party services load with your homepage (Google Tag Manager, Clarity and FontAwesome CDN and others), adding 955 KiB and 266 ms of main-thread time.

6 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

24 KiB could be saved by minifying JavaScript.

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

Desktop scores 97 but mobile only 69. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

412-T4-Platinum-EIS_compressed.webp weighs 492 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.5 MB in 80 requests on a phone: images 2.3 MB (54), scripts 749 KiB (10) and fonts 361 KiB (7). Under 2 MB keeps phones on slow connections fast.

AFrame-3_compressed.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

6 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: 8 elements on the page fail this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Your title is 81 characters, so Google will cut it off around 60: “Pharmaceutical Supplier - Leading Healthcare Distributor in Lebanon | Mersaco.com”.

Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 27 pages on mersaco.com and 8 external pages.

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

https://www.mersaco.com/home 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.

/ and https://www.mersaco.com/home all use the title “Pharmaceutical Supplier - Leading Healthcare Distributor in Lebanon |…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mersaco.com/news-and-initiatives/65/diater-strengthens-allergy-education-through-nationwide-scientific-and-awareness-initiatives has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mersaco.com/news-and-initiatives/66/live-lighter-novo-nordisk-brings-obesity-care-to-lebanon and https://www.mersaco.com/news-and-initiatives/64/mersaco-and-tabuk-pharmaceuticals-launch-lurabil-a-new-generation-atypical-antipsychotic use the same meta description. A description written for each page earns more clicks.

https://www.mersaco.com/news-and-initiatives, https://www.mersaco.com/sciencehealth, https://www.mersaco.com/aboutus, https://www.mersaco.com/careers, https://www.mersaco.com/news-and-initiatives/66/live-lighter-novo-nordisk-brings-obesity-care-to-lebanon and https://www.mersaco.com/news-and-initiatives/64/mersaco-and-tabuk-pharmaceuticals-launch-lurabil-a-new-generation-atypical-antipsychotic and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mersaco.com/sciencehealth 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.

https://www.mersaco.com/home took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Loading the image 'https://c.clarity.ms/c.gif' violates the following Content Security Policy directive: "img-src 'self…”.

Chrome logged issues while loading the page (“Content security policy”).

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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 23 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 597 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

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