Website review, no card needed
naturecan.tw website review
Visit site (opens in a new tab)Reviewed 10 November 202641 issues · 88 checks
This review found 41 issues worth fixing on naturecan.tw, 17 of them high impact, across 88 checks. The most urgent: main-thread work: 23.5 s. 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
72C- #74,163 of 95,268 reviewed websitesbeats 19%
- #43,655 of 51,322 online storesbeats 12%
- #40,499 of 46,434 Shopify storesbeats 10%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 170 ms |
| May 30, 2026 | 172 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 151 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 165 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 188 ms |
| Aug 8, 2026 | 183 ms |
| Aug 15, 2026 | 197 ms |
| Aug 22, 2026 | 202 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 130 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 160 ms |
| Oct 24, 2026 | 159 ms |
| Oct 31, 2026 | 148 ms |
| Nov 7, 2026 | 155 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
2.0 s
4.0 s
6.0 s
8.1 s
10.1 s
12.1 s
14.1 s
16.1 s
Speed
Main-thread work: 23.5 s
A phone's processor spends 23.5 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.8 s
1.8 sShopify costs a phone 1.8 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.3 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
typeform.com adds 1.1 s
1.1 stypeform.com costs a phone 1.1 s of main-thread work and 699 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,237 HTML elements
The page has 8,237 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, typeform.com and Klaviyo and others), adding 2.6 MB and 4.1 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 695 ms. During a long task the page ignores taps.
Improve image delivery
582 KiB34 images could be 582 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Klaviyo adds 515 ms
515 msKlaviyo costs a phone 515 ms of main-thread work and 309 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.
Use efficient cache lifetimes
150 ms · 364 KiB26 files are served with short cache lifetimes, so returning visitors download them again (364 KiB).
Reviews.io adds 445 ms
445 msReviews.io costs a phone 445 ms of main-thread work and 356 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.
Reduce unused JavaScript
476 KiBAbout 476 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify JavaScript
13 KiB13 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: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 31.5 s
31.5 sThe page becomes fully interactive after 31.5 s. Good is under 3.8 s.
Total Blocking Time: 3.2 s
3.2 sScripts block taps and scrolling for 3.2 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Main tw 99購物節-Mobile.png__PID:9a4fa44b-a90d-4c16-82ea-37eab…”.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 706 ms
706 msReal visitors wait 706 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 170 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 7.7 MB in 645 requests
7.7 MBYour homepage downloads 7.7 MB in 645 requests on a phone: images 4.1 MB (225), scripts 2.0 MB (239) and other files 869 KiB (142). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Main_TW-11.11_SALE-Mobile.png 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).
9 images in older formats
9 images (303 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.2 g of CO₂ per visit
2.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.17 g of CO₂e: 260.2 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
Scrollable region must have keyboard access (41 elements)
Scrollable region must have keyboard access: 41 elements on the page fail this check, rated serious by axe-core.
Elements must only use permitted ARIA attributes (34 elements)
Elements must only use permitted ARIA attributes: 34 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 284 images in the HTML carry an alt attribute.
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (61 characters)
Your meta description is only 61 characters: “Naturecan是來自英國的專業營養保健品牌,提供元性的商品, 從營養保健、美容保養到健身補給,多款高品質商品供您選擇。”. 70 to 160 characters is enough to sell the click.
2 H1 headlines
There are 2 <h1> headlines (“Naturecan TW” and “我適合什麼產品?”). One clear main headline is easier for people and search engines.
165 internal links, 2 external
The homepage links to 165 pages on naturecan.tw and 2 external pages.
6 checks passed
Title: 53 characters
Your title is a healthy 53 characters: “Naturecan 台灣官方網站| 高品質營養保健品|NMN & NAD購買 – Naturecan TW”.
Canonical URL set
The canonical URL is https://www.naturecan.tw/.
Structured data in place
Structured data found: BreadcrumbList and Organization.
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://www.naturecan.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 (640 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.naturecan.tw/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 linked pages are broken
Your homepage links to https://www.naturecan.tw/products/anti-ageing-longevity-bundle, https://www.naturecan.tw/products/glp-1-bundle and https://www.naturecan.tw/products/gut-health-bundle, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a meta description
https://www.naturecan.tw/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://www.naturecan.tw/collections/all, https://www.naturecan.tw/collections/naturecan-products, https://www.naturecan.tw/collections, https://www.naturecan.tw/products/silica-supplement-bloosil, https://www.naturecan.tw/products/longevity-powder-mix and https://www.naturecan.tw/products/glp-1-supplement and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.naturecan.tw/products/zinc-supplement, https://www.naturecan.tw/products/urolithin-a, https://www.naturecan.tw/products/apigenin-supplement and https://www.naturecan.tw/products/magnesium-gummies took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 12 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
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 'getElementsByTagName')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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 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 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 370 words of copy
The homepage carries about 370 words of visible text.
3 checks passed
17 short forms
17 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 2 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: TikTok Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 of them by other companies (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.
30 other companies contacted
Loading the homepage contacts 30 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 naturecan.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Naturecan Brand Blocks · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms
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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on naturecan.tw, including 19 speed issues, 2 SEO issues 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.