Website review, no card needed

ballaholic.jp logo

ballaholic.jp website review

Visit site (opens in a new tab)Reviewed 6 November 202629 issues · 78 checks

This review found 29 issues worth fixing on ballaholic.jp, 12 of them high impact, across 78 checks. The most urgent: page weight: 18.2 MB in 218 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
1.4 s1.0 sMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 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.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
77 ms70 msMay 16Oct 3175 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202674 ms
May 23, 202673 ms
May 30, 202673 ms
Jun 6, 202673 ms
Jun 13, 202673 ms
Jun 20, 202672 ms
Jun 27, 202673 ms
Jul 4, 202672 ms
Jul 11, 202671 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202672 ms
Aug 29, 202674 ms
Sep 5, 202674 ms
Sep 12, 202675 ms
Sep 19, 202675 ms
Sep 26, 202675 ms
Oct 3, 202676 ms
Oct 10, 202676 ms
Oct 17, 202675 ms
Oct 24, 202676 ms
Oct 31, 202675 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 ballaholic.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ballaholic.jp at 0.4 s0.4 s
  2. ballaholic.jp at 0.8 s0.8 s
  3. ballaholic.jp at 1.1 s1.1 s
  4. ballaholic.jp at 1.5 s1.5 s
  5. ballaholic.jp at 1.9 s1.9 s
  6. ballaholic.jp at 2.3 s2.3 s
  7. ballaholic.jp at 2.6 s2.6 s
  8. ballaholic.jp at 3.0 s3.0 s

Speed

2 to fix67
  • Improve image delivery

    450 ms · 8.6 MB

    28 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 67

    67/100

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

  • Reduce unused JavaScript

    150 ms · 221 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hubspot, Shopify and Google CDN and others), adding 471 KiB and 295 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 23 KiB

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

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • Use efficient cache lifetimes

    99 KiB

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    14 KiB

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

  • Minify CSS

    6 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 836 ms of it running JavaScript. That is comfortably low.

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 35.0 s

    35.0 s

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

  • Time to Interactive: 42.4 s

    42.4 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.2 s

    1.2 s

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

  • Real-user TTFB: 345 ms

    345 ms

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 58 ms

    58 ms

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

Images and page weight

5 to fix18
  • Page weight: 18.2 MB in 218 requests

    18.2 MB

    Your homepage downloads 18.2 MB in 218 requests on a phone: images 12.4 MB (51), media 4.3 MB (2) and other files 760 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 9.9 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    9.3 MB

    18 images are downloaded at several times the size a phone draws them, for example SM-Numbering.jpg at 2,250 px wide, shown at 330 px. Resized copies would save about 9.3 MB.

  • 22 images below the first screen load straight away

    22 images further down the page (11.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 8 images in older formats

    8 images (5.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 5.2 g of CO₂ per visit

    5.16 g

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

Accessibility

5 to fixGoogle 9292
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • Title is short (19 characters)

    Your title is only 19 characters: “ballaholicオンラインショップ”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (34 characters)

    Your meta description is only 34 characters: “ストリートボールブランドballaholicの公式オンラインショップ”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 106 internal links, 15 external

    The homepage links to 106 pages on ballaholic.jp and 15 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://ballaholic.jp/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://ballaholic.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 (309 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://ballaholic.jp/pages/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://ballaholic.jp/collections/all, https://ballaholic.jp/collections/custom, https://ballaholic.jp/blogs/style, https://ballaholic.jp/pages/shop-list, https://ballaholic.jp/collections/shorts and https://ballaholic.jp/collections/cotton-tees and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://ballaholic.jp/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 267 words of copy

    The homepage carries about 267 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop List” and “Contact”.

  • 1 short form

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 ballaholic.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Kor Order Limit Quantity · Purchase Limit · TEPO Product Options (Qikify) · amp-cdn.tokyo · mixlogue.jp · nice-team.net · hubapi.com · lipify.jp · Hulk Product Options

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on ballaholic.jp, including 6 speed issues, 3 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