fleshlight.jp website review

Signyfyd costs a phone 1.1 s of main-thread work and 281 KiB 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.

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

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

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

8 third-party services load with your homepage (Signyfyd, loox.io and Hexton and others), adding 1.4 MB and 1.7 s of main-thread time.

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

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

About 502 KiB of JavaScript is downloaded but never used on this page.

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

Hexton costs a phone 114 ms of main-thread work and 307 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 107 ms of main-thread work and 368 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.

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

44 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

29 KiB could be saved by minifying JavaScript.

About 26 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

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.

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

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

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide 1”. Most of its time is resource load delay (2.9 s).

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

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

The layout shifts by 0.149 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.8 MB in 366 requests on a phone: images 1.7 MB (112), scripts 1.4 MB (142) and other files 651 KiB (61). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (4 elements).

Your canonical URL points to fleshlight.eu, not fleshlight.jp, so Google may credit that host instead.

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

No XML sitemap at https://fleshlight.jp/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at fleshlight.jp/robots.txt, the first file search crawlers ask for.

Your <h1> is empty.

The homepage links to 179 pages on fleshlight.jp and 23 external pages.

There is no https://fleshlight.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://fleshlight.jp/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://fleshlight.jp/collections/fleshlight-girls and https://fleshlight.jp/collections/birthday-girls have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

Large scripts ship without source maps.

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

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.

The homepage carries about 1,978 words of visible text.