phukethospital.com website review

20 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

9 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

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

FontAwesome CDN costs a phone 16 ms of main-thread work and 301 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 95 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.

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

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

6 third-party services load with your homepage (cookiecdn.com, FontAwesome CDN and Cloudflare and others), adding 578 KiB and 78 ms of main-thread time.

6 long tasks block the main thread while loading, the longest for 127 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).

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.

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 12.7 s. Good is under 3.8 s.

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

Your homepage downloads 5.3 MB in 134 requests on a phone: images 4.1 MB (52), scripts 710 KiB (43) and fonts 321 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

8 images are downloaded at several times the size a phone draws them, for example DAA-03-76-88.jpg at 2,134 px wide, shown at 247 px. Resized copies would save about 1.6 MB.

5 images (1.8 MB) 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.

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 23 characters: “Bangkok Hospital Phuket”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 23 characters: “Bangkok Hospital Phuket”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 46 pages on phukethospital.com and 1 external page.

A phone browser shows 367 words, but the HTML your server sends has only 68. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

https://www.bangkokhospital.com/en/phuket and https://www.bangkokhospital.com/en/phuket/page/privacy-policy-undefined all use the title “Bangkok Hospital Phuket”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.bangkokhospital.com/en/phuket/contact, https://www.bangkokhospital.com/en/phuket/package, https://www.bangkokhospital.com/en/phuket/center-clinic and https://www.bangkokhospital.com/en/phuket/health-info have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.bangkokhospital.com/en, https://www.bangkokhospital.com/en/center-clinic and https://www.bangkokhospital.com/en/directory use the same meta description. A description written for each page earns more clicks.

https://www.bangkokhospital.com/en, https://www.bangkokhospital.com/en/phuket/page/privacy-policy-undefined and https://www.bangkokhospital.com/en/directory have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.bangkokhospital.com/en, https://www.bangkokhospital.com/en/phuket/doctor, https://www.bangkokhospital.com/en/phuket/appointment, https://www.bangkokhospital.com/en/phuket/contact, https://www.bangkokhospital.com/en/center-clinic and https://www.bangkokhospital.com/en/phuket/page/privacy-policy-undefined and 3 others 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 11 pages linked from your homepage and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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