yobek.jp website review

10 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

hcaptcha.com costs a phone 2.5 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.

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

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

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

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

A phone's processor spends 7.9 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 CDN and customerfields.com and others), adding 5.2 MB and 3.4 s of main-thread time.

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

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

33 KiB could be saved by minifying CSS.

Shopify costs a phone 128 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.

Google Fonts costs a phone 18 ms of main-thread work and 345 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.

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

7 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 14 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.

Your largest element takes 11.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 17.1 s (Speed Index). Good is under 3.4 s.

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

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

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

Your homepage downloads 9.7 MB in 198 requests on a phone: images 3.5 MB (17), scripts 3.3 MB (53) and HTML 1.3 MB (9). Under 2 MB keeps phones on slow connections fast.

20260417_sp_7_2622x3278_crop_center.jpg weighs 566 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 260629_41591_75fc715c-bd1c-48fe-a8e3-f8324b5d3bab.jpg at 5,837 px wide, shown at 328 px. Resized copies would save about 400 KiB.

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

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

All page content should be contained by landmarks: 2 elements on the page fail 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.

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

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

Your title is only 5 characters: “YOBEK”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'T', ..." "name": TOPPAGE - "... is not va)”.

The homepage links to 94 pages on yobek.jp and 4 external pages.

https://yobek.jp/en-us/pages/wedding and https://yobek.jp/pages/wedding all use the title “WEDDING – YOBEK”. Search engines can't tell which page to show for a search, so each competes with the others.

https://yobek.jp/en-us/pages/about-us, https://yobek.jp/en-us/collections/products, https://yobek.jp/en-us/collections/gift, https://yobek.jp/en-us/collections/pocket, https://yobek.jp/en-us/pages/stockists and https://yobek.jp/en-us/pages/wedding and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://yobek.jp/pages/wedding, whose canonical is https://yobek.jp/en-us/pages/wedding. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://yobek.jp/en-us/pages/about-us, https://yobek.jp/en-us/collections/products, https://yobek.jp/en-us/collections/gift, https://yobek.jp/en-us/collections/pocket, https://yobek.jp/en-us/pages/stockists and https://yobek.jp/en-us/collections/care and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://yobek.jp/en-us/pages/about-us, https://yobek.jp/en-us/collections/products, https://yobek.jp/en-us/collections/gift, https://yobek.jp/en-us/collections/pocket, https://yobek.jp/en-us/pages/wedding and https://yobek.jp/en-us/collections/care and 2 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 28 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.”).

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

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

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