Website review, no card needed

amway.co.jp logo

amway.co.jp website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 84 checks

This review found 34 issues worth fixing on amway.co.jp, 15 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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.6 s1.4 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.5 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.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
85 ms79 msMay 2Oct 1782 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202684 ms
May 9, 202684 ms
May 16, 202683 ms
May 23, 202683 ms
May 30, 202683 ms
Jun 6, 202682 ms
Jun 13, 202680 ms
Jun 20, 202681 ms
Jun 27, 202681 ms
Jul 4, 202682 ms
Jul 11, 202682 ms
Jul 18, 202683 ms
Jul 25, 202682 ms
Aug 1, 202681 ms
Aug 8, 202681 ms
Aug 15, 202680 ms
Aug 22, 202680 ms
Aug 29, 202682 ms
Sep 5, 202682 ms
Sep 12, 202682 ms
Sep 19, 202682 ms
Sep 26, 202680 ms
Oct 3, 202681 ms
Oct 10, 202681 ms
Oct 17, 202682 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 amway.co.jp (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix45
  • Use efficient cache lifetimes

    9.3 s · 15.6 MB

    92 files are served with short cache lifetimes, so returning visitors download them again (15.6 MB).

  • Improve image delivery

    1.3 s · 7.4 MB

    45 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Render-blocking requests

    6.5 s

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

  • Mobile performance score: 45

    45/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Qualtrics, Heap and Tealium and others), adding 1.2 MB and 100 ms of main-thread time.

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 988 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 · 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.

  • Reduce unused JavaScript

    69 KiB

    About 69 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 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).

  • Legacy JavaScript

    13 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 76 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Time to Interactive: 16.6 s

    16.6 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Cumulative Layout Shift: 0.283

    0.283

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

  • 44 images without width and height

    44 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-17, real Chrome visitors' tap response (inp) went from 84 ms to 82 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 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.5 s

    1.5 s

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

  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 425 ms

    425 ms

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix38
  • Page weight: 16.8 MB in 155 requests

    16.8 MB

    Your homepage downloads 16.8 MB in 155 requests on a phone: images 15.5 MB (74), fonts 959 KiB (45) and scripts 240 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 5.2 MB together. On a phone connection a single image that size takes seconds.

  • 34 images in older formats

    34 images (9.3 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.

  • 25 images below the first screen load straight away

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

  • About 4.7 g of CO₂ per visit

    4.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.75 g of CO₂e: 569.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 8693
  • 2 buttons without a name

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

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

    All page content should be contained by landmarks: 24 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.

  • Zoom is disabled

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

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

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 6 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 10089
  • Title is short (28 characters)

    Your title is only 28 characters: “日本アムウェイ(Amway)公式企業サイト|TOPページ”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No robots.txt

    There is no robots.txt at amway.co.jp/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 180 internal links, 61 external

    The homepage links to 180 pages on amway.co.jp and 61 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “日本アムウェイ合同会社(Amway Japan)のオフィシャルサイト。栄養補給食品ニュートリライト(Nutrilite),化粧品ブランドのアーティストリー(Artistry),ホームリビング製品のアムウェイホームの紹介や、アムウェイの企業…”.

  • One H1 headline

    Your main headline reads: “Helping People Live Better Lives”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.amway.co.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://www.amway.co.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.amway.co.jp/about/socialwork/one_by_one/index.html, whose canonical is https://www.amway.co.jp/about/socialwork/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.amway.co.jp/about/value/co_founders/index.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://www.amway.co.jp/brand/index.html, https://www.amway.co.jp/brand/detail/sustainability.html, https://www.amway.co.jp/about/index.html, https://www.amway.co.jp/about/company/index.html, https://www.amway.co.jp/about/company/jpn_company/index.html and https://www.amway.co.jp/about/company/jpn_company/shibuya.html and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 10093
  • 7 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • Only about 56 words

    The homepage has only about 56 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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
  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Heap (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.

  • 4 cookies set on arrival

    4

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 amway.co.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on amway.co.jp, including 12 speed issues, 2 SEO issues and 5 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