7.1 sec in total
949 ms
5.2 sec
960 ms
Welcome to asamizo-stadium.jpn.org homepage info - get ready to check Asamizo Stadium Jpn best content for Japan right away, or after learning these important things about asamizo-stadium.jpn.org
相模原麻溝公園競技場
Visit asamizo-stadium.jpn.orgWe analyzed Asamizo-stadium.jpn.org page load time and found that the first response time was 949 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
asamizo-stadium.jpn.org performance score
949 ms
368 ms
526 ms
542 ms
597 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 21% of them (29 requests) were addressed to the original Asamizo-stadium.jpn.org, 15% (21 requests) were made to Blog.sakura.ne.jp and 8% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Taikyo.sakura.ne.jp.
Page size can be reduced by 507.6 kB (27%)
1.9 MB
1.4 MB
In fact, the total size of Asamizo-stadium.jpn.org main page is 1.9 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 10.1 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.5 kB, which is 11% 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 10.1 kB or 71% of the original size.
Potential reduce by 37.1 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. Asamizo Stadium Jpn images are well optimized though.
Potential reduce by 203.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 203.1 kB or 69% of the original size.
Potential reduce by 257.4 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. Asamizo-stadium.jpn.org needs all CSS files to be minified and compressed as it can save up to 257.4 kB or 83% of the original size.
Number of requests can be reduced by 48 (36%)
133
85
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Asamizo Stadium Jpn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
asamizo-stadium.jpn.org
949 ms
style2-1128.css
368 ms
rogo-toumei.png
526 ms
logo6.gif
542 ms
npc.cgi
597 ms
gaiyo1210.gif
409 ms
riyo-annnai1210-2.gif
544 ms
senyou1210.gif
562 ms
annai1210.gif
587 ms
event1210.gif
701 ms
mail1210.gif
544 ms
blog1210gif
541 ms
link1210.gif
573 ms
main.png
608 ms
sub.png
613 ms
news.html
701 ms
VL3aud330dw
76 ms
www-embed-player-vflfNyN_r.css
24 ms
www-embed-player.js
40 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
32 ms
ad_status.js
37 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
54 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
55 ms
style.css
536 ms
style-iphone.css
544 ms
table.css
193 ms
style2.css
180 ms
widgets.js
88 ms
asamizo-stadium.sblo.jp
1231 ms
haikei-top.jpg
1131 ms
banar_sagamihara_green_hotel.jpg
181 ms
bana-60120.gif
185 ms
argus_research.jpg
195 ms
argus12060.jpg
180 ms
FunToShare.jpg
197 ms
argus_sokou12060.jpg
358 ms
argus_m12060.jpg
356 ms
get_adobe_reader.png
367 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
121 ms
syndication
99 ms
327686085046042624
192 ms
proxy.jpg
33 ms
proxy.jpg
77 ms
proxy.jpg
89 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
59 ms
pup3OyDF_normal.jpeg
34 ms
CdVAR9KUIAA4jXj.jpg:small
75 ms
CdU3L2UUsAA9qMc.jpg:small
69 ms
CdTrhu-VIAUY0Ib.jpg:small
77 ms
CaptjzpVIAEIdTd.jpg:small
190 ms
CalcZP6UcAA8sRi.jpg:small
191 ms
CWjVGwCU4AAKm9W.jpg:small
187 ms
CVmLgmiUwAEOzQD.jpg:small
197 ms
CVRJxq3UkAEAGLI.jpg:small
195 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
190 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
193 ms
styles-index.css
775 ms
user-common.css
518 ms
proxy.jpg
7 ms
ad_plugin.js
916 ms
proxy.jpg
36 ms
proxy.jpg
34 ms
bl-bookmarks.js
683 ms
jot.html
28 ms
blog_part2.png
1795 ms
pup3OyDF_normal.jpeg
8 ms
DSCN0472-1c8e4-thumbnail2.JPG
730 ms
DSCN0067-thumbnail2.jpg
914 ms
DSCN0063-thumbnail2.jpg
917 ms
DSCN8682-71f6e-thumbnail2.JPG
1110 ms
DSCN8309-thumbnail2.JPG
939 ms
DSCN47272028640x48029-thumbnail2.jpg
915 ms
159.gif
300 ms
150.gif
313 ms
140.gif
314 ms
160.gif
340 ms
146.gif
449 ms
1.gif
468 ms
162.gif
469 ms
158.gif
497 ms
145.gif
509 ms
87.gif
601 ms
163.gif
596 ms
powerdby.gif
622 ms
header.jpg
933 ms
floating_v2.css
730 ms
blog_top.jpg
235 ms
date.jpg
230 ms
blog_bottom.jpg
340 ms
sidetitle.jpg
196 ms
bookmark_button.js
347 ms
sdk.js
14 ms
button-only@2x.png
362 ms
bookmark.gif
189 ms
tweet.2c548e167cf5bdb0bd941e41896f257d.js
28 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
58 ms
159 ms
xd_arbiter.php
22 ms
xd_arbiter.php
58 ms
syndication
28 ms
tweets.json
117 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
89 ms
proxy.jpg
50 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
tweet.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
37 ms
CUJi4oMU8AAKi6d.jpg:large
197 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
30 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
38 ms
proxy.jpg
44 ms
224 ms
198 ms
194 ms
195 ms
370 ms
221 ms
376 ms
378 ms
374 ms
428 ms
jot
28 ms
jot.html
27 ms
reset.css
15 ms
entry-button.css
13 ms
bbtn-l_v3.png
9 ms
like.php
158 ms
like.php
122 ms
like.php
129 ms
like.php
119 ms
like.php
137 ms
like.php
134 ms
like.php
145 ms
like.php
149 ms
like.php
146 ms
like.php
160 ms
wy1X4hBW7e7.js
53 ms
LVx-xkvaJ0b.png
33 ms
asamizo-stadium.jpn.org SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asamizo-stadium.jpn.org 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 Asamizo-stadium.jpn.org 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.
asamizo-stadium.jpn.org
Open Graph description is not detected on the main page of Asamizo Stadium Jpn. 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: