Tools & Wizards About Us
fashioner.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fashioner.com.tw

采億科技 / 采盟數位媒體

Page Load Speed

8.8 sec in total

First Response

2.1 sec

Resources Loaded

6 sec

Page Rendered

636 ms

fashioner.com.tw screenshot

About Website

Click here to check amazing Fashioner content for Taiwan. Otherwise, check out these important facts you probably never knew about fashioner.com.tw

15年電子商務,社群行銷經歷深耕中小企業與1000大品牌服務,從品牌整合提案到行銷策略與執行內容,擁有的是原創製作,無論從創意發想.網頁程式.內容製作.廣告投放,成為許多網路品牌幕後的推手。

Visit fashioner.com.tw

Key Findings

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

Performance Metrics

fashioner.com.tw performance score

0

Network Requests Diagram

fashioner.com.tw

2128 ms

bootstrap.min.css

1489 ms

indexVer2.css

1344 ms

jquery.min.js

73 ms

bootstrap.min.js

1211 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 44% of them (34 requests) were addressed to the original Fashioner.com.tw, 40% (31 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Fashioner.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.6 kB (35%)

Content Size

704.5 kB

After Optimization

456.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 9.1 kB

  • Original 12.8 kB
  • After minification 11.0 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.1 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 19.3 kB

  • Original 376.9 kB
  • After minification 357.6 kB

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. Fashioner images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 65.1 kB

  • Original 131.6 kB
  • After minification 129.2 kB
  • After compression 66.4 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 65.1 kB or 49% of the original size.

CSS Optimization

-84%

Potential reduce by 154.1 kB

  • Original 183.2 kB
  • After minification 168.4 kB
  • After compression 29.2 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. Fashioner.com.tw needs all CSS files to be minified and compressed as it can save up to 154.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (52%)

Requests Now

75

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fashioner.com.tw

fashioner.com.tw

2128 ms

bootstrap.min.css

bootstrap.min.css

1489 ms

indexVer2.css

indexVer2.css

1344 ms

jquery.min.js

jquery.min.js

73 ms

bootstrap.min.js

bootstrap.min.js

1211 ms

mainScript.js

mainScript.js

638 ms

analytics.js

analytics.js

116 ms

navMainIcon.png

navMainIcon.png

508 ms

navRigLine.jpg

navRigLine.jpg

527 ms

lang01.png

lang01.png

498 ms

gear.png

gear.png

524 ms

headerIcon.png

headerIcon.png

534 ms

galleryNetGray.png

galleryNetGray.png

500 ms

ph1.jpg

ph1.jpg

1623 ms

playbutton.png

playbutton.png

921 ms

serviceIcon.png

serviceIcon.png

718 ms

stitleUnder3.png

stitleUnder3.png

730 ms

sai01.png

sai01.png

726 ms

whiteMiro.png

whiteMiro.png

757 ms

sai02.png

sai02.png

908 ms

sai03.png

sai03.png

937 ms

sai04.png

sai04.png

955 ms

advisorIcon.png

advisorIcon.png

1000 ms

ipt1.png

ipt1.png

1110 ms

inputLeft.jpg

inputLeft.jpg

1116 ms

ipt2.png

ipt2.png

1145 ms

ipt3.png

ipt3.png

1186 ms

ipt4.png

ipt4.png

1229 ms

ipt5.png

ipt5.png

1319 ms

ipt6.png

ipt6.png

1313 ms

advisorLady.png

advisorLady.png

1360 ms

btnIcon.png

btnIcon.png

1404 ms

footPoint.png

footPoint.png

1463 ms

footIcon1.png

footIcon1.png

1530 ms

footIcon2.png

footIcon2.png

1524 ms

sdk.js

sdk.js

31 ms

collect

collect

54 ms

ph2.jpg

ph2.jpg

2120 ms

164 ms

collect

collect

89 ms

xd_arbiter.php

xd_arbiter.php

51 ms

xd_arbiter.php

xd_arbiter.php

72 ms

204 ms

xd_arbiter.php

xd_arbiter.php

8 ms

video.php

video.php

129 ms

4CaSuI1pXxN.css

4CaSuI1pXxN.css

48 ms

25TyHxL4s5_.css

25TyHxL4s5_.css

46 ms

iUOMonzWz-d.css

iUOMonzWz-d.css

81 ms

hHM4NBz3Egj.css

hHM4NBz3Egj.css

52 ms

RTMA02q34Pb.css

RTMA02q34Pb.css

88 ms

HD718DCFoiY.css

HD718DCFoiY.css

77 ms

JBxjOp6Mcr9.css

JBxjOp6Mcr9.css

78 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

92 ms

b94UUzHjapV.js

b94UUzHjapV.js

127 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

119 ms

OCkothPJhqg.js

OCkothPJhqg.js

132 ms

6kb4qPGfoPa.js

6kb4qPGfoPa.js

118 ms

hQyBJD7FRta.js

hQyBJD7FRta.js

115 ms

D6JJJzT-tB6.js

D6JJJzT-tB6.js

115 ms

ezSeJz80WmZ.js

ezSeJz80WmZ.js

167 ms

tIFXiEZJgab.js

tIFXiEZJgab.js

161 ms

ThxFh2GztJe.js

ThxFh2GztJe.js

160 ms

B9x7unvN8Hn.js

B9x7unvN8Hn.js

163 ms

b_6HNn_J2BZ.js

b_6HNn_J2BZ.js

159 ms

_UYztdBNTjs.js

_UYztdBNTjs.js

159 ms

VpVLc1dkyZp.js

VpVLc1dkyZp.js

163 ms

Jl64yqKpITf.js

Jl64yqKpITf.js

162 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

161 ms

TTCre3391I0.js

TTCre3391I0.js

161 ms

12323364_506550566173327_1509597251_n.jpg

12323364_506550566173327_1509597251_n.jpg

138 ms

pzwyo2GOJzP.svg

pzwyo2GOJzP.svg

28 ms

pjFzEJk5jm9.png

pjFzEJk5jm9.png

21 ms

l5aPruN9xMM.png

l5aPruN9xMM.png

26 ms

Fl1c2TVhCj-.png

Fl1c2TVhCj-.png

21 ms

sOQnlBB68lt.png

sOQnlBB68lt.png

22 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

4 ms

f6T91Deal_q.js

f6T91Deal_q.js

6 ms

SEO Factors

fashioner.com.tw SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fashioner.com.tw

Open Graph description is not detected on the main page of Fashioner. 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: