foligain.sg website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Bing Ads and others), adding 1.2 MB and 559 ms of main-thread time.

Google Tag Manager costs a phone 441 ms of main-thread work and 635 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 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 420 ms faster on a phone.

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 253 requests on a phone: scripts 1.2 MB (108), other files 868 KiB (87) and images 848 KiB (29). Under 2 MB keeps phones on slow connections fast.

BUY-FOLIGAIN-MINOXIDIL_ONLINE_SINGAPORE_540x.jpg 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).

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

1 dropdown has no label.

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 80 characters, so Google will cut it off around 60: “FOLIGAIN® Singapore | Minoxidil & TRIOXIDIL® for Hair Loss – FOLIGAIN® SINGAPORE”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “TRUSTED. LOVED. PROVEN”). One clear main headline is easier for people and search engines.

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

The homepage links to 190 pages on foligain.sg and 12 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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://foligain.sg/products/foligain%C2%AE-2ddr-hair-regeneration-serum, whose canonical is https://foligain.sg/products/foligain%c2%ae-2ddr-hair-regeneration-serum. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://reorder-master.hulkapps.com/css/re-order.css?v=2025-12-04%2003:54:41' from origin …”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,113 words of visible text.

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

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