Website review, no card needed

amway.id logo

amway.id website review

Visit site (opens in a new tab)Reviewed 28 October 202651 issues · 89 checks

This review found 51 issues worth fixing on amway.id, 25 of them high impact, across 89 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
6.9 s6.4 sMay 9Oct 246.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.8 s
May 16, 20266.8 s
May 23, 20266.8 s
May 30, 20266.8 s
Jun 6, 20266.8 s
Jun 13, 20266.8 s
Jun 20, 20266.8 s
Jun 27, 20266.9 s
Jul 4, 20266.9 s
Jul 11, 20266.8 s
Jul 18, 20266.8 s
Jul 25, 20266.7 s
Aug 1, 20266.7 s
Aug 8, 20266.7 s
Aug 15, 20266.7 s
Aug 22, 20266.6 s
Aug 29, 20266.6 s
Sep 5, 20266.6 s
Sep 12, 20266.5 s
Sep 19, 20266.5 s
Sep 26, 20266.5 s
Oct 3, 20266.6 s
Oct 10, 20266.6 s
Oct 17, 20266.6 s
Oct 24, 20266.6 s
Real-visitor tap response (INP)75th percentile, phones
425 ms363 msMay 9Oct 24376 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026395 ms
May 16, 2026394 ms
May 23, 2026396 ms
May 30, 2026396 ms
Jun 6, 2026384 ms
Jun 13, 2026376 ms
Jun 20, 2026373 ms
Jun 27, 2026370 ms
Jul 4, 2026384 ms
Jul 11, 2026391 ms
Jul 18, 2026394 ms
Jul 25, 2026397 ms
Aug 1, 2026410 ms
Aug 8, 2026418 ms
Aug 15, 2026417 ms
Aug 22, 2026411 ms
Aug 29, 2026394 ms
Sep 5, 2026386 ms
Sep 12, 2026381 ms
Sep 19, 2026381 ms
Sep 26, 2026381 ms
Oct 3, 2026379 ms
Oct 10, 2026378 ms
Oct 17, 2026376 ms
Oct 24, 2026376 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.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amway.id at 0.6 s0.6 s
  2. amway.id at 1.2 s1.2 s
  3. amway.id at 1.8 s1.8 s
  4. amway.id at 2.4 s2.4 s
  5. amway.id at 3.1 s3.1 s
  6. amway.id at 3.7 s3.7 s
  7. amway.id at 4.3 s4.3 s
  8. amway.id at 4.9 s4.9 s

Speed

9 to fix54
  • Use efficient cache lifetimes

    8.0 s · 1.7 MB

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

  • Render-blocking requests

    6.5 s

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

  • Improve image delivery

    3.8 s · 974 KiB

    16 images could be 974 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 216 KiB

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

  • Reduce unused CSS

    1.1 s · 252 KiB

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

  • Minify JavaScript

    1.1 s · 183 KiB

    183 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 64). Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 2.7 s

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

  • 1,882 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (datadome.co, Clarity and Tealium and others), adding 172 KiB and 209 ms of main-thread time.

  • Minify CSS

    150 ms · 42 KiB

    42 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    50 ms · 25 KiB

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

11 to fix0
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 7.5 s

    7.5 s

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

  • Real-user CLS: 0.37

    0.37

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

  • Real-user FCP: 6.6 s

    6.6 s

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

  • Real-user TTFB: 3.9 s

    3.9 s

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

  • Largest Contentful Paint: 24.4 s

    24.4 s

    Your largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ID_homepage_mobile_promo durables.jpg”.

  • Time to Interactive: 24.5 s

    24.5 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

    The first text or image appears after 6.8 s on a phone. Good is under 1.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.

  • Real-user INP: 392 ms

    392 ms

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

  • 24 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Total Blocking Time: 133 ms

    133 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

3 to fix50
  • Page weight: 4.4 MB in 300 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 300 requests on a phone: images 2.0 MB (63), scripts 1.5 MB (203) and fonts 615 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (655 KiB) 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.

  • 2 images far larger than shown

    78 KiB

    2 images are downloaded at several times the size a phone draws them, for example ID_homepage_mobile_promo durables.jpg at 1,563 px wide, shown at 390 px. Resized copies would save about 78 KiB.

  • 4 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.23 g

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

Accessibility

8 to fixGoogle 7887
  • 3 buttons without a name

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • Malformed lists

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

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

  • 27 form fields without a label

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h3 → h6, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 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: 43 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9270
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (25 characters)

    Your title is only 25 characters: “Amway Indonesia | Beranda”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 122 internal links, 31 external

    The homepage links to 122 pages on amway.id and 31 external pages.

3 checks passed
  • Meta description: 83 characters

    Your meta description is 83 characters: “Amway adalah perusahaan direct selling global terbesar dan nomor 1 (satu) di dunia.”.

  • 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://www.amway.id/id/sitemap.xml.

AI search readiness

1 to fix88
  • 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.id/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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,272 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://www.amway.id/id/contactus, https://www.amway.id/id/selfHelp, https://www.amway.id/id/register-landing-page, https://www.amway.id/id/promotions-landing, https://www.amway.id/id/c/foodsupplementvitamin and https://www.amway.id/id/c/healthybeverages and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.amway.id/id/contactus has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.amway.id/id/contactus, https://www.amway.id/id/selfHelp, https://www.amway.id/id/register-landing-page, https://www.amway.id/id/c/foodsupplementvitamin, https://www.amway.id/id/c/healthybeverages and https://www.amway.id/id/c/weightmanagement and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 9 broken images

    9 images failed to load on a phone, for example https://www.amway.id/id/.

  • 16 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 405 ()”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • A 9-field form

    Your longest form asks for 9 fields (1 required). Every extra field lowers completion.

  • Only about 238 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 1 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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Vue.js
Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on amway.id, including 20 speed issues, 6 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