9.2 sec in total
991 ms
7.7 sec
503 ms
Welcome to shapeshop.co.jp homepage info - get ready to check Shapeshop best content right away, or after learning these important things about shapeshop.co.jp
トップページ|BODYSOLID,バーサーカー,トレーニング器具,リハビリ機器通販のシェイプショップ
Visit shapeshop.co.jpWe analyzed Shapeshop.co.jp page load time and found that the first response time was 991 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
shapeshop.co.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.2 s
71/100
25%
Value5.8 s
50/100
10%
Value110 ms
98/100
30%
Value0.162
72/100
15%
Value3.3 s
94/100
10%
991 ms
320 ms
324 ms
339 ms
341 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 71% of them (113 requests) were addressed to the original Shapeshop.co.jp, 17% (27 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Shapeshop.co.jp.
Page size can be reduced by 172.8 kB (20%)
850.8 kB
678.0 kB
In fact, the total size of Shapeshop.co.jp main page is 850.8 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. 60% of websites need less resources to load. Images take 631.7 kB which makes up the majority of the site volume.
Potential reduce by 57.0 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 20.9 kB, which is 32% 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 57.0 kB or 88% of the original size.
Potential reduce by 13.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. Shapeshop images are well optimized though.
Potential reduce by 63.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 63.4 kB or 59% of the original size.
Potential reduce by 39.3 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. Shapeshop.co.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 85% of the original size.
Number of requests can be reduced by 45 (29%)
157
112
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shapeshop. 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 15 to 1 for CSS and as a result speed up the page load time.
shapeshop.co.jp
991 ms
import.css
320 ms
css.js
324 ms
navi.js
339 ms
win_op.js
341 ms
site.js
487 ms
jquery-1.4.2.min.js
925 ms
roll.js
659 ms
reset.css
335 ms
common.css
369 ms
contents.css
563 ms
table.css
524 ms
bloc.css
640 ms
bloc_alpha.css
653 ms
popup.css
681 ms
print.css
885 ms
ga.js
70 ms
f603_anim.gif
2504 ms
kabe_02.gif
159 ms
header.gif
334 ms
logo.gif
341 ms
header_catch.gif
342 ms
bt_01.gif
346 ms
bt_02.gif
349 ms
bt_03.gif
500 ms
bt_04.gif
711 ms
bt_05.gif
710 ms
bt_06.gif
711 ms
hnavi1.gif
715 ms
hnavi2.gif
712 ms
hnavi3.gif
835 ms
member.gif
1015 ms
h2_search.gif
1014 ms
ico_arrow_03.gif
1041 ms
serach.gif
1022 ms
h2_cat.gif
1257 ms
h2_calendar.gif
1261 ms
ban_kominato.jpg
1347 ms
h2_1.gif
1368 ms
main2a.jpg
1555 ms
main1a.jpg
1370 ms
main3a.jpg
1695 ms
h2_2.gif
1540 ms
spl1.gif
1659 ms
spl2.gif
1696 ms
spl3.gif
1720 ms
spl4.gif
1873 ms
spl5.gif
1900 ms
spl6.gif
2012 ms
spl7.gif
2029 ms
spl8.gif
2050 ms
spl9.gif
2062 ms
spl10.gif
2195 ms
spl11.gif
2161 ms
__utm.gif
13 ms
likebox.php
198 ms
likebox.php
781 ms
spl12.gif
2173 ms
410ucuAGgaJ.css
169 ms
tSbl8xBI27R.css
209 ms
q68gy-v_YMF.js
290 ms
FJmpeSpHpjS.js
366 ms
0wM5s1Khldu.js
306 ms
1bNoFZUdlYZ.js
306 ms
h2_3.gif
2018 ms
kaigo1a.jpg
2033 ms
kaigo2a.jpg
2050 ms
kaigo3a.jpg
2191 ms
kaigo4a.jpg
2173 ms
h2_8.gif
2158 ms
316484_173238966091161_479774734_n.jpg
175 ms
wL6VQj7Ab77.png
49 ms
s7jcwEQH7Sx.png
48 ms
h2_4.gif
1949 ms
h2_5.gif
1964 ms
resize_image.php
2049 ms
ico1.gif
2163 ms
resize_image.php
2192 ms
ico2.gif
2147 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
80 ms
Czh0gDTFcBt.css
46 ms
VyhHmC9SnBT.css
43 ms
Ek6lpayKeeB.css
84 ms
EoarYgA68t4.css
59 ms
njO1TPvGzoR.js
80 ms
OloiM1PZafe.js
81 ms
LTv6ZK-5zxz.js
205 ms
1FCa-btixu2.js
106 ms
Oagsvfb4VWi.js
155 ms
pObvZSrFc_4.js
158 ms
Kt4tkgSRvHH.js
119 ms
H3EKDTObx05.js
121 ms
eR-qA8bp1RM.js
137 ms
1QuX41zDRrx.js
158 ms
resize_image.php
2005 ms
ico3.gif
1968 ms
resize_image.php
2118 ms
ico4.gif
2153 ms
10354686_10150004552801856_220367501106153455_n.jpg
119 ms
safe_image.php
211 ms
safe_image.php
285 ms
safe_image.php
325 ms
safe_image.php
362 ms
safe_image.php
327 ms
249319_102068513318756_1953497287_n.jpg
117 ms
269816_125197547566736_2668800_n.jpg
123 ms
1379841_10150004552801901_469209496895221757_n.jpg
162 ms
549744_101641176654800_1306347920_n.jpg
166 ms
205991_106424196202180_1258983460_n.jpg
196 ms
12651042_812877032174216_1223017901350436730_n.jpg
165 ms
540553_254807897951693_1738396156_n.jpg
161 ms
QDwYpIaRyfG.png
110 ms
K00K-UgnsKu.png
110 ms
gxbPuQdXIZP.png
57 ms
resize_image.php
2013 ms
ico5.gif
2042 ms
h2_6.gif
1964 ms
resize_image.php
1994 ms
resize_image.php
2144 ms
resize_image.php
2009 ms
resize_image.php
2101 ms
resize_image.php
2011 ms
h2_7.gif
1937 ms
1.jpg
2172 ms
2.jpg
2128 ms
3.jpg
2015 ms
4.jpg
2217 ms
5.jpg
2110 ms
powerjacket.jpg
1956 ms
7.jpg
2130 ms
8.jpg
2359 ms
9.jpg
2048 ms
250.jpg
2128 ms
S1.jpg
2120 ms
S2.jpg
2139 ms
S11.jpg
2172 ms
S12.jpg
2162 ms
S5.jpg
2128 ms
s16.jpg
2228 ms
s17.jpg
2124 ms
S8.jpg
2151 ms
S9.jpg
2225 ms
S18.jpg
2170 ms
S19a.jpg
2080 ms
S24a.jpg
2200 ms
S22a.jpg
2163 ms
S23a.jpg
2209 ms
S21a.jpg
2235 ms
SStanren.jpg
2328 ms
SScramer.jpg
2244 ms
SSvenexR.jpg
2346 ms
SSmac.jpg
2364 ms
bn_pagetop.gif
2208 ms
ico_arrow_01.gif
2215 ms
ico_level.gif
2266 ms
ico_arrow_04.gif
2246 ms
line_dot_01.gif
2189 ms
__utm.gif
4 ms
shapeshop.co.jp accessibility score
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.
shapeshop.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
shapeshop.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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shapeshop.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 Shapeshop.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.
shapeshop.co.jp
Open Graph description is not detected on the main page of Shapeshop. 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: