Programmable

Website review, no card needed

mushiyoke.com logo

mushiyoke.com website review

Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 81 checks

This review found 33 issues worth fixing on mushiyoke.com, 13 of them high impact, across 81 checks. The most urgent: invalid ARIA attributes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.6 s1.1 sMay 30Aug 151.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.5 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
120 ms114 msJun 27Aug 8116 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 2026115 ms
Jul 11, 2026119 ms
Jul 25, 2026118 ms
Aug 1, 2026118 ms
Aug 8, 2026116 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

www.mushiyoke.com (opens in a new tab)
Full-page screenshot of mushiyoke.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mushiyoke.com at 0.6 s0.6 s
  2. mushiyoke.com at 1.2 s1.2 s
  3. mushiyoke.com at 1.8 s1.8 s
  4. mushiyoke.com at 2.4 s2.4 s
  5. mushiyoke.com at 3.0 s3.0 s
  6. mushiyoke.com at 3.6 s3.6 s
  7. mushiyoke.com at 4.2 s4.2 s
  8. mushiyoke.com at 4.8 s4.8 s

Speed

6 to fix77

  • Mobile performance score: 77

    77/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, nofraud.com and Privy and others), adding 583 KiB and 582 ms of main-thread time.

  • Reduce unused JavaScript

    300 ms · 293 KiB

    About 293 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    350 ms

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

  • Google Tag Manager adds 275 ms

    275 ms

    Google Tag Manager costs a phone 275 ms of main-thread work and 298 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.

  • Main-thread work: 2.2 s

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    20 KiB

    About 20 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    14 KiB

    1 image could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    12 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix84

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Total Blocking Time: 485 ms

    485 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 19 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “インセクトシールドでは、虫よけ加工を採用いただけるブランドパートナー様を募集しております。インセクトシールドＯＥＭ加工…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100

  • About 0.5 g of CO₂ per visit

    0.51 g

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

4 checks passed

  • Page weight: 1.8 MB in 136 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 136 requests on a phone: scripts 768 KiB (40), other files 673 KiB (80) and images 296 KiB (7). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 6884

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 links without text

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 12 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091

  • No structured data

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

  • Meta description is long (260 characters)

    Your meta description is 260 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 63 internal links, 36 external

    The homepage links to 63 pages on mushiyoke.com and 36 external pages.

6 checks passed

  • One H1 headline

    Your main headline reads: “インセクトシールドジャパン”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “虫よけ.com : 虫よけ加工衣類オンラインショップ | インセクトシールドジャパン”.

  • Canonical URL set

    The canonical URL is https://www.mushiyoke.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mushiyoke.com/sitemap.xml.

AI search readiness

1 to fix83

  • No Organization structured data

    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.

2 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • llms.txt published

    The site publishes https://www.mushiyoke.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.mushiyoke.com/pages/%E7%92%B0%E5%A2%83-environment, whose canonical is https://www.mushiyoke.com/pages/%e7%92%b0%e5%a2%83-environment. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.mushiyoke.com/pages/insects-we-repel and https://www.mushiyoke.com/pages/what-is-permethrin have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://www.mushiyoke.com/pages/faq, https://www.mushiyoke.com/pages/technology, https://www.mushiyoke.com/pages/insects-we-repel, https://www.mushiyoke.com/pages/what-is-permethrin, https://www.mushiyoke.com/pages/how-does-permethrin-work and https://www.mushiyoke.com/pages/permethrin-safe and 5 others 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.

  • 15 internal pages checked

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

5 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9684

  • 1 broken image

    1 image failed to load on a phone, for example https://www.mushiyoke.com/.

3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    29 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57

  • No call to action on the first screen

    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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

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

  • Only about 142 words

    The homepage has only about 142 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

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

3 checks passed

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 19 other companies contacted

    Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mushiyoke.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Tabs Studio · privy.com · stationmade.com · nfcube.com · nofraud.com · backinstock.org

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on mushiyoke.com, including 11 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25