loopearplugs.jp website review

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

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

8 third-party services load with your homepage (Google Tag Manager, yougreencolumn.com and Shopify and others), adding 10.0 MB and 294 ms of main-thread time.

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

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

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

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

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

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

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

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

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.9 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 9.3 s. Good is under 3.8 s.

Real visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors wait 978 ms for your server to start answering (75th percentile). Good is under 800 ms.

Visually, the page fills in at 5.4 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 231 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 20.9 MB in 306 requests on a phone: media 16.7 MB (8), fonts 1.2 MB (45) and images 1.1 MB (60). Under 2 MB keeps phones on slow connections fast.

Background_container_-_portrait_1.jpg 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 5.91 g of CO₂e: 709.2 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.

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

Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'L', ..." "logo": Liquid err"... is not va)”.

The homepage links to 137 pages on loopearplugs.jp and 6 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.

https://www.loopearplugs.jp/products/build-your-bundle, https://www.loopearplugs.jp/collections/accessories and https://www.loopearplugs.jp/pages/compare-loop-earplugs have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.loopearplugs.jp/pages/%E7%9D%A1%E7%9C%A0%E7%94%A8%E3%81%AE%E3%82%A4%E3%83%A4%E3%83%BC%E3%83%97%E3%83%A9%E3%82%B0, whose canonical is https://www.loopearplugs.jp/pages/%e7%9d%a1%e7%9c%a0%e7%94%a8%e3%81%ae%e3%82%a4%e3%83%a4%e3%83%bc%e3%83%97%e3%83%a9%e3%82%b0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.loopearplugs.jp/collections/all-products, https://www.loopearplugs.jp/collections/accessories and https://www.loopearplugs.jp/pages/help-me-choose have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.loopearplugs.jp/products/dream, https://www.loopearplugs.jp/products/experience-plus, https://www.loopearplugs.jp/products/quiet and https://www.loopearplugs.jp/products/engage 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 40 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

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

Social proof on the homepage: 89 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.

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

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