trollbeads.jp website review

About 638 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

8 images could be 344 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

8 third-party services load with your homepage (posthog.com, Klaviyo and Shopify and others), adding 1.7 MB and 793 ms of main-thread time.

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

posthog.com costs a phone 516 ms of main-thread work and 253 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.

68 KiB could be saved by minifying CSS.

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

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

Klaviyo costs a phone 172 ms of main-thread work and 318 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 Fonts costs a phone 31 ms of main-thread work and 842 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 costs a phone 53 ms of main-thread work and 303 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 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

18 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 54.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “スターダストドリームブレスレット(セット) TAGBO-02250”.

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

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

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

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

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

4 images 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' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.0 MB in 209 requests on a phone: fonts 6.9 MB (13), other files 917 KiB (91) and scripts 843 KiB (70). Under 2 MB keeps phones on slow connections fast.

Hero_Peoples-uniques-2026_mobile.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).

1 image is downloaded at several times the size a phone draws it, for example Untitled_design_-_2026-10-19T140806.392.jpg at 1,080 px wide, shown at 356 px. Resized copies would save about 4 KiB.

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

60 buttons have no accessible name, so screen readers announce just “button”.

4 dropdowns have no label.

21 tap targets are too small or too close together to hit reliably with a finger.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 7 characters: “トロールビーズ”. 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 meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 257 pages on trollbeads.jp and 7 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.

https://www.trollbeads.jp/collections/bn2026-teaser and https://www.trollbeads.jp/collections/beads-and-pendants have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.trollbeads.jp/collections/beads and https://www.trollbeads.jp/collections/%E3%83%93%E3%83%BC%E3%82%BA%E3%81%AE%E3%82%B3%E3%83%94%E3%83%BC use the same meta description. A description written for each page earns more clicks.

https://www.trollbeads.jp/collections/bn2026-teaser, https://www.trollbeads.jp/collections/new_in, https://www.trollbeads.jp/collections/beads and https://www.trollbeads.jp/collections/%E3%83%93%E3%83%BC%E3%82%BA%E3%81%AE%E3%82%B3%E3%83%94%E3%83%BC have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.trollbeads.jp/collections/bn2026-teaser and https://www.trollbeads.jp/collections/jewelry 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 114 found) and read each the way a search engine does.

4 images failed to load on a phone, for example https://www.trollbeads.jp/.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

The homepage has only about 102 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, Klaviyo and Meta 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 14 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.