Website review, no card needed
compasia.my website review
Visit site (opens in a new tab)Reviewed 4 November 202631 issues · 81 checks
This review found 31 issues worth fixing on compasia.my, 4 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81B- #41,744 of 125,248 reviewed websitesbeats 61%
- #27,566 of 70,140 online storesbeats 54%
- #26,553 of 63,737 Shopify storesbeats 52%
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.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 246 ms |
| May 23, 2026 | 228 ms |
| May 30, 2026 | 221 ms |
| Jun 6, 2026 | 215 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 195 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 193 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 197 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 213 ms |
| Oct 24, 2026 | 217 ms |
| Oct 31, 2026 | 216 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
Mobile performance score: 80
80/100Your mobile performance score is 80. 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 TikTok and others), adding 749 KiB and 750 ms of main-thread time.
Render-blocking requests
600 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
357 KiBAbout 357 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
329 KiB8 files are served with short cache lifetimes, so returning visitors download them again (329 KiB).
Google Tag Manager adds 259 ms
259 msGoogle Tag Manager costs a phone 259 ms of main-thread work and 189 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.
2,116 HTML elements
The page has 2,116 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.
Improve image delivery
26 KiB1 image could be 26 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
1 checks passed
Server response: 200 ms
200 msYour server sent the HTML in 200 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: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Real-user INP: 215 ms
215 msReal visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 838 ms
838 msReal visitors wait 838 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 554 ms
554 msScripts block taps and scrolling for 554 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 246 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Carousel slide”.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.1 MB in 167 requests
2.1 MBYour homepage downloads 2.1 MB in 167 requests on a phone: scripts 1.2 MB (58), images 527 KiB (78) and fonts 161 KiB (3). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image 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 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 72.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 190 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
81 internal links, 61 external
The homepage links to 81 pages on compasia.my and 61 external pages.
6 checks passed
Title: 62 characters
Your title is a healthy 62 characters: “Buy Apple & Samsung Second-Hand Devices in Malaysia | CompAsia”.
Canonical URL set
The canonical URL is https://compasia.my/.
Structured data in place
Structured data found: Organization.
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://compasia.my/sitemap.xml.
AI search readiness
No llms.txt
There is no https://compasia.my/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.
3 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (740 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://compasia.my/collections/laptop and https://compasia.my/collections/all-tablets use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://compasia.my/pages/renewngo, https://compasia.my/pages/about-us, https://compasia.my/pages/all-stores, https://compasia.my/pages/sell-your-devices and https://compasia.my/pages/financing-plan have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://compasia.my/pages/sell-your-devices took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
6 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.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
58 of 63 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 795 words of copy
The homepage carries about 795 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us on WhatsApp” and “Apply Now”.
13 calls to action
The homepage has 13 calls to action, for example “Buy Devices”, “Contact” and “Buy & Win a Car”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and “5k+ Reviews”.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
1 other company contacted
Loading the homepage contacts 1 host 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 compasia.my, 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
- E-commerce
- Shopify;Shopify Plus
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on compasia.my, including 15 speed issues, 3 SEO issues and 1 conversion gap. 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.