11.4 sec in total
1 sec
9.7 sec
612 ms
Welcome to bandtokyo.info homepage info - get ready to check Bandtokyo best content right away, or after learning these important things about bandtokyo.info
中学生・高校生のためのバンドスクール「ミュージックスクール・ライブジャム」メンバーと仲良くなりバンドを組んでライブをする音楽教室です。ヴォーカル、ギター、ベース、ドラム、キーボード・作曲/DTMの個人レッスンと共にバンドレッスンを提供しています。
Visit bandtokyo.infoWe analyzed Bandtokyo.info page load time and found that the first response time was 1 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
bandtokyo.info performance score
1018 ms
357 ms
354 ms
1163 ms
560 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 70% of them (120 requests) were addressed to the original Bandtokyo.info, 9% (15 requests) were made to Maps.googleapis.com and 5% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Bandtokyo.info.
Page size can be reduced by 1.7 MB (23%)
7.2 MB
5.6 MB
In fact, the total size of Bandtokyo.info main page is 7.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 54.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. 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 54.1 kB or 80% of the original size.
Potential reduce by 876.4 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. Obviously, Bandtokyo needs image optimization as it can save up to 876.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 699.5 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 699.5 kB or 71% of the original size.
Potential reduce by 26.5 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. Bandtokyo.info needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 83% of the original size.
Number of requests can be reduced by 62 (37%)
166
104
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bandtokyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
bandtokyo.info
1018 ms
style.css
357 ms
mobile.css
354 ms
jquery-1.7.1.min.js
1163 ms
jquery.easing.1.3.js
560 ms
jquery.mousewheel.min.js
510 ms
jquery.inview.js
704 ms
jquery.cookie.js
529 ms
jquery.ba-hashchange.min.js
713 ms
jquery.queryloader2.js
813 ms
script.js
707 ms
8_plugin.css
899 ms
8.css
1012 ms
8_mobile.css
864 ms
script.js
1358 ms
jquery.skitter.js
1699 ms
jquery.animate-colors-min.js
1054 ms
jquery.fancybox-1.3.4.js
1260 ms
jquery.jrumble.1.3.min.js
1202 ms
script.js
1239 ms
script.js
1350 ms
script.js
1430 ms
script.js
1437 ms
script.js
1453 ms
script.js
1544 ms
script.js
1581 ms
naviAnimate.js
1590 ms
script.js
1624 ms
script.js
1711 ms
script.js
1858 ms
script.js
1869 ms
script.js
1758 ms
ga.js
144 ms
maps
210 ms
67_2.jpg
526 ms
69_2.jpg
996 ms
68_2.jpg
1124 ms
59_2.jpg
870 ms
58_2.jpg
661 ms
62_2.jpg
868 ms
62_2.jpg
1063 ms
63_2.jpg
1156 ms
64_2.jpg
1369 ms
65_2.jpg
1517 ms
66_2.jpg
1579 ms
67_2.jpg
1408 ms
44_3.jpg
1292 ms
42_3.jpg
1365 ms
43_3.jpg
1451 ms
41_3.jpg
1640 ms
button.png
1553 ms
button.png
1587 ms
75.png
1772 ms
51.png
1826 ms
34.png
1841 ms
48.png
1836 ms
bg.png
1888 ms
thanks.png
1943 ms
widgets.js
19 ms
embed
404 ms
__utm.gif
16 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
22 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
13 ms
jot
98 ms
js
74 ms
init_embed.js
64 ms
common.js
64 ms
map.js
64 ms
google4.png
82 ms
overlay.js
12 ms
util.js
77 ms
onion.js
78 ms
search_impl.js
79 ms
StaticMapService.GetMapImage
319 ms
stats.js
45 ms
openhand_8_8.cur
40 ms
ViewportInfoService.GetViewportInfo
61 ms
ViewportInfoService.GetViewportInfo
31 ms
kh
47 ms
transparent.png
20 ms
controls.js
23 ms
ViewportInfoService.GetViewportInfo
79 ms
css
102 ms
entity11.png
62 ms
vt
150 ms
vt
139 ms
vt
136 ms
vt
126 ms
vt
134 ms
vt
141 ms
vt
226 ms
mapcnt6.png
41 ms
tmapctrl.png
36 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
47 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
47 ms
AuthenticationService.Authenticate
13 ms
0.jpg
1396 ms
17.png
1383 ms
16.png
1367 ms
12.png
1360 ms
6.png
1417 ms
7.png
1291 ms
53.png
2053 ms
49.png
1266 ms
24.jpg
1411 ms
33.png
1247 ms
34.jpg
1463 ms
35.jpg
1046 ms
play.png
1075 ms
82.png
1102 ms
42.png
1242 ms
fancybox.png
1295 ms
fancybox-x.png
1115 ms
fancybox-y.png
1148 ms
blank.gif
1263 ms
0.jpg
1264 ms
67_2.jpg
1299 ms
69_2.jpg
1462 ms
68_2.jpg
1438 ms
51.png
1284 ms
7.png
1288 ms
thanks.png
1308 ms
58_2.jpg
1426 ms
59_2.jpg
1577 ms
62_2.jpg
1320 ms
17.png
2283 ms
62_2.jpg
1771 ms
63_2.jpg
1550 ms
64_2.jpg
1585 ms
16.png
1429 ms
65_2.jpg
1601 ms
67_2.jpg
1471 ms
12.png
1543 ms
44_3.jpg
1597 ms
53.png
1880 ms
49.png
1670 ms
66_2.jpg
1589 ms
43_3.jpg
1607 ms
42_3.jpg
1569 ms
41_3.jpg
1642 ms
24.jpg
1675 ms
33.png
1543 ms
6.png
1547 ms
34.jpg
1768 ms
35.jpg
1497 ms
button.png
1516 ms
play.png
1484 ms
button.png
1571 ms
75.png
1471 ms
34.png
1834 ms
82.png
1497 ms
42.png
1475 ms
48.png
1424 ms
fancybox.png
1416 ms
fancybox-x.png
1423 ms
fancybox-y.png
1483 ms
blank.gif
1472 ms
253 ms
all.js
269 ms
prev.png
969 ms
next.png
968 ms
ajax-loader.gif
953 ms
232 ms
xd_arbiter.php
221 ms
xd_arbiter.php
427 ms
QuotaService.RecordEvent
13 ms
164 ms
like.php
183 ms
wy1X4hBW7e7.js
488 ms
LVx-xkvaJ0b.png
552 ms
bandtokyo.info SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bandtokyo.info can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Bandtokyo.info 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.
bandtokyo.info
Open Graph data is detected on the main page of Bandtokyo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: