mochidoki.com website review

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

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

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

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

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 (Yotpo, Klaviyo and talkshop.live and others), adding 1.1 MB and 545 ms of main-thread time.

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

Yotpo costs a phone 150 ms of main-thread work and 295 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.

Klaviyo costs a phone 147 ms of main-thread work and 311 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.

12 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 213 requests on a phone: scripts 1.3 MB (83), images 1.1 MB (30) and other files 641 KiB (71). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (223 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Your title is 77 characters, so Google will cut it off around 60: “Mochidoki - Mochi Ice Cream – Mochidoki - The Premium Mochi Ice Cream Company”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 63 pages on mochidoki.com and 10 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.

There is no https://mochidoki.com/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://mochidoki.com/collections/all, https://mochidoki.com/pages/corporate-events and https://mochidoki.com/pages/wholesale-inquiries 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://mochidoki.com/pages/corporate-events, whose canonical is https://mochidoki.com/pages/gifting-events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mochidoki.com/pages/corporate-events, https://mochidoki.com/pages/store-locator, https://mochidoki.com/pages/location and https://mochidoki.com/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Social proof on the homepage: 38 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 871 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, LinkedIn Insight and Meta Pixel and 2 mores (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 18 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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.