Tools & Wizards About Us
teaseed.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

teaseed.com.tw

Page Load Speed

9.5 sec in total

First Response

3.6 sec

Resources Loaded

5.8 sec

Page Rendered

141 ms

teaseed.com.tw screenshot

About Website

Visit teaseed.com.tw now to see the best up-to-date Teaseed content for Taiwan and also check out these interesting facts you probably never knew about teaseed.com.tw

來自台灣在地的茶籽堂，追求天然與人文間的和諧，冀望自然純粹的「茶籽」完整陪伴人們的生活。系列商品以「苦茶油」的滋潤呵護與「茶苷」的溫和清潔做區分，搭配天然植物萃取液與純精油，讓身心在每日呼吸吞吐間，都能由內而外感受台灣孕育出的美好。, QDM 網路開店平台

Visit teaseed.com.tw

Key Findings

We analyzed Teaseed.com.tw page load time and found that the first response time was 3.6 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

teaseed.com.tw performance score

0

Network Requests Diagram

teaseed.com.tw

3607 ms

jquery.min.js

8 ms

jquery-migrate-1.3.0.min.js

29 ms

js1.js

236 ms

js2.js

274 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Teaseed.com.tw, 22% (13 requests) were made to Cdn.qdm.com.tw and 9% (5 requests) were made to Orientea.qdm.com.tw. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Teaseed.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.3 kB (6%)

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Teaseed.com.tw main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 28.7 kB

  • Original 39.0 kB
  • After minification 38.6 kB
  • After compression 10.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.7 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 15.1 kB

  • Original 1.3 MB
  • After minification 1.3 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Teaseed images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 88 B

  • Original 22.6 kB
  • After minification 22.6 kB
  • After compression 22.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-78%

Potential reduce by 39.4 kB

  • Original 50.7 kB
  • After minification 49.9 kB
  • After compression 11.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Teaseed.com.tw needs all CSS files to be minified and compressed as it can save up to 39.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (59%)

Requests Now

49

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teaseed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

teaseed.com.tw

teaseed.com.tw

3607 ms

jquery.min.js

jquery.min.js

8 ms

jquery-migrate-1.3.0.min.js

jquery-migrate-1.3.0.min.js

29 ms

js1.js

js1.js

236 ms

js2.js

js2.js

274 ms

conversion_async.js

conversion_async.js

28 ms

jquery.lazy.min.js

jquery.lazy.min.js

25 ms

normalize.min.css

normalize.min.css

3 ms

css1.css

css1.css

16 ms

skin-3.css

skin-3.css

5 ms

css

css

47 ms

icon

icon

46 ms

font-awesome.min.css

font-awesome.min.css

11 ms

font-awesome.min.css

font-awesome.min.css

7 ms

animate.min.css

animate.min.css

42 ms

ihover.min.css

ihover.min.css

37 ms

jquery.smartbanner.css

jquery.smartbanner.css

44 ms

index.php

index.php

543 ms

slideshow.css

slideshow.css

42 ms

fbevents.js

fbevents.js

54 ms

analytics.js

analytics.js

16 ms

a17cde5ec8e92142c983c54bd44f9510.png.pagespeed.ce.hhjz_9Otr7.png

a17cde5ec8e92142c983c54bd44f9510.png.pagespeed.ce.hhjz_9Otr7.png

775 ms

19118ccd18c481a54b5f61744fedb640.png.pagespeed.ce.TLMsW0AbXr.png

19118ccd18c481a54b5f61744fedb640.png.pagespeed.ce.TLMsW0AbXr.png

604 ms

ff414f9c4e461d5d044c1c14800cf11b.jpg

ff414f9c4e461d5d044c1c14800cf11b.jpg

519 ms

0a9f61d3757a1d5eb6171612ac50dfcc.png

0a9f61d3757a1d5eb6171612ac50dfcc.png

518 ms

438ec6368a46b7f37aff100c883ec5a5.png

438ec6368a46b7f37aff100c883ec5a5.png

595 ms

39386517f1c93d061086559e548fc380.png

39386517f1c93d061086559e548fc380.png

515 ms

b88bb0810c49c4540b9555696cf8e125.png

b88bb0810c49c4540b9555696cf8e125.png

590 ms

83f80eb0047023326c7319aa267f8615.png

83f80eb0047023326c7319aa267f8615.png

636 ms

c57e670717fb212b01b68b08e0b52395.jpg

c57e670717fb212b01b68b08e0b52395.jpg

341 ms

126297ac50b4831eb682d8828444966b.jpg

126297ac50b4831eb682d8828444966b.jpg

381 ms

c9e31ac4a7ded04fc73ff30a67ced1d5.jpg

c9e31ac4a7ded04fc73ff30a67ced1d5.jpg

505 ms

6bfe3beace9eccd127b1ee5228a07b5f.jpg

6bfe3beace9eccd127b1ee5228a07b5f.jpg

431 ms

ed378c1137c38260045209fd5ee79ecc-max-w-1170.jpg.pagespeed.ce.q74khMcvrW.jpg

ed378c1137c38260045209fd5ee79ecc-max-w-1170.jpg.pagespeed.ce.q74khMcvrW.jpg

1291 ms

33b4c3ab0cb442d158b2ceac3ce80650-max-w-1170.jpg.pagespeed.ce.4cj1l9Hhp6.jpg

33b4c3ab0cb442d158b2ceac3ce80650-max-w-1170.jpg.pagespeed.ce.4cj1l9Hhp6.jpg

1270 ms

72d4bc99f1e313884cb8c336c2189983-max-w-1170.jpg.pagespeed.ce.3rp2QXxdX5.jpg

72d4bc99f1e313884cb8c336c2189983-max-w-1170.jpg.pagespeed.ce.3rp2QXxdX5.jpg

787 ms

88 ms

gtm.js

gtm.js

89 ms

linkid.js

linkid.js

14 ms

ecommerce.js

ecommerce.js

17 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

47 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

47 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

46 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

45 ms

sdk.js

sdk.js

64 ms

collect

collect

12 ms

collect

collect

75 ms

49 ms

collect

collect

22 ms

61 ms

9 ms

xd_arbiter.php

xd_arbiter.php

87 ms

xd_arbiter.php

xd_arbiter.php

143 ms

47 ms

ga-audiences

ga-audiences

47 ms

ga-audiences

ga-audiences

41 ms

custom.min.js

custom.min.js

17 ms

ping

ping

16 ms

SEO Factors

teaseed.com.tw SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teaseed.com.tw can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Teaseed.com.tw main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

teaseed.com.tw

Open Graph data is detected on the main page of Teaseed. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: