Website review, no card needed

aeonretail.com.my logo

aeonretail.com.my website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 83 checks

This review found 40 issues worth fixing on aeonretail.com.my, 16 of them high impact, across 83 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
4.7 s2.8 sMay 30Nov 143.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.9 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.1 s
Jun 27, 20264.3 s
Jul 4, 20264.4 s
Jul 11, 20264.5 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.2 s
Aug 29, 20264.0 s
Sep 5, 20263.8 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.2 s
Oct 31, 20263.2 s
Nov 7, 20263.1 s
Nov 14, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
131 ms81 msMay 30Nov 14100 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026125 ms
Jun 6, 2026115 ms
Jun 13, 2026106 ms
Jun 20, 2026101 ms
Jun 27, 2026100 ms
Jul 4, 202695 ms
Jul 11, 202694 ms
Jul 18, 202692 ms
Jul 25, 202687 ms
Aug 1, 202688 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202689 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 202697 ms
Sep 19, 2026100 ms
Sep 26, 2026101 ms
Oct 3, 2026104 ms
Oct 10, 2026107 ms
Oct 17, 2026115 ms
Oct 24, 2026114 ms
Oct 31, 2026112 ms
Nov 7, 2026109 ms
Nov 14, 2026100 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 aeonretail.com.my (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aeonretail.com.my at 2.1 s2.1 s
  2. aeonretail.com.my at 4.3 s4.3 s
  3. aeonretail.com.my at 6.4 s6.4 s
  4. aeonretail.com.my at 8.5 s8.5 s
  5. aeonretail.com.my at 10.6 s10.6 s
  6. aeonretail.com.my at 12.8 s12.8 s
  7. aeonretail.com.my at 14.9 s14.9 s
  8. aeonretail.com.my at 17.0 s17.0 s

Speed

10 to fix50
  • Use efficient cache lifetimes

    3.5 s · 35.8 MB

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

  • Reduce unused JavaScript

    1.4 s · 7.3 MB

    About 7.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Improve image delivery

    21.3 MB

    21 images could be 21.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hubz752.ai and Google/Doubleclick Ads and others), adding 8.9 MB and 527 ms of main-thread time.

  • Reduce unused CSS

    900 ms · 356 KiB

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

  • Mobile performance score: 50

    50/100

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

  • hubz752.ai adds 146 ms

    146 ms

    hubz752.ai costs a phone 146 ms of main-thread work and 8.3 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.

  • 12 long tasks on the main thread

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

  • Main-thread work: 3.8 s

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

  • Legacy JavaScript

    10 KiB

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

  • 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: 44 ms

    44 ms

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

Core Web Vitals

9 to fix67
  • 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: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Time to Interactive: 71.8 s

    71.8 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (3.7 s).

  • Total Blocking Time: 564 ms

    564 ms

    Scripts block taps and scrolling for 564 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 1.9 s

    1.9 s

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

5 checks passed
  • Real-user INP: 143 ms

    143 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix36
  • 2 images over 500 KB

    2 images weigh 65.8 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 36.5 MB in 87 requests

    36.5 MB

    Your homepage downloads 36.5 MB in 87 requests on a phone: images 27.0 MB (33), scripts 8.8 MB (25) and stylesheets 373 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (66.0 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.

  • An image on the first screen is lazy-loaded

    kl-midtown-website-banner_1024-400x203.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 10.3 g of CO₂ per visit

    10.35 g

    By the Sustainable Web Design model, a visit to your homepage emits about 10.35 g of CO₂e: 1241.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

5 to fixGoogle 9092
  • 16 tap targets too small

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

  • 17 images without alt text

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

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

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

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

  • Headings should not be empty (58 elements)

    Headings should not be empty: 58 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 7775
  • No H1 headline

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

  • 58 links with vague text

    58 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “AEON Retail Malaysia | Leading Shopping Malls, Department Stores & Hypermarkets”.

  • Meta description is long (213 characters)

    Your meta description is 213 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 100 internal links, 13 external

    The homepage links to 100 pages on aeonretail.com.my and 13 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://aeonretail.com.my/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://www.aeonretail.com.my/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (558 words), so crawlers that don't run JavaScript still read it.

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 //trends, whose canonical is https://aeonretail.com.my/trends. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://aeonretail.com.my/glam-beautique and https://aeonretail.com.my/gifts/giftvoucher have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://aeonretail.com.my/kids-republic, https://aeonretail.com.my/electronics, https://aeonretail.com.my/glam-beautique and https://aeonretail.com.my/must-haves 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.

  • 13 pages slow to respond

    https://aeonretail.com.my/grocery, https://aeonretail.com.my/apparel, https://aeonretail.com.my/kids-republic, https://aeonretail.com.my/home-coordy, https://aeonretail.com.my/electronics and https://aeonretail.com.my/glam-beautique and 7 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 58 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 8893
  • 13 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

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

2 to fix70
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  • About 672 words of copy

    The homepage carries about 672 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop-and-Win-emas-website-banner” and “Value-Buy”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop now”, “Sign up” and “Shop-and-Win-emas-website-banner”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 2 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.

  • 17 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Google Cloud

Company

Headquarters
Bentong

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on aeonretail.com.my, including 19 speed issues, 5 SEO issues and 2 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