Tools & Wizards About Us
fancyfancy.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fancyfancy.com.tw

Fancy Made

Page Load Speed

8.9 sec in total

First Response

196 ms

Resources Loaded

7.2 sec

Page Rendered

1.6 sec

fancyfancy.com.tw screenshot

About Website

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

fancy是別緻的，是甜美夢幻的，是優質且美好的 fancy是一種想像，是一種迷戀，是種想望與愛慕 What do you fancy for? 有人說:「幸福，是無法用金錢買到的東西」 但如果一些些花費，就能讓你感受到一絲絲的幸福 那麼，無論你消費的是一件服飾或者是一個小擺飾 你不覺得，也都是一件很棒又很幸福的事嗎 所以現在，就請和我們一起

Visit fancyfancy.com.tw

Key Findings

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

Performance Metrics

fancyfancy.com.tw performance score

0

Network Requests Diagram

fancyfancy.com.tw

196 ms

www.fancyfancy.com.tw

437 ms

reset.css

138 ms

style.css

213 ms

font-awesome.css

14 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 95% of them (109 requests) were addressed to the original Fancyfancy.com.tw, 2% (2 requests) were made to Netdna.bootstrapcdn.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Fancyfancy.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 778.0 kB (11%)

Content Size

6.8 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fancyfancy.com.tw main page is 6.8 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. 55% of websites need less resources to load. Images take 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 44.4 kB

  • Original 53.1 kB
  • After minification 49.9 kB
  • After compression 8.7 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 44.4 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 533.3 kB

  • Original 6.5 MB
  • After minification 6.0 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. Fancy images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 141.4 kB

  • Original 201.2 kB
  • After minification 154.8 kB
  • After compression 59.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 141.4 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 58.9 kB

  • Original 75.0 kB
  • After minification 61.9 kB
  • After compression 16.1 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. Fancyfancy.com.tw needs all CSS files to be minified and compressed as it can save up to 58.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (33%)

Requests Now

112

After Optimization

75

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fancyfancy.com.tw

fancyfancy.com.tw

196 ms

www.fancyfancy.com.tw

www.fancyfancy.com.tw

437 ms

reset.css

reset.css

138 ms

style.css

style.css

213 ms

font-awesome.css

font-awesome.css

14 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

13 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

150 ms

jquery.mu.image.resize.js

jquery.mu.image.resize.js

150 ms

jquery.idTabs.min.js

jquery.idTabs.min.js

177 ms

stickySidebar.js

stickySidebar.js

272 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

285 ms

focus.js

focus.js

298 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

380 ms

jquery.fancybox.css

jquery.fancybox.css

317 ms

css

css

28 ms

jquery.bxslider.css

jquery.bxslider.css

345 ms

jquery.bxslider.js

jquery.bxslider.js

542 ms

stickysidebar.jquery.js

stickysidebar.jquery.js

432 ms

header.js

header.js

450 ms

jcarousellite_1.0.1.js

jcarousellite_1.0.1.js

475 ms

jquery.slimscroll.min.js

jquery.slimscroll.min.js

499 ms

responsiveslides.css

responsiveslides.css

459 ms

themes.css

themes.css

519 ms

responsiveslides.js

responsiveslides.js

542 ms

tw_cn.js

tw_cn.js

590 ms

store_logo.png

store_logo.png

132 ms

search.gif

search.gif

634 ms

search_btn.gif

search_btn.gif

635 ms

go_top.png

go_top.png

638 ms

slideR_addbtn.png

slideR_addbtn.png

639 ms

_captcha.php

_captcha.php

640 ms

again_icon.gif

again_icon.gif

642 ms

L-01_01.png

L-01_01.png

640 ms

cb_show_18.png

cb_show_18.png

643 ms

cb_show_20.png

cb_show_20.png

643 ms

cb_show_15.png

cb_show_15.png

644 ms

cb_show_1.png

cb_show_1.png

646 ms

cb_show_9.png

cb_show_9.png

646 ms

cb_show_8.png

cb_show_8.png

647 ms

cb_show_10.png

cb_show_10.png

649 ms

cb_show_11.png

cb_show_11.png

647 ms

cb_show_12.png

cb_show_12.png

649 ms

cb_show_13.png

cb_show_13.png

651 ms

cb_show_14.png

cb_show_14.png

651 ms

cb_show_21.png

cb_show_21.png

652 ms

cb_show_27.png

cb_show_27.png

652 ms

L-01_14.gif

L-01_14.gif

654 ms

L-01_15.gif

L-01_15.gif

681 ms

L-01_16.gif

L-01_16.gif

690 ms

L-01_17.gif

L-01_17.gif

713 ms

L-01_21.png

L-01_21.png

749 ms

L-01_18.gif

L-01_18.gif

739 ms

L-01_20.png

L-01_20.png

761 ms

icon_facebook.png

icon_facebook.png

843 ms

icon_mail.png

icon_mail.png

859 ms

icon_line.png

icon_line.png

869 ms

bi_93.jpg

bi_93.jpg

1448 ms

bi_77.jpg

bi_77.jpg

1445 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

14 ms

bi_92.jpg

bi_92.jpg

1647 ms

bi_72.jpg

bi_72.jpg

1649 ms

bi_73.jpg

bi_73.jpg

1556 ms

analytics.js

analytics.js

503 ms

validationEngine.jquery.css

validationEngine.jquery.css

393 ms

shopcart.php

shopcart.php

2347 ms

shopcart.php

shopcart.php

2491 ms

bi_82.jpg

bi_82.jpg

1092 ms

bi_81.jpg

bi_81.jpg

1500 ms

bi_78.jpg

bi_78.jpg

1614 ms

bi_70.jpg

bi_70.jpg

1740 ms

bi_69.jpg

bi_69.jpg

1824 ms

bi_2.jpg

bi_2.jpg

1748 ms

%E5%B0%8FICON-09_01.png

%E5%B0%8FICON-09_01.png

1510 ms

%E5%B0%8FICON-09_02.png

%E5%B0%8FICON-09_02.png

1705 ms

%E5%B0%8FICON-09_03.jpg

%E5%B0%8FICON-09_03.jpg

1653 ms

%E5%B0%8FICON-09_04.png

%E5%B0%8FICON-09_04.png

1812 ms

1BANNER-02--%E6%9C%88%E5%BA%95.gif

1BANNER-02--%E6%9C%88%E5%BA%95.gif

2637 ms

ai_2.jpg

ai_2.jpg

2110 ms

ai_3.jpg

ai_3.jpg

2157 ms

ai_4.jpg

ai_4.jpg

2162 ms

salet_20151015181456.png

salet_20151015181456.png

1978 ms

pi_3756.jpg

pi_3756.jpg

2730 ms

pi_4086.jpg

pi_4086.jpg

2400 ms

pi_4098.jpg

pi_4098.jpg

2600 ms

collect

collect

25 ms

pi_4114.jpg

pi_4114.jpg

2624 ms

pi_4125.jpg

pi_4125.jpg

3410 ms

pi_4184.jpg

pi_4184.jpg

2974 ms

pi_4192.jpg

pi_4192.jpg

2989 ms

pi_4220.jpg

pi_4220.jpg

3105 ms

pi_4218.jpg

pi_4218.jpg

3322 ms

pi_3075.jpg

pi_3075.jpg

3165 ms

salet_20151015180900.png

salet_20151015180900.png

2959 ms

pi_4553.jpg

pi_4553.jpg

3418 ms

pi_4556.jpg

pi_4556.jpg

3579 ms

pi_3798.jpg

pi_3798.jpg

3446 ms

pi_3801.jpg

pi_3801.jpg

2958 ms

pi_3807.jpg

pi_3807.jpg

3153 ms

pi_3816.jpg

pi_3816.jpg

3082 ms

pi_3823.jpg

pi_3823.jpg

3141 ms

pi_3832.jpg

pi_3832.jpg

3204 ms

pi_3861.jpg

pi_3861.jpg

3268 ms

pi_3874.jpg

pi_3874.jpg

2804 ms

pi_3948.jpg

pi_3948.jpg

3042 ms

salet_20151015180851.png

salet_20151015180851.png

2650 ms

pi_4024.jpg

pi_4024.jpg

3173 ms

pi_4034.jpg

pi_4034.jpg

3049 ms

pi_4042.jpg

pi_4042.jpg

3094 ms

pi_4059.jpg

pi_4059.jpg

3098 ms

pi_2344.jpg

pi_2344.jpg

3136 ms

pi_2389.jpg

pi_2389.jpg

3276 ms

pi_1850.jpg

pi_1850.jpg

3232 ms

ICON-S(1).jpg

ICON-S(1).jpg

3308 ms

bx_loader.gif

bx_loader.gif

2818 ms

themes.gif

themes.gif

2826 ms

SEO Factors

fancyfancy.com.tw SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fancyfancy.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Fancyfancy.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

fancyfancy.com.tw

Open Graph description is not detected on the main page of Fancy . Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: