carguru.sg website review

47 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 1.1 s faster on a phone.

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

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

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

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

Shopify costs a phone 38 ms of main-thread work and 328 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.

About 244 KiB of JavaScript is downloaded but never used on this page.

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

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

4 third-party services load with your homepage (Shopify, Google Fonts and shop.app and others), adding 398 KiB and 39 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.

2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

Your largest element takes 31.2 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 34.7 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 11.4 MB in 272 requests on a phone: images 9.5 MB (103), other files 750 KiB (73) and scripts 570 KiB (55). Under 2 MB keeps phones on slow connections fast.

14 images (2.2 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.

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

2 images are downloaded at several times the size a phone draws them, for example Used-Car-TOYOTA-SIENTA-HYBRID-1.5G-CVT-Luxury-Sedan-4-Mar-21 at 1,024 px wide, shown at 290 px. Resized copies would save about 56 KiB.

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

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

4 dropdowns have no label.

15 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: 190 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Elements marked as presentational should be consistently ignored: 16 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.

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

Your title is 67 characters, so Google will cut it off around 60: “Singapore Used Car Buy, Sell, Trade-in Used/New Cars｜CarGuru.sg 车师父”.

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 favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 286 pages on carguru.sg and 0 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.

https://www.carguru.sg/collections/all-used-cars, https://www.carguru.sg/collections/honda-used-car, https://www.carguru.sg/collections/mercedes-benz-used-car-singapore-used-car, https://www.carguru.sg/collections/bmw-new-car-singapore-new-car, https://www.carguru.sg/collections/mazda-new-car-singapore-new-car and https://www.carguru.sg/collections/hyundai-used-car-singapore-used-car and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,387 words of visible text.

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

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

Opening the homepage sets 9 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.