Website review, no card needed

bagan.com.my logo

bagan.com.my website review

Visit site (opens in a new tab)Reviewed 26 October 202627 issues · 81 checks

This review found 27 issues worth fixing on bagan.com.my, 9 of them high impact, across 81 checks. The most urgent: font display. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s387 msMay 9Oct 24735 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.6 s
May 23, 20262.2 s
May 30, 2026919 ms
Jun 6, 2026775 ms
Jun 13, 2026766 ms
Jun 20, 2026759 ms
Jun 27, 2026732 ms
Jul 4, 2026745 ms
Jul 11, 2026730 ms
Jul 18, 2026763 ms
Jul 25, 2026793 ms
Aug 1, 2026815 ms
Aug 8, 2026874 ms
Aug 15, 2026848 ms
Aug 22, 2026842 ms
Aug 29, 2026820 ms
Sep 5, 2026795 ms
Sep 12, 2026778 ms
Sep 19, 2026777 ms
Sep 26, 2026756 ms
Oct 3, 2026732 ms
Oct 10, 2026732 ms
Oct 17, 2026711 ms
Oct 24, 2026735 ms
Real-visitor tap response (INP)75th percentile, phones
113 ms94 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026106 ms
May 23, 2026102 ms
May 30, 2026100 ms
Jun 6, 202698 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 202697 ms
Jul 4, 202698 ms
Jul 11, 202697 ms
Jul 18, 202699 ms
Jul 25, 202699 ms
Aug 1, 2026102 ms
Aug 8, 2026101 ms
Aug 15, 2026101 ms
Aug 22, 2026101 ms
Aug 29, 202698 ms
Sep 5, 2026100 ms
Sep 12, 202699 ms
Sep 19, 202699 ms
Sep 26, 202698 ms
Oct 3, 202697 ms
Oct 10, 202696 ms
Oct 17, 202697 ms
Oct 24, 202698 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of bagan.com.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bagan.com.my at 0.5 s0.5 s
  2. bagan.com.my at 1.1 s1.1 s
  3. bagan.com.my at 1.6 s1.6 s
  4. bagan.com.my at 2.2 s2.2 s
  5. bagan.com.my at 2.7 s2.7 s
  6. bagan.com.my at 3.3 s3.3 s
  7. bagan.com.my at 3.8 s3.8 s
  8. bagan.com.my at 4.4 s4.4 s

Speed

6 to fix85
  • Font display

    1.3 s

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

  • Mobile performance score: 85

    85/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    750 ms · 143 KiB

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

  • Improve image delivery

    150 ms · 424 KiB

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

  • Use efficient cache lifetimes

    300 ms · 118 KiB

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

  • Chained critical requests

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

2 checks passed
  • Server response: 431 ms

    431 ms

    Your server sent the HTML in 431 ms, well inside Google's 600 ms guideline.

  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 33 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

3 to fix100
  • Speed Index: 5.3 s

    5.3 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Specialised & Equipped Wholehearted Care Healing begins not…”. Most of its time is resource load delay (2.1 s).

  • First Contentful Paint: 2.0 s

    2.0 s

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 90 ms

    90 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 368 ms

    368 ms

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

  • Largest content (LCP) got 74% faster for real visitors

    -74%

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

  • Time to Interactive: 3.5 s

    3.5 s

    The page is fully interactive after 3.5 s.

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 2 images far larger than shown

    67 KiB

    2 images are downloaded at several times the size a phone draws them, for example bagan-explore-banner-cover2.webp at 1,440 px wide, shown at 390 px. Resized copies would save about 67 KiB.

  • 5 images in older formats

    5 images (260 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 below the first screen load straight away

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

  • About 0.3 g of CO₂ per visit

    0.34 g

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

1 checks passed
  • Page weight: 1.2 MB in 19 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 19 requests on a phone: images 859 KiB (14), fonts 180 KiB (2) and stylesheets 145 KiB (1). That is a lean page.

Accessibility

9 to fixGoogle 8987
  • Invalid ARIA attributes

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

  • [role="img"] and [role="image"] elements must have alternative text (19 elements)

    [role="img"] and [role="image"] elements must have alternative text: 19 elements on the page fail this check, rated serious by axe-core.

  • 15 text elements with low contrast

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

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 8 links without text

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • No robots.txt

    There is no robots.txt at bagan.com.my/robots.txt, the first file search crawlers ask for.

  • 96 internal links, 6 external

    The homepage links to 96 pages on bagan.com.my and 6 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Your trusted healthcare partner in Butterworth, Penang. Experience wholeheartedly care advanced medical services, inclu…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Bagan Specialist Centre - A Wholeheartedly Hospital”.

  • Canonical URL set

    The canonical URL is https://www.bagan.com.my/.

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.bagan.com.my/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (456 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.bagan.com.my/llms.txt (43 KiB, 183 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.bagan.com.my/dialysis-centre is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.bagan.com.my/dialysis-centre has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.bagan.com.my/dialysis-centre has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.bagan.com.my/our-room took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 2 broken images

    2 images failed to load on a phone, for example https://www.bagan.com.my/.

  • 15 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

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

  • About 453 words of copy

    The homepage carries about 453 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 7 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 6 cookies set on arrival

    6

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

  • No consent tool detected

    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.

  • 12 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at bagan.com.my, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Exa Bytes Network Sdn.Bhd.

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on bagan.com.my, including 9 speed issues and 2 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25