carguru.my website review

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

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

52 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

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

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

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

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

3 third-party services load with your homepage (Shopify, Google Fonts and placeholder.com), adding 94 KiB and 21 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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 “…”.

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

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

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

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

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

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

Your homepage downloads 9.1 MB in 315 requests on a phone: images 7.4 MB (98), other files 905 KiB (129) and fonts 320 KiB (10). Under 2 MB keeps phones on slow connections fast.

15 images (2.6 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.

11 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example Toyota-Vellfire-2.4-Turbo-Z-Premier-Twin-Sunroof-Black-MPV-2 at 1,024 px wide, shown at 290 px. Resized copies would save about 155 KiB.

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

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

4 dropdowns have no label.

11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 15 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 14 elements on the page fail this check, rated minor by axe-core.

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

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

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

Your title is 137 characters, so Google will cut it off around 60: “Malaysia Best Recond Car Importer -Toyota, Honda, Mercedes, BMW, Lexus – CarGuru - Malays…”.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 470 pages on carguru.my and 3 external pages.

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.

Your homepage links to https://www.carguru.my/pages/wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.carguru.my/collections/recond-car, https://www.carguru.my/collections/popular-recond-car, https://www.carguru.my/collections/exotic-recond-car, https://www.carguru.my/collections/super-car-recond-car and https://www.carguru.my/collections/hyper-car-recond-car have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.carguru.my/.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute') https://www.carguru.my/:7799:32”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 2,204 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.