pharmacity.vn website review

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

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

pharmacity.io costs a phone 3.5 s of main-thread work and 18.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 501 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 698 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (pharmacity.io, Google Tag Manager and TikTok and others), adding 19.7 MB and 5.4 s of main-thread time.

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

TikTok costs a phone 257 ms of main-thread work and 157 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 54 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

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.

5 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 48.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1026 - Vitaweek Livespo - Popup”.

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

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

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

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

Real visitors wait 472 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 20.1 MB in 376 requests on a phone: images 17.8 MB (196), scripts 1.8 MB (99) and HTML 189 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 20240301030421-0-Type=B2G2, Size=Normal (2).png at 468 px wide, shown at 48 px. Resized copies would save about 109 KiB.

3 images (166 KiB) 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.

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

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

3 buttons have no accessible name, so screen readers announce just “button”.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Alternative text of images should not be repeated as text: 27 elements on the page fail this check, rated minor by axe-core.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

Structured data found (MedicalBusiness and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 351 pages on pharmacity.vn and 8 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://www.pharmacity.vn/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.pharmacity.vn/tra-cuu-don-hang 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.

https://www.pharmacity.vn/collection/ho-tro-tang-de-khang, https://www.pharmacity.vn/collection/khau-trang and https://www.pharmacity.vn/collection/sua-abbott are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.pharmacity.vn/tra-cuu-don-hang all use the title “Nhà thuốc Pharmacity | Đúng thuốc, tận tâm, giá tốt”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pharmacity.vn/collection/ho-tro-tang-de-khang, https://www.pharmacity.vn/collection/khau-trang and https://www.pharmacity.vn/collection/sua-abbott have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pharmacity.vn/danh-cho-khach-hang-doanh-nghiep.lp, https://www.pharmacity.vn/he-thong-cua-hang, https://www.pharmacity.vn/benh, https://www.pharmacity.vn/thang-cua-nang-khong-qua-dung-ve-nha.lp, https://www.pharmacity.vn/cau-lac-bo-benh-man-song-khoe.lp and https://www.pharmacity.vn/collection/ho-tro-tang-de-khang and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://production-cdn.pharmacity.io/digital/425x0/plain/e-com/images/banners/20261020073336-0-APPMainBanner.png?versionId=ttOFbLhdhqv56lKrRgOzaknNAtidHjpW.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Requests the geolocation permission on page load.

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.

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.

Social proof on the homepage: 4 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.

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 2,483 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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 15 cookies (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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.