naturelab.com website review

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

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

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

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

8 third-party services load with your homepage (Yotpo, Klaviyo and rebuyengine.com and others), adding 2.1 MB and 1.3 s of main-thread time.

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

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

Klaviyo costs a phone 356 ms of main-thread work and 614 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.

Yotpo costs a phone 357 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.

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

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

rebuyengine.com costs a phone 225 ms of main-thread work and 300 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 page has 2,215 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

9 KiB could be saved by minifying CSS.

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

19 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 17.4 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 19.2 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 4.3 MB in 286 requests on a phone: scripts 2.0 MB (111), images 1.0 MB (57) and other files 751 KiB (94). Under 2 MB keeps phones on slow connections fast.

5 images (166 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.

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

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

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

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.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Your title is 67 characters, so Google will cut it off around 60: “The Japanese Destination for Scalp & Hair Health – NatureLab. TOKYO”.

Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 126 pages on naturelab.com and 9 external pages.

https://naturelab.com/pages/kanso-core-quiz has no meta description, so Google writes the search snippet from whatever text it finds.

https://naturelab.com/collections/all-products, https://naturelab.com/pages/loyalty-rewards, https://naturelab.com/collections/best-sellers, https://naturelab.com/collections/new-arrivals, https://naturelab.com/collections/shampoo-1 and https://naturelab.com/collections/shampoo-copy use the same meta description. A description written for each page earns more clicks.

https://naturelab.com/pages/loyalty-rewards, https://naturelab.com/pages/kanso-core-quiz, https://naturelab.com/pages/faq and https://naturelab.com/collections/product-sets have no <h1> headline, so visitors and search engines get no clear main topic.

https://naturelab.com/products/kiseki-molecular-repair-mizu-hair-oil, https://naturelab.com/products/kiseki-molecular-repair-leave-in-hair-masque and https://naturelab.com/products/saisei-biomimetic-peptide-treatment-essence took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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