Website review, no card needed

aumnie.jp logo

aumnie.jp website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 78 checks

This review found 38 issues worth fixing on aumnie.jp, 16 of them high impact, across 78 checks. The most urgent: avoid multiple page redirects. 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
3.0 s2.1 sMay 16Oct 102.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Aug 8, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 19, 20262.9 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
113 ms90 msJun 27Oct 10107 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 202693 ms
Jul 11, 202696 ms
Jul 18, 202699 ms
Sep 19, 2026109 ms
Sep 26, 2026110 ms
Oct 3, 2026109 ms
Oct 10, 2026107 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 aumnie.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aumnie.jp at 0.5 s0.5 s
  2. aumnie.jp at 1.0 s1.0 s
  3. aumnie.jp at 1.5 s1.5 s
  4. aumnie.jp at 2.0 s2.0 s
  5. aumnie.jp at 2.5 s2.5 s
  6. aumnie.jp at 3.0 s3.0 s
  7. aumnie.jp at 3.5 s3.5 s
  8. aumnie.jp at 4.0 s4.0 s

Speed

11 to fix37
  • Avoid multiple page redirects

    14.1 s

    The page goes through 2 redirects before it starts loading, costing about 14.1 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    3.5 s · 669 KiB

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

  • Use efficient cache lifetimes

    1.6 s · 332 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (aumnie.com, csell.co and Shopify and others), adding 2.6 MB and 752 ms of main-thread time.

  • Improve image delivery

    600 ms · 78 KiB

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

  • Reduce unused CSS

    320 ms · 50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 320 ms faster on a phone.

  • aumnie.com adds 182 ms

    182 ms

    aumnie.com costs a phone 182 ms of main-thread work and 1.5 MB 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: 3.1 s

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

  • Privy adds 99 ms

    99 ms

    Privy costs a phone 99 ms of main-thread work and 296 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.

  • Legacy JavaScript

    200 ms · 65 KiB

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

  • Duplicated JavaScript

    100 ms · 8 KiB

    8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • Document request latency

    100 ms

    The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix41
  • Largest Contentful Paint: 23.7 s

    23.7 s

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

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • First Contentful Paint: 5.5 s

    5.5 s

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

  • Cumulative Layout Shift: 0.425

    0.425

    The layout shifts by 0.425 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.6 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.

1 checks passed
  • Total Blocking Time: 53 ms

    53 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.8 MB in 427 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 427 requests on a phone: scripts 1.8 MB (140), images 1.5 MB (36) and other files 1.1 MB (223). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    29 KiB

    2 images are downloaded at several times the size a phone draws them, for example 3_7d88c3b2-42ce-4f74-a87d-643ecfefaa90_2048x.png at 1,366 px wide, shown at 390 px. Resized copies would save about 29 KiB.

  • About 1.4 g of CO₂ per visit

    1.35 g

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

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

Accessibility

8 to fixGoogle 7385
  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 10 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 7 failed. 1 more 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.

  • 2 H1 headlines

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

  • 227 internal links, 1 external

    The homepage links to 227 pages on aumnie.jp and 1 external page.

6 checks passed
  • Meta description: 105 characters

    Your meta description is 105 characters: “アムニー は世界で最も美しく、多様な文化が混在するカナダの西海岸で誕生したヨガウェアを中心としたライフスタイルブランドです。 ヨガウエア・トレーニング・スポーツウエアの購入はアムニー公式サイトからご覧ください。”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “カナダ発ヨガ・スポーツウエアのアムニー公式オンラインショップ – AUMNIE JAPAN”.

  • Canonical URL set

    The canonical URL is https://aumnie.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://aumnie.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.

  • No llms.txt

    There is no https://aumnie.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://aumnie.jp/collections/2026best, https://aumnie.jp/collections/all-item, https://aumnie.jp/collections/tennis, https://aumnie.jp/collections/white-1 and https://aumnie.jp/collections/white have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    9 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 21 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 69 words

    The homepage has only about 69 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 1 call to action

    The homepage has 1 call to action, for example “SHOP NOW”.

  • 1 short form

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 25 cookies set on arrival

    25

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 aumnie.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

Klaviyo Email Marketing Sms · Reamaze Live Chat Helpdesk · Event Promotion Bar · privy.com · csell.co · chimpstatic.com · azureedge.net · hextom.com · Swym Wishlist Plus

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 38 issues on aumnie.jp, including 17 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