murataen.com website review

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

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

8 third-party services load with your homepage (Shopify, firebaseapp.com and Adobe TypeKit and others), adding 21.3 MB and 277 ms of main-thread time.

Adobe TypeKit costs a phone 54 ms of main-thread work and 20.4 MB 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.

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

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

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

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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 9.0 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 15.5 s. Good is under 3.8 s.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.3 MB in 341 requests on a phone: fonts 19.9 MB (5), other files 1.8 MB (240) and images 1.6 MB (36). Under 2 MB keeps phones on slow connections fast.

26winterEN_slider_04_143dcbae-13a9-4c2b-bea2-321787ca658f.jp 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).

2 images are downloaded at several times the size a phone draws them, for example 500__banner_e7ca56bb-0e29-4267-b7bc-5d709140f6f8.png at 1,301 px wide, shown at 366 px. Resized copies would save about 63 KiB.

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

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

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

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

All page content should be contained by landmarks: 3 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.

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

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

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

Structured data found (Organization and WebSite) but with 4 problems, for example “Organization: logo is not an absolute URL ("https:files/logo.png")”.

The homepage links to 109 pages on murataen.com and 4 external pages.

https://www.murataen.com/pages/category-bannoucha, https://www.murataen.com/collections/clearance-price, https://www.murataen.com/pages/category-nihonzenkoku-umaimonoichi, https://www.murataen.com/pages/category-health-green-tea, https://www.murataen.com/pages/category-food-snacks and https://www.murataen.com/collections/%E6%B5%B7%E5%A4%96%E7%9B%B4%E8%BC%B8%E5%85%A5 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.murataen.com/collections/%E6%B5%B7%E5%A4%96%E7%9B%B4%E8%BC%B8%E5%85%A5, whose canonical is https://www.murataen.com/collections/%e6%b5%b7%e5%a4%96%e7%9b%b4%e8%bc%b8%e5%85%a5. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.murataen.com/pages/category-bannoucha, https://www.murataen.com/pages/category-nihonzenkoku-umaimonoichi, https://www.murataen.com/pages/category-health-green-tea and https://www.murataen.com/pages/category-food-snacks have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.murataen.com/pages/category-bannoucha, https://www.murataen.com/collections/clearance-price, https://www.murataen.com/pages/category-nihonzenkoku-umaimonoichi, https://www.murataen.com/pages/category-health-green-tea, https://www.murataen.com/pages/category-food-snacks and https://www.murataen.com/collections/%E6%B5%B7%E5%A4%96%E7%9B%B4%E8%BC%B8%E5%85%A5 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 38 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://reorder-master.hulkapps.com/css/re-order.css?v=2023-08-31%2002:59:33' from origin …”.

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 41 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 and Google Tag Manager (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 12 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.