Website review, no card needed

boody.co.jp logo

boody.co.jp website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 82 checks

This review found 32 issues worth fixing on boody.co.jp, 9 of them high impact, across 82 checks. The most urgent: page weight: 12.9 MB in 530 requests. 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.2 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.9 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
186 ms118 msMay 30Nov 14178 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026126 ms
Jun 6, 2026130 ms
Jun 13, 2026133 ms
Jun 20, 2026136 ms
Jun 27, 2026138 ms
Jul 4, 2026138 ms
Jul 11, 2026137 ms
Jul 18, 2026138 ms
Jul 25, 2026135 ms
Aug 1, 2026136 ms
Aug 8, 2026141 ms
Aug 15, 2026141 ms
Aug 22, 2026144 ms
Aug 29, 2026144 ms
Sep 5, 2026144 ms
Sep 12, 2026148 ms
Sep 19, 2026152 ms
Sep 26, 2026155 ms
Oct 3, 2026157 ms
Oct 10, 2026159 ms
Oct 17, 2026159 ms
Oct 24, 2026161 ms
Oct 31, 2026166 ms
Nov 7, 2026174 ms
Nov 14, 2026178 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

Full-page screenshot of boody.co.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boody.co.jp at 2.2 s2.2 s
  2. boody.co.jp at 4.5 s4.5 s
  3. boody.co.jp at 6.7 s6.7 s
  4. boody.co.jp at 8.9 s8.9 s
  5. boody.co.jp at 11.2 s11.2 s
  6. boody.co.jp at 13.4 s13.4 s
  7. boody.co.jp at 15.6 s15.6 s
  8. boody.co.jp at 17.9 s17.9 s

Speed

13 to fix64
  • Main-thread work: 5.9 s

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

  • Reduce unused JavaScript

    300 ms · 752 KiB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. 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 (Klaviyo, Clarity and Yotpo and others), adding 2.1 MB and 695 ms of main-thread time.

  • Improve image delivery

    650 ms · 170 KiB

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

  • Render-blocking requests

    650 ms

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

  • Use efficient cache lifetimes

    308 KiB

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

  • 2,875 HTML elements

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

  • Klaviyo adds 189 ms

    189 ms

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

  • Yotpo adds 99 ms

    99 ms

    Yotpo costs a phone 99 ms of main-thread work and 294 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 adds 77 ms

    77 ms

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

  • joy.so adds 57 ms

    57 ms

    joy.so costs a phone 57 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.

  • azurefd.net adds 48 ms

    48 ms

    azurefd.net costs a phone 48 ms of main-thread work and 324 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.

  • Reduce unused CSS

    150 ms · 81 KiB

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

  • 5 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • 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: 18 ms

    18 ms

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

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 47.2 s

    47.2 s

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

  • Speed Index: 21.5 s

    21.5 s

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

  • Time to Interactive: 61.6 s

    61.6 s

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

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

  • Largest content (LCP) got 48% slower for real visitors

    +48%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

7 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 136 ms

    136 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 110 ms

    110 ms

    Scripts block the page for only 110 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 12.9 MB in 530 requests

    12.9 MB

    Your homepage downloads 12.9 MB in 530 requests on a phone: fonts 8.2 MB (6), scripts 2.0 MB (187) and other files 1.5 MB (267). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.67 g

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

3 checks passed
  • 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

2 to fixGoogle 9798
  • 5 text elements with low contrast

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 69 images in the HTML carry an alt attribute.

  • 58 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: 58 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 349 internal links, 11 external

    The homepage links to 349 pages on boody.co.jp and 11 external pages.

7 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “竹布のインナーをはじめ、BOODYでは竹布のアイテムを豊富に揃えています。抗菌性や消臭性など、天然の優れた力を持っている竹布はインナーの素材として最適。肌を柔らかさで包んでくれる、竹布の恵みをぜひお試しください。”.

  • One H1 headline

    Your main headline reads: “Boody Japan”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “BOODY JAPAN | 快適さと持続性に注力してつくられたエシカルファッション”.

  • Canonical URL set

    The canonical URL is https://www.boody.co.jp/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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.boody.co.jp/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (411 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://www.boody.co.jp/collections/new-bra-arrivals, https://www.boody.co.jp/collections/new-shorts-arrivals, https://www.boody.co.jp/collections/new-apparel, https://www.boody.co.jp/collections/new-lounge, https://www.boody.co.jp/collections/airarib and https://www.boody.co.jp/collections/bra-bestseller and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://www.boody.co.jp/collections/full-bust took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 40 small tap targets

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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.

  • About 312 words of copy

    The homepage carries about 312 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 1 of them by other companies (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.

  • 49 other companies contacted

    Loading the homepage contacts 49 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 boody.co.jp, 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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Gorgias Live Chat Helpdesk · Microsoft Clarity · Yotpo Product Reviews · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Joy Wishlist · Joy Loyalty Program · hulkapps.com · pickystory.com

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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on boody.co.jp, including 20 speed issues, 1 SEO issue 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