Website review, no card needed
mtradeasia.com website review
Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 78 checks
This review found 38 issues worth fixing on mtradeasia.com, 12 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 211 ms |
| May 16, 2026 | 213 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 205 ms |
| Jun 6, 2026 | 206 ms |
| Jun 13, 2026 | 205 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 213 ms |
| Jul 4, 2026 | 216 ms |
| Jul 11, 2026 | 215 ms |
| Jul 18, 2026 | 212 ms |
| Jul 25, 2026 | 207 ms |
| Aug 1, 2026 | 200 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 181 ms |
| Oct 24, 2026 | 183 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
Speed
Render-blocking requests
2.2 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Reduce unused JavaScript
1.1 s · 690 KiBAbout 690 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 84). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 932 KiB and 790 ms of main-thread time.
Improve image delivery
705 KiB2 images could be 705 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
600 ms · 98 KiBAbout 98 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.
Google Tag Manager adds 509 ms
509 msGoogle Tag Manager costs a phone 509 ms of main-thread work and 639 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 285 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
258 KiB20 files are served with short cache lifetimes, so returning visitors download them again (258 KiB).
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 50 ms
50 msYour server sent the HTML in 50 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.
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Asia’s Leader in Money Services, Digital Payments & Micro-I…”.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Real-user TTFB: 821 ms
821 msReal visitors wait 821 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 261 ms
261 msScripts block taps and scrolling for 261 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 211 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 15.7 MB in 76 requests
15.7 MBYour homepage downloads 15.7 MB in 76 requests on a phone: media 13.2 MB (1), scripts 1.4 MB (33) and images 1.0 MB (17). Under 2 MB keeps phones on slow connections fast.
About 4.5 g of CO₂ per visit
4.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.46 g of CO₂e: 534.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h1 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 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
Title is short (25 characters)
Your title is only 25 characters: “Merchantrade Asia Sdn Bhd”. 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.
5 H1 headlines
There are 5 <h1> headlines (“Asia’s Leader in Money Services, Digital Payments…”, “Advocating Progress by Transforming Communities” and “29 Years of Industry Excellence”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
26 internal links, 8 external
The homepage links to 26 pages on mtradeasia.com and 8 external pages.
4 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Asia's leader in Money Services, Digital Payments & Mobile Communications. Discover innovative Personal & Business Prod…”.
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://democorp.digitalmta.com/sitemap.xml.
AI search readiness
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://mtradeasia.com/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 (269 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://mtradeasia.com/insure is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://mtradeasia.com/main/valyou has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages share a meta description
https://mtradeasia.com/about, https://mtradeasia.com/sustainability, https://mtradeasia.com/exchange, https://mtradeasia.com/careers, https://mtradeasia.com/contact and https://mtradeasia.com/msb use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://mtradeasia.com/main/valyou has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://mtradeasia.com/newsroom and https://mtradeasia.com/msb 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 18 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://cdn.page-source.com/resizeimage.ashx?ig=mtradeasia.com&sz=145407.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 258 words of copy
The homepage carries about 258 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “Learn More”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Cloudflare Web Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
23 other companies contacted
Loading the homepage contacts 23 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 mtradeasia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
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 mtradeasia.com, including 16 speed issues, 5 SEO issues and 3 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.