Website review, no card needed
amazingraze.com.my website review
Visit site (opens in a new tab)Reviewed 6 November 202646 issues · 93 checks
This review found 46 issues worth fixing on amazingraze.com.my, 13 of them high impact, across 93 checks. The most urgent: mobile performance score: 44. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #86,668 of 124,051 reviewed websitesbeats 26%
- #54,482 of 69,761 online storesbeats 18%
- #51,181 of 63,450 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 168 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 174 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 191 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 182 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 186 ms |
| Sep 12, 2026 | 182 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 182 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
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.3 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Clarity and others), adding 1.6 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
900 KiBAbout 900 KiB of JavaScript is downloaded but never used on this page.
Shopify adds 843 ms
843 msShopify costs a phone 843 ms of main-thread work and 335 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.
Google Tag Manager adds 699 ms
699 msGoogle Tag Manager costs a phone 699 ms of main-thread work and 543 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
600 ms · 125 KiBAbout 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
150 ms · 484 KiB20 images could be 484 KiB 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.
Use efficient cache lifetimes
200 ms · 319 KiB24 files are served with short cache lifetimes, so returning visitors download them again (319 KiB).
Render-blocking requests
500 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 365 ms. During a long task the page ignores taps.
1,519 HTML elements
The page has 1,519 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
93 KiBPolyfills for old browsers add 93 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.1 s
28.1 sThe page becomes fully interactive after 28.1 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 802 ms
802 msScripts block taps and scrolling for 802 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 168 ms to 182 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-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 189 ms
189 msReal visitors wait 189 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 594 ms
594 msReal visitors wait 594 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.045
0.045The layout barely moves while loading (CLS 0.045, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 296 requests
4.9 MBYour homepage downloads 4.9 MB in 296 requests on a phone: scripts 2.1 MB (109), images 1.5 MB (48) and other files 866 KiB (111). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Unwrap_Paradise_-_Phuket_Trip_Mobile_MY.png 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).
2 images far larger than shown
71 KiB2 images are downloaded at several times the size a phone draws them, for example Trial_Kit_1021bdba-e7c3-41ad-88c0-fe1d3cfc4b45.png at 1,440 px wide, shown at 358 px. Resized copies would save about 71 KiB.
2 images in older formats
2 images (80 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.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (18 elements)
Elements must only use permitted ARIA attributes: 18 elements on the page fail this check, rated serious by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (65 elements)
All page content should be contained by landmarks: 65 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
76 internal links, 8 external
The homepage links to 76 pages on amazingraze.com.my and 8 external pages.
5 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Natural Healthy Snacks & Breakfast - Amazin' Graze Malaysia”.
Canonical URL set
The canonical URL is https://www.amazingraze.com.my/.
Structured data in place
Structured data found: Organization and WebSite.
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.amazingraze.com.my/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (905 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.amazingraze.com.my/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.amazingraze.com.my/collections/christmas-2026 and https://www.amazingraze.com.my/pages/loyalty have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.amazingraze.com.my/collections/best-seller/products/bundle-of-2-protein-blend-tub-700g, whose canonical is https://www.amazingraze.com.my/products/bundle-of-2-protein-blend-tub-700g. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.amazingraze.com.my/pages/loyalty has no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.amazingraze.com.my/collections/all, https://www.amazingraze.com.my/collections/nuts, https://www.amazingraze.com.my/collections/gift-bundle, https://www.amazingraze.com.my/pages/our-story and https://www.amazingraze.com.my/pages/corporate-page took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “$ is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 778 words of copy
The homepage carries about 778 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “Login / Register”.
8 calls to action
The homepage has 8 calls to action, for example “SHOP”, “Shop now” and “SIGN UP”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 114 testimonial or review blocks, 17 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
47 other companies contacted
Loading the homepage contacts 47 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 amazingraze.com.my, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Ta Labels Badges · Judge Me Reviews · Microsoft Clarity · Bundler Bundles App · Eg Auto Add To Cart · Dondy Whatsapp Chat Widget · Automatic Discounts Upsells · cloudfront.net · jsdelivr.net · nice-team.net
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
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 13 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on amazingraze.com.my, including 20 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.