Website review, no card needed
sangu.com.tw website review
Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 78 checks
This review found 36 issues worth fixing on sangu.com.tw, 13 of them high impact, across 78 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
82B- #34,112 of 121,660 reviewed websitesbeats 66%
- #22,697 of 68,831 online storesbeats 61%
- #21,935 of 62,720 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 134 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 148 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 131 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 137 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
Improve image delivery
2.6 s · 3.8 MB28 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
1.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 365 KiBAbout 365 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and getbutton.io and others), adding 832 KiB and 558 ms of main-thread time.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 207 ms
207 msShopify costs a phone 207 ms of main-thread work and 340 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.
1,610 HTML elements
The page has 1,610 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 233 KiB9 files are served with short cache lifetimes, so returning visitors download them again (233 KiB).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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.
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: 13 ms
13 msYour server sent the HTML in 13 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.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carousel Image”.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
Real-user TTFB: 816 ms
816 msReal visitors wait 816 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 134 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
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: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.1 MB in 265 requests
8.1 MBYour homepage downloads 8.1 MB in 265 requests on a phone: images 5.1 MB (48), fonts 1.1 MB (2) and scripts 889 KiB (66). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (1.3 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.
An image on the first screen is lazy-loaded
02_c17fa2c6-6a9b-475e-b093-1d189c7ced9d.gif 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 2.3 g of CO₂ per visit
2.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.29 g of CO₂e: 275.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (12 elements)
Links must have discernible text: 12 elements on the page fail this check, rated serious by axe-core.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 106 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “SANGU 三谷家電 - 讓生活更有品味,讓家更有溫度。”. Between 30 and 65 characters leaves room to say what you do and for whom.
One H1 headline
Your <h1> is empty.
154 internal links, 16 external
The homepage links to 154 pages on sangu.com.tw and 16 external pages.
6 checks passed
Meta description: 70 characters
Your meta description is 70 characters: “SANGU 三谷家電專注於質感家電、設計美學,嚴選日系精品家電、行動電源,20年專業團隊把關,為您打造品味生活、溫暖居家。線上購物輕鬆選購。”.
Canonical URL set
The canonical URL is https://sangu.com.tw/.
Structured data in place
Structured data found: Organization and WebSite.
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://sangu.com.tw/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (294 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sangu.com.tw/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://sangu.com.tw/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://sangu.com.tw/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
9 pages without a meta description
https://sangu.com.tw/customer_authentication/redirect, https://sangu.com.tw/collections/crowdfunder, https://sangu.com.tw/collections/%E6%9C%AC%E5%91%A8%E7%86%B1%E9%8A%B7%E6%8E%92%E8%A1%8C, https://sangu.com.tw/collections/%E4%B8%80%E8%88%AC%E8%B2%A9%E5%94%AE, https://sangu.com.tw/collections/%E9%A4%90%E5%BB%9A%E5%AE%B6%E9%9B%BB and https://sangu.com.tw/collections/%E7%94%9F%E6%B4%BB%E5%AE%B6%E9%9B%BB and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://sangu.com.tw/collections/%E6%9C%AC%E5%91%A8%E7%86%B1%E9%8A%B7%E6%8E%92%E8%A1%8C, whose canonical is https://sangu.com.tw/collections/%e6%9c%ac%e5%91%a8%e7%86%b1%e9%8a%b7%e6%8e%92%e8%a1%8c. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://sangu.com.tw/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://sangu.com.tw/collections/crowdfunder, https://sangu.com.tw/collections/%E6%9C%AC%E5%91%A8%E7%86%B1%E9%8A%B7%E6%8E%92%E8%A1%8C, https://sangu.com.tw/pages/about, https://sangu.com.tw/pages/contact, https://sangu.com.tw/blogs/kolin-plus-%E9%8B%BC%E9%8B%BC%E5%A5%BD%E5%BF%AB%E9%8D%8B-%E7%A7%81%E5%BB%9A%E9%A3%9F%E8%AD%9C%E6%8E%A8%E8%96%A6/kolin-plus-sus304-pressure-cooker-recipe and https://sangu.com.tw/blogs/polar-%E5%85%A9%E7%84%99%E6%8B%8C-%E5%B1%85%E5%AE%B6%E9%A3%9F%E8%AD%9C%E6%8E%A8%E8%96%A6/polar-homemade-recipes and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading '0') https://sangu.com.tw/web-pixels/strict/app/web-pixel-735183088@4d2308b162a…”.
2 checks passed
Tap targets are thumb-sized
98 of 106 tappable elements near the top are at least 24 px.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 221 words
The homepage has only about 221 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
38 other companies contacted
Loading the homepage contacts 38 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 sangu.com.tw, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Rank King Best Sellers · Simesy Faq · Uplinkly Sticky Cart · Tagfly Tag Manager · Judge Me Reviews · Avada Seo Ai Blog · Microsoft Clarity · Mps Sales Notification · Ymq Upsell Cross Sell · Ymq Bundle Quantity Breaks · Event Promotion Bar · Facebook Pixel · cloudfront.net · hextom.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on sangu.com.tw, including 15 speed issues, 2 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.