13.3 sec in total
991 ms
9 sec
3.3 sec
Welcome to shirt.co.jp homepage info - get ready to check SHIRT best content for Japan right away, or after learning these important things about shirt.co.jp
鎌倉シャツでは、正しいビジネスシーンの着こなしをお手伝いしています。日本では「正しい着こなし」を教えてくれる機会がほとんどありませんが、相手は服装を見ていることが多いのです。颯爽とした服を着て振る舞えば、きっと、説得力が高まります。
Visit shirt.co.jpWe analyzed Shirt.co.jp page load time and found that the first response time was 991 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
shirt.co.jp performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value15.7 s
0/100
25%
Value17.5 s
0/100
10%
Value2,390 ms
5/100
30%
Value0.3
39/100
15%
Value12.2 s
15/100
10%
991 ms
313 ms
476 ms
632 ms
350 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 90% of them (112 requests) were addressed to the original Shirt.co.jp, 4% (5 requests) were made to Google.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.4 sec) belongs to the original domain Shirt.co.jp.
Page size can be reduced by 467.6 kB (11%)
4.3 MB
3.8 MB
In fact, the total size of Shirt.co.jp main page is 4.3 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. 70% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 27.6 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 27.6 kB or 80% of the original size.
Potential reduce by 74.5 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. SHIRT images are well optimized though.
Potential reduce by 126.2 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 126.2 kB or 60% of the original size.
Potential reduce by 239.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. Shirt.co.jp needs all CSS files to be minified and compressed as it can save up to 239.2 kB or 83% of the original size.
Number of requests can be reduced by 43 (35%)
122
79
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SHIRT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
shirt.co.jp
991 ms
normalize.css
313 ms
font.css
476 ms
common.css
632 ms
shadowbox.css
350 ms
index.css
723 ms
jquery-2.1.1.min.js
1086 ms
TweenMax.min.js
1211 ms
CustomEase.js
633 ms
jquery.gsap.min.js
662 ms
smart-crossfade.js
788 ms
common.js
791 ms
EaselPlugin.min.js
828 ms
SplitText.min.js
907 ms
modernizr.js
946 ms
shadowbox.js
1299 ms
jquery.superscrollorama.js
994 ms
easeljs-0.7.1.min.js
1448 ms
preloadjs-0.4.1.min.js
1125 ms
index.js
1155 ms
jsapi.js
1139 ms
16 ms
default+en.css
2 ms
default+en.I.js
4 ms
logo00.png
275 ms
nav_btn00.png
232 ms
nav_txt07.png
230 ms
nav_txt05.png
226 ms
nav_txt06.png
225 ms
nav_txt03.png
226 ms
nav_txt01.png
301 ms
nav_txt00.png
312 ms
nav_txt02.png
322 ms
nav_txt10.png
340 ms
nav_txt09.png
409 ms
nav_txt04.png
409 ms
header_txt00.png
593 ms
header_txt01.png
593 ms
mark00.png
594 ms
mark01.png
594 ms
mark02.png
614 ms
slide_freshers.jpg
1274 ms
slide_dammy.png
622 ms
loading_white.gif
782 ms
arrow00_l.svg
645 ms
arrow00_r.svg
647 ms
c0_bg00.jpg
771 ms
c0_img00.jpg
1126 ms
c0_txt00.svg
803 ms
c0_img01.jpg
805 ms
c0_txt01.svg
951 ms
c0_img02.jpg
1093 ms
c0_txt02.svg
961 ms
c0_img03.jpg
958 ms
c0_txt03.svg
1126 ms
c0_img04.jpg
1120 ms
c0_txt04.svg
1118 ms
c1_txt00.svg
1241 ms
arrow01.svg
1273 ms
c1_txt01.svg
1265 ms
ga.js
160 ms
kPT5Pl9QRG8
103 ms
c2_title00.svg
1063 ms
brand_dammy.png
1091 ms
logo01.svg
1185 ms
logo02.svg
1223 ms
logo03.svg
1217 ms
__utm.gif
11 ms
logo04.svg
1145 ms
logo05.svg
1160 ms
collect
285 ms
logo06.svg
1186 ms
www-embed-player-vfltSWGRn.css
126 ms
www-embed-player.js
201 ms
c2_title01.svg
1226 ms
logo07.svg
1261 ms
logo14.svg
1196 ms
logo13.svg
1212 ms
logo10.svg
1035 ms
logo11.svg
1084 ms
logo12.svg
1127 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
45 ms
ad_status.js
50 ms
logo08.svg
1147 ms
logo09.svg
1140 ms
bnr_01.png
1170 ms
c3_txt00.svg
1147 ms
bnr_02.png
1210 ms
c3_txt01.svg
1106 ms
bnr_03.png
1137 ms
c3_txt02.svg
1115 ms
c3_img03.png
1160 ms
c3_txt03.svg
1007 ms
bnr_05.png
1078 ms
c3_txt04.svg
1068 ms
c4_title00.svg
984 ms
c4_img01.png
952 ms
c4_img02.png
1006 ms
c4_img03.png
1012 ms
c4_img04.png
1053 ms
c4_img05.png
971 ms
c4_img06.png
1108 ms
arrow02_l.svg
949 ms
arrow02_r.svg
1007 ms
footer_bg00.jpg
1017 ms
footer_txt00.svg
1029 ms
footer_txt01.svg
994 ms
footer_txt02.svg
953 ms
mark03.svg
1017 ms
mark04.svg
1040 ms
mark05.svg
1040 ms
arrow03.svg
1054 ms
arrow03_2.svg
989 ms
slide_freshers_s.jpg
982 ms
slide_atago_s.jpg
1023 ms
slide_bfp_s.jpg
1040 ms
slide_dicros_s.jpg
1029 ms
brand_01.png
1190 ms
slide_atago.jpg
1783 ms
brand_02.png
3382 ms
slide_bfp.jpg
1668 ms
slide_dicros.jpg
182 ms
Gfeeds
331 ms
brand_03.png
704 ms
shirt.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
shirt.co.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
shirt.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shirt.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Shirt.co.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.
shirt.co.jp
Open Graph data is detected on the main page of SHIRT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: