bape.com website review

About 605 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 1.5 MB and 678 ms of main-thread time.

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

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

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

Shopify costs a phone 133 ms of main-thread work and 327 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 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.

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

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

13 KiB could be saved by minifying CSS.

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

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

2 KiB could be saved by minifying JavaScript.

Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NEWS【飛び先変更なし】”.

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

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

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

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

Your homepage downloads 8.2 MB in 313 requests on a phone: images 4.0 MB (64), scripts 2.2 MB (106) and other files 897 KiB (122). Under 2 MB keeps phones on slow connections fast.

1 image (88 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.

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

[role]s are not contained by their required parent element (2 elements).

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

1 dropdown has no label.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Elements with visible text labels do not have matching accessible names. (9 elements).

Your title is only 14 characters: “A BATHING APE®”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

The homepage links to 323 pages on bape.com and 70 external pages.

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.

/collections/all, /mens-all, /ladies-all, /kids-all and /pages/redirct-accessories all use the title “全商品 | bape.com”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/blogs/news/bapecard-collection, /blogs/news/mr-25fw, /blogs/news/bapeblack-fw25, /blogs/news/apee-25fw, /collections/all and /all and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /all, whose canonical is /collections/new-in?type=product. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

62 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 error was logged to the browser console while the page loaded, for example “Failed to fetch dynamically imported module: https://shopify-gtm-suite.getelevar.com/configs/48d6af47df6474a1a3f72b2037…”.

Large scripts ship without source maps.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://jp.bape.com/kids-all.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bape.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

DMARC is set to p=none, so mail pretending to be bape.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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