eotd.jp website review

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

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

8 third-party services load with your homepage (YouTube, Shopify and growave.io and others), adding 2.0 MB and 1.3 s of main-thread time.

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

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

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

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

YouTube costs a phone 533 ms of main-thread work and 1,007 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 338 ms of main-thread work and 377 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.

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

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

18 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

12 KiB could be saved by minifying CSS.

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

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

2 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Your homepage downloads 5.3 MB in 349 requests on a phone: images 2.0 MB (85), scripts 1.9 MB (121) and other files 807 KiB (119). Under 2 MB keeps phones on slow connections fast.

EOJ_new_MBN_20.png 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).

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

Elements must only use permitted ARIA attributes: 24 elements on the page fail this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

There are 2 <h1> headlines (“eotd JP” and “eotd JP”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 260 pages on eotd.jp and 7 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.

Your homepage links to https://www.eotd.jp/blogs/events/morumoru-sale-50, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.eotd.jp/blogs/events/pocky-day, https://www.eotd.jp/blogs/events/feel-the-rush-restock-notification, https://www.eotd.jp/collections/fixing, https://www.eotd.jp/collections/trial-pair-%E3%83%9F%E3%83%8B%E3%83%AC%E3%83%B3%E3%82%BA, https://www.eotd.jp/collections/%E4%B9%B1%E8%A6%96%E7%94%A8%E3%82%AB%E3%83%A9%E3%82%B3%E3%83%B3 and https://www.eotd.jp/collections/new-arrivals and 3 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.eotd.jp/collections/trial-pair-%E3%83%9F%E3%83%8B%E3%83%AC%E3%83%B3%E3%82%BA, whose canonical is https://www.eotd.jp/collections/trial-pair-%e3%83%9f%e3%83%8b%e3%83%ac%e3%83%b3%e3%82%ba. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.eotd.jp/collections/trial-pair-%E3%83%9F%E3%83%8B%E3%83%AC%E3%83%B3%E3%82%BA and https://www.eotd.jp/collections/best-sellers 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 87 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 298 words of visible text.

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