simius.tokyo website review

hcaptcha.com costs a phone 2.3 s of main-thread work and 3.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Google CDN and others), adding 5.1 MB and 3.3 s of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

Google CDN costs a phone 321 ms of main-thread work and 736 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 costs a phone 321 ms of main-thread work and 326 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.

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

LoyaltyLion costs a phone 50 ms of main-thread work and 360 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.

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

3 images could be 41 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

20 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 13.3 MB in 327 requests on a phone: fonts 6.0 MB (25), scripts 4.4 MB (95) and HTML 1.3 MB (9). Under 2 MB keeps phones on slow connections fast.

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

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: 1 element on the page fails this check, rated serious by axe-core.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 50 pages on simius.tokyo and 5 external pages.

https://simius.tokyo/collections/all, https://simius.tokyo/collections/outlet, https://simius.tokyo/blogs/beauty-navi/tagged/%E7%BE%8E%E8%82%8C-%E3%82%B7%E3%83%9F-%E3%81%8F%E3%81%99%E3%81%BF and https://simius.tokyo/blogs/beauty-navi/tagged/%E7%B4%AB%E5%A4%96%E7%B7%9A%E5%AF%BE%E7%AD%96 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://simius.tokyo/blogs/beauty-navi/tagged/%E7%BE%8E%E8%82%8C-%E3%82%B7%E3%83%9F-%E3%81%8F%E3%81%99%E3%81%BF, whose canonical is https://simius.tokyo/blogs/beauty-navi/tagged/%e7%be%8e%e8%82%8c-%e3%82%b7%e3%83%9f-%e3%81%8f%e3%81%99%e3%81%bf. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://simius.tokyo/collections/all, https://simius.tokyo/blogs/beauty-navi/tagged/%E7%BE%8E%E8%82%8C-%E3%82%B7%E3%83%9F-%E3%81%8F%E3%81%99%E3%81%BF and https://simius.tokyo/blogs/beauty-navi/tagged/%E7%B4%AB%E5%A4%96%E7%B7%9A%E5%AF%BE%E7%AD%96 have no <h1> headline, so visitors and search engines get no clear main topic.

https://simius.tokyo/collections/outlet, https://simius.tokyo/pages/guide, https://simius.tokyo/collections/simius, https://simius.tokyo/products/subscription, https://simius.tokyo/products/uv-serum-ex and https://simius.tokyo/products/lotion-ex and 8 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 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

3 errors were logged to the browser console while the page loaded, for example “[hCaptcha] Rate limited or network error. Please retry.”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 16 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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.