kaiwachimerch.com website review

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

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

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

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

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

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

eventcalendarapp.com costs a phone 193 ms of main-thread work and 356 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.

5 third-party services load with your homepage (eventcalendarapp.com, Klaviyo and Shopify and others), adding 764 KiB and 253 ms of main-thread time.

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

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

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

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.

2 KiB could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 169 requests on a phone: images 1.5 MB (16), other files 684 KiB (75) and scripts 673 KiB (62). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 15 characters: “KAI WACHI MUSIC”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 46 pages on kaiwachimerch.com and 9 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.kaiwachimusic.com/collections/all-products, https://www.kaiwachimusic.com/collections/heavyweight-club, https://www.kaiwachimusic.com/pages/music, https://www.kaiwachimusic.com/pages/tour, https://www.kaiwachimusic.com/pages/skullteam and https://www.kaiwachimusic.com/collections/baseball-jersey and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kaiwachimusic.com/pages/music, https://www.kaiwachimusic.com/pages/tour and https://www.kaiwachimusic.com/pages/skullteam 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.

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

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.

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

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