royalmikawa.com website review

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

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

About 53 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

loox.io costs a phone 187 ms of main-thread work and 829 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.

6 third-party services load with your homepage (loox.io, jQuery CDN and shopclimb.com and others), adding 949 KiB and 218 ms of main-thread time.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

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 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blue Lagoon”.

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

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

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

1 image 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 2.3 MB in 222 requests on a phone: other files 1.0 MB (151), images 967 KiB (44) and scripts 248 KiB (17). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Ek0lV7whAGP.jpg at 400 px wide, shown at 120 px. Resized copies would save about 10 KiB.

1 image (54 KiB) is 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 0.66 g of CO₂e: 79.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

The homepage links to 19 pages on royalmikawa.com and 1 external page.

https://royalmikawa.com/collections/all and https://royalmikawa.com/collections/frontpage have no meta description, so Google writes the search snippet from whatever text it finds.

https://royalmikawa.com/collections/frontpage/products/blue-lagoon, https://royalmikawa.com/collections/frontpage/products/oxwood, https://royalmikawa.com/collections/frontpage/products/aged-willow, https://royalmikawa.com/collections/frontpage/products/coral-reef, https://royalmikawa.com/collections/frontpage/products/athens and https://royalmikawa.com/collections/frontpage/products/desert-sand and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://royalmikawa.com/collections/frontpage/products/blue-lagoon, whose canonical is https://royalmikawa.com/products/blue-lagoon. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://royalmikawa.com/collections/all and https://royalmikawa.com/collections/frontpage 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 12 pages linked from your homepage and read each the way a search engine does.

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

Opening the homepage sets 6 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.