Website review, no card needed
salomon.com.tw website review
Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 77 checks
This review found 32 issues worth fixing on salomon.com.tw, 5 of them high impact, across 77 checks. The most urgent: page weight: 4.1 MB in 237 requests. 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
88B- #4,950 of 101,636 reviewed websitesbeats 93%
- #2,680 of 56,291 online storesbeats 93%
- #2,599 of 51,174 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 739 ms |
| May 23, 2026 | 739 ms |
| May 30, 2026 | 757 ms |
| Jun 6, 2026 | 752 ms |
| Jun 13, 2026 | 767 ms |
| Jun 20, 2026 | 788 ms |
| Jun 27, 2026 | 813 ms |
| Jul 4, 2026 | 834 ms |
| Jul 11, 2026 | 841 ms |
| Jul 18, 2026 | 845 ms |
| Jul 25, 2026 | 825 ms |
| Aug 1, 2026 | 838 ms |
| Aug 8, 2026 | 850 ms |
| Aug 15, 2026 | 865 ms |
| Aug 22, 2026 | 873 ms |
| Aug 29, 2026 | 878 ms |
| Sep 5, 2026 | 879 ms |
| Sep 12, 2026 | 874 ms |
| Sep 19, 2026 | 882 ms |
| Sep 26, 2026 | 879 ms |
| Oct 3, 2026 | 861 ms |
| Oct 10, 2026 | 845 ms |
| Oct 17, 2026 | 821 ms |
| Oct 24, 2026 | 796 ms |
| Oct 31, 2026 | 786 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 90 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 93 ms |
| Jun 27, 2026 | 92 ms |
| Jul 4, 2026 | 89 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 90 ms |
| Sep 5, 2026 | 90 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 115 ms |
| Oct 31, 2026 | 113 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
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Shopify, Clarity and bogos.io and others), adding 1.3 MB and 814 ms of main-thread time.
Improve image delivery
500 ms · 379 KiB16 images could be 379 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Shopify adds 647 ms
647 msShopify costs a phone 647 ms of main-thread work and 954 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.
Render-blocking requests
650 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Reduce unused JavaScript
556 KiBAbout 556 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
265 KiB13 files are served with short cache lifetimes, so returning visitors download them again (265 KiB).
2,247 HTML elements
The page has 2,247 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 46 KiBAbout 46 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.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.2 s
14.2 sThe page becomes fully interactive after 14.2 s. Good is under 3.8 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 90 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 341 ms
341 msScripts block taps and scrolling for 341 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.8 s 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 555 ms
555 msReal visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 237 requests
4.1 MBYour homepage downloads 4.1 MB in 237 requests on a phone: images 1.9 MB (53), scripts 1.2 MB (64) and other files 820 KiB (100). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 137.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 149 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Salomon|台灣直營官方旗艦店”. Between 30 and 65 characters leaves room to say what you do and for whom.
260 internal links, 3 external
The homepage links to 260 pages on salomon.com.tw and 3 external pages.
7 checks passed
Meta description: 87 characters
Your meta description is 87 characters: “戶外科技品牌Salomon,專精越野跑鞋、登山鞋、XT-6與Gorpcore服飾配件。憑藉戶外性能與潮流設計成為專業跑與山系穿搭首選,無論攀登巔峰或穿梭城市都能享受專業性能。”.
One H1 headline
Your main headline reads: “Salomon Taiwan”.
Canonical URL set
The canonical URL is https://salomon.com.tw/.
Structured data in place
Structured data found: BreadcrumbList, 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://salomon.com.tw/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (375 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://salomon.com.tw/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://salomon.com.tw/pages/%E9%A0%98%E5%8F%96%E6%8A%98%E5%8D%B7, https://salomon.com.tw/collections/new-arrivals-shoes, https://salomon.com.tw/collections/new-arrivals-bags, https://salomon.com.tw/pages/salomon-campaign, https://salomon.com.tw/collections/%E4%BA%BA%E6%B0%A3%E7%86%B1%E9%8A%B7 and https://salomon.com.tw/collections/11%E6%9C%88%E9%99%90%E5%AE%9A-%E7%B2%BE%E9%81%B8%E5%95%86%E5%93%8165-7%E6%8A%98 have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://salomon.com.tw/collections/november-mix-9, https://salomon.com.tw/collections/november-mix-6000-9 and https://salomon.com.tw/collections/november-gift use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://salomon.com.tw/collections/%E9%85%8D%E4%BB%B6-%E5%BE%8C%E8%83%8C%E5%8C%85, whose canonical is https://salomon.com.tw/collections/%e9%85%8d%e4%bb%b6-%e5%be%8c%e8%83%8c%e5%8c%85. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://salomon.com.tw/pages/%E9%A0%98%E5%8F%96%E6%8A%98%E5%8D%B7, https://salomon.com.tw/pages/sale, https://salomon.com.tw/pages/salomon-campaign, https://salomon.com.tw/pages/salomon-the-broken-arm and https://salomon.com.tw/pages/salomon-feid-acs-nexxt have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 114 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
31 small tap targets
31 of 71 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'openOnCustomerLogin')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 186 words
The homepage has only about 186 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
7 calls to action
The homepage has 7 calls to action, for example “SHOP NOW”, “XT-icons 潮流時尚 ✕ 山系機能 SHOP NOW” and “XT-Winter Story 全新系列 ✕ 官網獨家 SHOP NOW”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
24 other companies contacted
Loading the homepage contacts 24 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 salomon.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Seowill Ai Seo · Judge Me Reviews · Microsoft Clarity · Forms · Ako Retargeting · Ecomsend · Freegifts · akocommerce.com · akohub.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
Hiring
- Hiring
- 70 open roles
- Teams
- D2C - Retail Stores (17), IT (7), Finance (2), Brand Marketing (1)
- Job board
- smartrecruiters
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on salomon.com.tw, including 14 speed issues, 1 SEO issue and 3 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.