Tools & Wizards About Us
stussy.com.tw screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

stussy.com.tw

Stüssy – Worldwide Since 1980 – Stüssy

Page Load Speed

6.8 sec in total

First Response

789 ms

Resources Loaded

5.5 sec

Page Rendered

520 ms

stussy.com.tw screenshot

About Website

Welcome to stussy.com.tw homepage info - get ready to check Stussy best content for Taiwan right away, or after learning these important things about stussy.com.tw

Stüssy - The Official Website of Stüssy. Worldwide since 1980.

Visit stussy.com.tw

Key Findings

We analyzed Stussy.com.tw page load time and found that the first response time was 789 ms and then it took 6 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

stussy.com.tw performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

stussy.com.tw

789 ms

www.stussy.com.tw

1971 ms

modernizr-2.5.3.min.js

415 ms

jquery.min.js

33 ms

jquery.flexslider-min.js

622 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 52% of them (40 requests) were addressed to the original Stussy.com.tw, 21% (16 requests) were made to D3e87q9f3bkl05.cloudfront.net and 5% (4 requests) were made to Stussy-wordpress-production.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Stussy.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.3 kB (30%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stussy.com.tw main page is 1.7 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 64.1 kB

  • Original 89.0 kB
  • After minification 87.7 kB
  • After compression 24.9 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 64.1 kB or 72% of the original size.

Image Optimization

-8%

Potential reduce by 81.8 kB

  • Original 1.0 MB
  • After minification 963.2 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. Stussy images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 326.9 kB

  • Original 517.8 kB
  • After minification 502.5 kB
  • After compression 190.9 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 326.9 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 42.6 kB

  • Original 51.7 kB
  • After minification 38.8 kB
  • After compression 9.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. Stussy.com.tw needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (46%)

Requests Now

74

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stussy. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stussy.com.tw

stussy.com.tw

789 ms

www.stussy.com.tw

www.stussy.com.tw

1971 ms

modernizr-2.5.3.min.js

modernizr-2.5.3.min.js

415 ms

jquery.min.js

jquery.min.js

33 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

622 ms

jquery.lazyload.js

jquery.lazyload.js

443 ms

jquery.tweet.js

jquery.tweet.js

442 ms

addthis_widget.js

addthis_widget.js

17 ms

geoip2.js

geoip2.js

21 ms

welcome_mat.js

welcome_mat.js

463 ms

product_effects.js

product_effects.js

693 ms

jquery.join.js

jquery.join.js

689 ms

style.css

style.css

1041 ms

flexslider.css

flexslider.css

691 ms

jquery.tweet.css

jquery.tweet.css

744 ms

css

css

26 ms

styles.css

styles.css

826 ms

ehu.css

ehu.css

827 ms

plugins.js

plugins.js

1052 ms

main.js

main.js

946 ms

jquery.form.min.js

jquery.form.min.js

958 ms

scripts.js

scripts.js

837 ms

ehu.js

ehu.js

839 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

1383 ms

nav.js

nav.js

1044 ms

widgets.js

widgets.js

70 ms

StussyRootz-Banner.jpg

StussyRootz-Banner.jpg

89 ms

131491_BLAC_1.jpg

131491_BLAC_1.jpg

968 ms

tw.gif

tw.gif

551 ms

usa.gif

usa.gif

554 ms

euro.gif

euro.gif

554 ms

MadeInCA_Banner.jpg

MadeInCA_Banner.jpg

58 ms

bear-promo.jpeg

bear-promo.jpeg

46 ms

PromoBox_Hats.jpg

PromoBox_Hats.jpg

99 ms

132727_BLAC_1.jpg

132727_BLAC_1.jpg

1202 ms

132726_BLAC_1.jpg

132726_BLAC_1.jpg

958 ms

132720_KHAK_1.jpg

132720_KHAK_1.jpg

1541 ms

132744_BLAC_1.jpg

132744_BLAC_1.jpg

1182 ms

132743_BLAC_1.jpg

132743_BLAC_1.jpg

1218 ms

132739_BLAC_1.jpg

132739_BLAC_1.jpg

1406 ms

132742_BLAC_1.jpg

132742_BLAC_1.jpg

1187 ms

132737_BLAC_1.jpg

132737_BLAC_1.jpg

1629 ms

132747_CHAR_1.jpg

132747_CHAR_1.jpg

1637 ms

132729_BLAC_1.jpg

132729_BLAC_1.jpg

1547 ms

131512_BLAC_1.jpg

131512_BLAC_1.jpg

1456 ms

131498_BLAC_1.jpg

131498_BLAC_1.jpg

1632 ms

131506_CHAH_1.jpg

131506_CHAH_1.jpg

1698 ms

131504_BLAC_1.jpg

131504_BLAC_1.jpg

1881 ms

131494_BLAC_1.jpg

131494_BLAC_1.jpg

1890 ms

all.js

all.js

160 ms

164 ms

xd_arbiter.php

xd_arbiter.php

154 ms

xd_arbiter.php

xd_arbiter.php

275 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

336 ms

stussy-stock-logo.svg

stussy-stock-logo.svg

597 ms

nav-slash.gif

nav-slash.gif

391 ms

arrow.gif

arrow.gif

393 ms

search-magnifying-glass.gif

search-magnifying-glass.gif

394 ms

arrow-right-dark.gif

arrow-right-dark.gif

596 ms

ico.gif

ico.gif

584 ms

post-facebook.gif

post-facebook.gif

569 ms

footer-facebook.png

footer-facebook.png

569 ms

footer-instagram.png

footer-instagram.png

760 ms

post-twitter.gif

post-twitter.gif

727 ms

footer-twitter.png

footer-twitter.png

754 ms

footer-vimeo.png

footer-vimeo.png

731 ms

i.js

i.js

187 ms

ga.js

ga.js

79 ms

me

me

125 ms

top.links

top.links

518 ms

300lo.json

300lo.json

104 ms

ping

ping

100 ms

home-slide-arrow-left.png

home-slide-arrow-left.png

233 ms

home-slide-arrow-right.png

home-slide-arrow-right.png

423 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

49 ms

__utm.gif

__utm.gif

34 ms

init1.js

init1.js

296 ms

Accessibility Review

stussy.com.tw accessibility score

83

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

stussy.com.tw best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stussy.com.tw SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

stussy.com.tw

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