Website review, no card needed

farmasisihat.com logo

farmasisihat.com website review

Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 81 checks

This review found 35 issues worth fixing on farmasisihat.com, 10 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
2.5 s1.9 sMay 16Oct 102.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.1 s
May 30, 20262.0 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.3 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.3 s

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 farmasisihat.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. farmasisihat.com at 0.7 s0.7 s
  2. farmasisihat.com at 1.5 s1.5 s
  3. farmasisihat.com at 2.2 s2.2 s
  4. farmasisihat.com at 3.0 s3.0 s
  5. farmasisihat.com at 3.7 s3.7 s
  6. farmasisihat.com at 4.4 s4.4 s
  7. farmasisihat.com at 5.2 s5.2 s
  8. farmasisihat.com at 5.9 s5.9 s

Speed

12 to fix65
  • Reduce unused JavaScript

    2.2 s · 370 KiB

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

  • Use efficient cache lifetimes

    1.7 s · 203 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    800 ms · 262 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Google Tag Manager and Shopify and others), adding 1.8 MB and 695 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 60 KiB

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

  • Main-thread work: 3.2 s

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

  • Google Maps adds 181 ms

    181 ms

    Google Maps costs a phone 181 ms of main-thread work and 711 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.

  • Shopify adds 158 ms

    158 ms

    Shopify costs a phone 158 ms of main-thread work and 397 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.

  • Google Tag Manager adds 161 ms

    161 ms

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

  • 1,884 HTML elements

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

  • Forced reflow

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 17.3 s

    17.3 s

    Your largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 17.5 s

    17.5 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-31, 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).

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 140 ms

    140 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

3 to fix74
  • Page weight: 3.4 MB in 281 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 281 requests on a phone: scripts 1.4 MB (129), images 1.1 MB (53) and other files 666 KiB (83). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 1 image far larger than shown

    66 KiB

    1 image is downloaded at several times the size a phone draws it, for example ChatGPT_Image_12_Jun_2026_04_16_46_PTG.png at 1,983 px wide, shown at 390 px. Resized copies would save about 66 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (47 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fixGoogle 8893
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Hidden but focusable

    8 elements hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 18 links without text

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

  • 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 (h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 10083
  • No H1 headline

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

  • Title is long (87 characters)

    Your title is 87 characters, so Google will cut it off around 60: “Farmasi Sihat | Farmasi Berdaftar untuk Diabetes & Kolesterol – Farmasi Sihat Sdn. Bhd.”.

  • 76 internal links, 14 external

    The homepage links to 76 pages on farmasisihat.com and 14 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Farmasi Sihat ialah farmasi berdaftar di Johor yang menyediakan produk kesihatan, konsultasi diabetes, kolesterol, nutr…”.

  • Canonical URL set

    The canonical URL is https://farmasisihat.com/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://farmasisihat.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://farmasisihat.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 8 pages without a meta description

    https://farmasisihat.com/collections/all, https://farmasisihat.com/pages/store-locator, https://farmasisihat.com/collections/health-food-beverage, https://farmasisihat.com/collections/health-supplement, https://farmasisihat.com/collections/personal-care and https://farmasisihat.com/collections/skincare and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://farmasisihat.com/pages/shop, https://farmasisihat.com/pages/store-locator and https://farmasisihat.com/collections have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://farmasisihat.com/collections took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Google Maps JavaScript API error: BillingNotEnabledMapError https://developers.google.com/maps/documentation/javascript…”.

2 checks passed
  • Tap targets are thumb-sized

    41 of 41 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix80
  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • Only about 238 words

    The homepage has only about 238 words of visible text; thin pages give Google and first-time buyers little to go on.

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop By Brand”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop”, “Shop By Brand” and “Shop Now”.

  • 12 short forms

    12 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 6 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.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 farmasisihat.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ot Theme Sections · Optis Color Swatch · Judge Me Reviews · Gempages Builder · Pagefly Ai Page Builder · Ot Section Builder · Pop Convert

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on farmasisihat.com, including 16 speed issues, 2 SEO issues and 3 conversion gaps. 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