getmantou.com website review

The page goes through 3 redirects before it starts loading, costing about 3.9 s. Link and advertise the final URL directly.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, stryv.com and Google Tag Manager and others), adding 5.6 MB and 1.9 s of main-thread time.

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

Shopify costs a phone 639 ms of main-thread work and 2.2 MB 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.

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

stryv.com costs a phone 441 ms of main-thread work and 1.9 MB 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 costs a phone 368 ms of main-thread work and 996 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.

The HTML itself could arrive about 350 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner mobile.jpg__PID:2c313b78-f35d-4080-a1de-56692e7018af”.

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

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

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

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

7 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 6.7 MB in 468 requests on a phone: scripts 3.1 MB (151), images 1.3 MB (84) and other files 1.1 MB (169). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 24 characters: “MANTOU The Regrowth Duo.”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 49 pages on getmantou.com and 4 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.

The HTML your server sends has 403 of the 804 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to https://getmantou.com/pages/about-us, https://getmantou.com/pages/contact-us and https://getmantou.com/pages/hair-loss, which answer with an error. Visitors hit a dead end and search engines drop them.

https://getmantou.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://getmantou.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://getmantou.com/pages/faqs, https://getmantou.com/products/shop, https://getmantou.com/products/purifying-scalp-shampoo, https://getmantou.com/products/hair-regrowth-tonic, https://getmantou.com/customer_authentication/redirect and https://getmantou.com/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://getmantou.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://getmantou.com/pages/faqs has 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 12 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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 31 cookies, 9 of them by other companies (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 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.