zenith.com.bd website review

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

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

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

2 third-party services load with your homepage (zyrosite.com and pexels.com), adding 27.5 MB and 0 ms of main-thread time.

pexels.com costs a phone 0 ms of main-thread work and 26.8 MB 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.

21 images could be 427 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

zyrosite.com costs a phone 0 ms of main-thread work and 715 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.

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

Desktop scores 97 but mobile only 66. 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.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 27.9 MB in 60 requests on a phone: media 26.6 MB (7), images 873 KiB (33) and scripts 370 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

There are 13 <h1> headlines (“Zenith Pharmaceuticals and Ventures”, “Zenith Pharmaceuticals Ltd.” and “Zenith Nutraceuticals Ltd.”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 16 pages on zenith.com.bd and 6 external pages.

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.

There is no https://zenith.com.bd/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://zenith.com.bd/portfolio and https://zenith.com.bd/about-zenith-pharmaceuticals all use the title “Zenith Pharmaceuticals: Quality and Innovation in Healthcare | ZENITH”. Search engines can't tell which page to show for a search, so each competes with the others.

https://zenith.com.bd/product-list, https://zenith.com.bd/about-our-management and https://zenith.com.bd/career have no meta description, so Google writes the search snippet from whatever text it finds.

https://zenith.com.bd/product-list and https://zenith.com.bd/career have 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.

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

4 of 5 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 “Failed to load resource: net::ERR_FAILED”.

17 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.