Website review, no card needed

undefeated.jp logo

undefeated.jp website review

Visit site (opens in a new tab)Reviewed 7 November 202627 issues · 76 checks

This review found 27 issues worth fixing on undefeated.jp, 9 of them high impact, across 76 checks. The most urgent: render-blocking 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.0 s822 msMay 16Oct 31893 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026974 ms
May 23, 2026913 ms
May 30, 2026906 ms
Jun 6, 2026909 ms
Jun 13, 2026951 ms
Jun 20, 2026978 ms
Jun 27, 2026966 ms
Jul 4, 2026993 ms
Jul 11, 2026871 ms
Jul 18, 2026844 ms
Jul 25, 2026849 ms
Aug 1, 2026848 ms
Aug 8, 2026894 ms
Aug 15, 2026923 ms
Aug 22, 2026943 ms
Aug 29, 2026977 ms
Sep 5, 2026992 ms
Sep 12, 2026991 ms
Sep 19, 2026980 ms
Sep 26, 2026981 ms
Oct 3, 2026978 ms
Oct 10, 2026971 ms
Oct 17, 2026961 ms
Oct 24, 2026946 ms
Oct 31, 2026893 ms
Real-visitor tap response (INP)75th percentile, phones
57 ms46 msMay 16Oct 3153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202653 ms
May 23, 202653 ms
May 30, 202654 ms
Jun 6, 202654 ms
Jun 13, 202655 ms
Jun 20, 202656 ms
Jun 27, 202654 ms
Jul 4, 202654 ms
Jul 11, 202650 ms
Jul 18, 202648 ms
Jul 25, 202648 ms
Aug 1, 202647 ms
Aug 8, 202647 ms
Aug 15, 202649 ms
Aug 22, 202651 ms
Aug 29, 202654 ms
Sep 5, 202655 ms
Sep 12, 202653 ms
Sep 19, 202652 ms
Sep 26, 202652 ms
Oct 3, 202652 ms
Oct 10, 202653 ms
Oct 17, 202652 ms
Oct 24, 202653 ms
Oct 31, 202653 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 undefeated.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix78
  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 78

    78/100

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

  • Improve image delivery

    332 KiB

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

  • Font display

    200 ms

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

  • Reduce unused JavaScript

    150 ms · 46 KiB

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

  • Minify JavaScript

    150 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 30 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (jQuery CDN, Shopify and minmaxify.com and others), adding 253 KiB and 76 ms of main-thread time.

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    12 KiB

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 6.6 s

    6.6 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 12 images without width and height

    12 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 53 ms to 53 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

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

9 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: 70 ms

    70 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 338 ms

    338 ms

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

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.026

    0.026

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

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

2 to fix63
  • Page weight: 9.5 MB in 163 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 163 requests on a phone: media 7.5 MB (2), images 860 KiB (21) and other files 747 KiB (86). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (374 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (144 KiB) is 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 2.7 g of CO₂ per visit

    2.70 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 7991
  • 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.

  • 1 tap target too small

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

  • 6 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 6 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • No structured data

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

  • One H1 headline

    Your <h1> is empty.

  • 70 internal links, 2 external

    The homepage links to 70 pages on undefeated.jp and 2 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “2002年、ロサンゼルスのラ・ブレア地区で誕生したUNDEFEATED。ブランドスローガンは”勝利・いかなる脅威に屈しない”。創業当時と変わらぬ初期衝動を体現し、世界中で最もエキサイティングなフットウェアとアパレルを世界各地に届けている。”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Undefeated Japan – UNDEFEATED JAPAN”.

  • Canonical URL set

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

  • 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://undefeated.jp/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://undefeated.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://undefeated.jp/collections/undefeated is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://undefeated.jp/collections/mens-foot-wear, https://undefeated.jp/collections/womens-foot-wear, https://undefeated.jp/collections/mens-apparel, https://undefeated.jp/collections/tops, https://undefeated.jp/collections/tees and https://undefeated.jp/collections/short and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://undefeated.jp/collections/tees, https://undefeated.jp/collections/short, https://undefeated.jp/collections/outerwear and https://undefeated.jp/collections/underwear took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

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

  • Only about 102 words

    The homepage has only about 102 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.

1 checks passed
  • 3 short forms

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

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 undefeated.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Minmaxify Order Limits

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 27 issues on undefeated.jp, including 7 speed issues, 2 SEO issues and 6 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