9.9 sec in total
1.1 sec
6.5 sec
2.3 sec
Visit stussy.jp now to see the best up-to-date Stussy content for Japan and also check out these interesting facts you probably never knew about stussy.jp
ステューシー公式サイト. Worldwide Since 1980.
Visit stussy.jpWe analyzed Stussy.jp page load time and found that the first response time was 1.1 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
stussy.jp performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value8.7 s
1/100
25%
Value4.7 s
69/100
10%
Value1,680 ms
11/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
1055 ms
364 ms
22 ms
365 ms
365 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 91% of them (70 requests) were addressed to the original Stussy.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Stussy.jp.
Page size can be reduced by 378.3 kB (12%)
3.1 MB
2.7 MB
In fact, the total size of Stussy.jp main page is 3.1 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. 40% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 53.8 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 15.3 kB, which is 24% 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 53.8 kB or 83% of the original size.
Potential reduce by 89.3 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.
Potential reduce by 118.1 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 118.1 kB or 73% of the original size.
Potential reduce by 117.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.jp needs all CSS files to be minified and compressed as it can save up to 117.1 kB or 81% of the original size.
Number of requests can be reduced by 40 (53%)
76
36
The browser has sent 76 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 15 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
stussy.jp
1055 ms
import.css
364 ms
css
22 ms
style.css
365 ms
swfobject.js
365 ms
xmlhttprequest.js
389 ms
ec3.js
409 ms
jquery-1.10.2.js
6 ms
heightLine.js
543 ms
jquery.flexslider.js
913 ms
jquery.unveil.js
505 ms
trim_image.js
535 ms
mosaic.1.0.1.js
507 ms
base.css
363 ms
layout.css
547 ms
style.css
418 ms
prettyPhoto.css
397 ms
extend.css
455 ms
common.js
511 ms
colorbox.css
539 ms
jquery.colorbox.js
794 ms
spin.js
613 ms
ec3.css
182 ms
554272274_640.jpg
54 ms
151221094621.jpg
1043 ms
151211035659.jpg
1374 ms
151010010607.jpg
1491 ms
151221094621sp.jpg
729 ms
151211035659sp.jpg
816 ms
151010010607sp.jpg
737 ms
spmenu_close.jpg
903 ms
spsearch_off.jpg
919 ms
spmenu.png
1020 ms
nav_search_off.jpg
1079 ms
a11b4bb3ba448d1fa402ac3dc62cc91f3.jpg
1279 ms
f9fd259376f1bb114dea573e096635c6.jpg
1626 ms
a11b4bb3ba448d1fa402ac3dc62cc91f2.jpg
1383 ms
a11b4bb3ba448d1fa402ac3dc62cc91f1.jpg
1451 ms
a11b4bb3ba448d1fa402ac3dc62cc91f.jpg
1834 ms
a11b4bb3ba448d1fa402ac3dc62cc91f3.jpg
1560 ms
a11b4bb3ba448d1fa402ac3dc62cc91f4.jpg
1733 ms
08760fe7a1daa9936bdd520836fd8402.jpg
1818 ms
a11b4bb3ba448d1fa402ac3dc62cc91f.jpg
1671 ms
info01.jpg
1755 ms
140605020529.png
1830 ms
140605020540.png
1851 ms
140605020550.png
1906 ms
140618072816.png
1949 ms
140605020458.png
2000 ms
140605020520.png
2034 ms
140605020612.png
2013 ms
150127044937.png
2032 ms
all.js
49 ms
h_logo.jpg
2046 ms
nav_bar.gif
2094 ms
nav_onlinestore.png
2130 ms
icon_side_follow_pc.jpg
1974 ms
arrow01_pc.png
1981 ms
btn_play_off_pc.png
2006 ms
insta_feed_cell.php
2984 ms
arrow02_off_pc.png
2078 ms
ga.js
84 ms
xd_arbiter.php
40 ms
__utm.gif
232 ms
bg_f_boxnavi_pc02.jpg
1650 ms
pagetop.jpg
1650 ms
bg_f_icon_sns_pc.jpg
1588 ms
insta.css
523 ms
mosaic.1.0.1.js
195 ms
import.css
184 ms
base.css
176 ms
layout.css
390 ms
flexslider.css
183 ms
style.css
183 ms
prettyPhoto.css
207 ms
keyimg_prev.png
175 ms
keyimg_next.png
195 ms
stussy.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
stussy.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
stussy.jp SEO score
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
Document uses legible font sizes
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stussy.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Stussy.jp 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.
stussy.jp
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: