ttracing.sg website review

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

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

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

30 images could be 1.9 MB 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.

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

About 387 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Shopify, jQuery CDN and Google Tag Manager and others), adding 1,002 KiB and 456 ms of main-thread time.

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

Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need.

6 KiB could be saved by minifying CSS.

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.

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.

For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.

Your largest element takes 73.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Eight Friends, One Comfy Seat”.

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

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

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 128 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 27.9 MB in 1,312 requests on a phone: images 26.5 MB (978), scripts 1,001 KiB (90) and HTML 194 KiB (2). Under 2 MB keeps phones on slow connections fast.

40 images are downloaded at several times the size a phone draws them, for example spidermanfp-main.png at 1,500 px wide, shown at 106 px. Resized copies would save about 5.0 MB.

4 images further down the page (749 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

3 images have no alt text, which hurts accessibility and image search.

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

66 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: 27 elements on the page fail this check, rated minor by axe-core.

6 elements hidden from screen readers can still receive keyboard focus.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

79 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your title is 68 characters, so Google will cut it off around 60: “Best Gaming Chair, Standing Desk & Office Chair | TTRacing Singapore”.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 656 pages on ttracing.sg and 16 external pages.

https://ttracing.sg/pages/bundle-sale-13, https://ttracing.sg/pages/bundle-sale-14, https://ttracing.sg/pages/bundle-sale-15 and https://ttracing.sg/pages/bundle-sale-9 have no meta description, so Google writes the search snippet from whatever text it finds.

https://ttracing.sg/pages/bt21-ora-sofa, https://ttracing.sg/pages/bundle-deals, https://ttracing.sg/pages/bundle-sale-2, https://ttracing.sg/pages/bundle-sale-10, https://ttracing.sg/pages/bundle-sale-3 and https://ttracing.sg/pages/bundle-sale-13 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ttracing.sg/pages/bundle-sale-2, https://ttracing.sg/pages/bundle-sale-10, https://ttracing.sg/pages/bundle-sale, https://ttracing.sg/pages/bundle-sale-5, https://ttracing.sg/pages/bundle-sale-12 and https://ttracing.sg/collections/all-products and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 183 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”.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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,799 words of visible text.

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

Before a visitor clicks anything, the page loads Google Tag Manager, LinkedIn Insight and 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.

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