Website review, no card needed
tcacoustic.com.sg website review
Visit site (opens in a new tab)Reviewed 5 November 202660 issues · 109 checks
This review found 60 issues worth fixing on tcacoustic.com.sg, 27 of them high impact, across 109 checks. The most urgent: improve image delivery. 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
74C- #86,774 of 124,235 reviewed websitesbeats 26%
- #54,526 of 69,824 online storesbeats 18%
- #51,217 of 63,496 Shopify storesbeats 16%
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.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 120 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 109 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 112 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Improve image delivery
2.4 s · 1.7 MB20 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.8 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Google Tag Manager and posthog.com and others), adding 2.6 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
330 ms · 775 KiBAbout 775 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.
Use efficient cache lifetimes
641 KiB28 files are served with short cache lifetimes, so returning visitors download them again (641 KiB).
Reduce unused CSS
450 ms · 86 KiBAbout 86 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.
Hotjar adds 434 ms
434 msHotjar costs a phone 434 ms of main-thread work and 260 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.
Google Tag Manager adds 301 ms
301 msGoogle Tag Manager costs a phone 301 ms of main-thread work and 324 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.
posthog.com adds 254 ms
254 msposthog.com costs a phone 254 ms of main-thread work and 184 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.
Shopify adds 91 ms
91 msShopify costs a phone 91 ms of main-thread work and 1.3 MB 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.
1,590 HTML elements
The page has 1,590 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
LiveChat adds 66 ms
66 msLiveChat costs a phone 66 ms of main-thread work and 367 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Minify CSS
30 ms · 12 KiB12 KiB could be saved by minifying CSS.
Duplicated JavaScript
15 KiB15 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image 1”.
Time to Interactive: 33.8 s
33.8 sThe page becomes fully interactive after 33.8 s. Good is under 3.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 764 ms
764 msScripts block taps and scrolling for 764 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 114 ms
114 msReal visitors wait 114 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 375 ms
375 msReal visitors wait 375 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 303 requests
7.3 MBYour homepage downloads 7.3 MB in 303 requests on a phone: images 4.1 MB (85), scripts 2.2 MB (95) and other files 663 KiB (103). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Roundhouse_and_Gambit_BAU_TC_-_Homepage_Top_Banner_Desktop.j weighs 805 KiB. On a phone connection a single image that size takes seconds.
8 images far larger than shown
1.2 MB8 images are downloaded at several times the size a phone draws them, for example photo_2026-05-15_12.00.49.jpg at 2,560 px wide, shown at 308 px. Resized copies would save about 1.2 MB.
17 images below the first screen load straight away
17 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
Lutron---Mobile.jpg 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).
2 images in older formats
2 images (780 KiB) 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.
About 2.1 g of CO₂ per visit
2.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.06 g of CO₂e: 246.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (4 elements)
Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (4 elements)
ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
12 elements hidden from screen readers can still receive keyboard focus.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (5 elements)
ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
No main landmark
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)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 18 failed. 4 mores 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.
Title is short (23 characters)
Your title is only 23 characters: “TC Acoustic | Singapore”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 3 problems
Structured data found (ElectronicsStore and Organization) but with 3 problems, for example “Organization: logo is not an absolute URL ("//sg.tcacoustic.asia/cdn/shopifycloud/storefront/assets…”.
93 internal links, 5 external
The homepage links to 93 pages on tcacoustic.com.sg and 5 external pages.
5 checks passed
Meta description: 104 characters
Your meta description is 104 characters: “Everyone's Favourite Company. Official distributor of Sonos, Marshall and Bowers & Wilkins in Singapore.”.
Canonical URL set
The canonical URL is https://sg.tcacoustic.asia/.
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://sg.tcacoustic.asia/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (515 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sg.tcacoustic.asia/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://sg.tcacoustic.asia/collections/sale and https://sg.tcacoustic.asia/collections/clearance, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://sg.tcacoustic.asia/pages/sonos-flagship-store and https://sg.tcacoustic.asia/collections/sonos all use the title “Official Sonos Flagship Store Singapore | TC Acoustic Singapore”. Search engines can't tell which page to show for a search, so each competes with the others.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sg.tcacoustic.asia/collections/sonos/products/sonos-arc-ultra, whose canonical is https://sg.tcacoustic.asia/products/sonos-arc-ultra. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages without an H1
https://sg.tcacoustic.asia/collections/new-arrivals, https://sg.tcacoustic.asia/pages/sonos-flagship-store, https://sg.tcacoustic.asia/collections/sonos, https://sg.tcacoustic.asia/collections/marshall, https://sg.tcacoustic.asia/collections/bowers-wilkins and https://sg.tcacoustic.asia/collections/bestsellers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://sg.tcacoustic.asia/collections/marshall, https://sg.tcacoustic.asia/pages/lutron and https://sg.tcacoustic.asia/collections/bestsellers took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 13 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://sg.tcacoustic.asia/.
17 small tap targets
17 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 575 words of copy
The homepage carries about 575 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Group Buy”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating, 2 trust badges and “5,000+ reviews”.
Analytics in place
Analytics detected: Google Tag Manager, Hotjar and PostHog.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
29 cookies set on arrival
29Opening the homepage sets 29 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.
52 other companies contacted
Loading the homepage contacts 52 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 tcacoustic.com.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Oracle Cloud
Company
- Headquarters
- Singapore
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 60 issues on tcacoustic.com.sg, including 20 speed issues, 3 SEO issues and 4 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.