8.8 sec in total
564 ms
7.2 sec
1.1 sec
Click here to check amazing Burg 13 content for Japan. Otherwise, check out these important facts you probably never knew about burg13.com
横浜ブルク13,横浜桜木町駅から徒歩1分.TOCみなとみらいにワンランク上のシネマコンプレックス誕生
Visit burg13.comWe analyzed Burg13.com page load time and found that the first response time was 564 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
burg13.com performance score
564 ms
334 ms
360 ms
657 ms
335 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 37% of them (56 requests) were addressed to the original Burg13.com, 47% (71 requests) were made to Pr.tjoy.jp and 10% (15 requests) were made to T-joy.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Pr.tjoy.jp.
Page size can be reduced by 228.6 kB (16%)
1.4 MB
1.2 MB
In fact, the total size of Burg13.com main page is 1.4 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 9.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 18% 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 9.6 kB or 72% of the original size.
Potential reduce by 161.8 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, Burg 13 needs image optimization as it can save up to 161.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.6 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 5.6 kB or 19% of the original size.
Potential reduce by 51.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. Burg13.com needs all CSS files to be minified and compressed as it can save up to 51.5 kB or 76% of the original size.
Number of requests can be reduced by 43 (29%)
149
106
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Burg 13. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
index.html
564 ms
import.css
334 ms
function.js
360 ms
swfobject.js
657 ms
common.css
335 ms
top.css
389 ms
info.css
225 ms
schedule.css
575 ms
faq.css
398 ms
facilities.css
415 ms
access.css
550 ms
recruit.css
510 ms
sitemap.css
574 ms
eat.css
600 ms
price.css
603 ms
kinezo.css
682 ms
rule.css
770 ms
suica.css
766 ms
adticket.css
754 ms
widget.js
69 ms
widgets.js
5 ms
conversion.js
15 ms
ayakano.jpg
1142 ms
sp_kinezo_bnr_yellow.jpg
1263 ms
ja_follow_me-a.png
161 ms
189935971074547.1593.1371571649.png
168 ms
selector.jpg
1758 ms
chihayahuru.jpg
1522 ms
doukyusei.jpg
1345 ms
shiro1.jpg
606 ms
bokumachi.jpg
1023 ms
shinshunwb_movie.jpg
1404 ms
bnr_s.jpg
1649 ms
kinezo_coupon.jpg
1539 ms
banner315.jpg
1536 ms
bg_wrapper.gif
191 ms
bg_header.gif
183 ms
logo_burg.gif
224 ms
bg_mainnav.gif
335 ms
btn_recruit.gif
197 ms
btn_sitemap.gif
204 ms
bg_container.gif
363 ms
t_schedule.gif
381 ms
t_coming.gif
391 ms
t_info.gif
405 ms
btn_pagetop.gif
443 ms
bn_kinezo.gif
502 ms
bn_mobile_qr.gif
543 ms
bn_ticket.gif
573 ms
bunner_powerup.jpg
1261 ms
bunner_u-next.png
1298 ms
pitta.jpg
1527 ms
mobilesuica20120329.jpg
1748 ms
coming_soon.html
1139 ms
information.html
984 ms
bg_coming.gif
595 ms
bg_info.gif
649 ms
bn_mobile.gif
655 ms
45 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
28 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
17 ms
34 ms
jot
99 ms
sflash_160323.jpg
1063 ms
sflash_160315.jpg
1123 ms
sflash_160302.jpg
1170 ms
sflash_160304.jpg
1189 ms
sflash_160309.jpg
1199 ms
sflash_160328.jpg
1669 ms
btn_officialsite.gif
205 ms
import.css
398 ms
sflash_160318.jpg
1456 ms
sflash_160332.jpg
1306 ms
sflash_160314.jpg
1363 ms
sflash_160312.jpg
1573 ms
sflash_160306.jpg
1613 ms
sflash_160305.jpg
1686 ms
sflash_160313.jpg
1776 ms
sflash_160317.jpg
1592 ms
sflash_160343.jpg
1617 ms
sflash_160316.jpg
1589 ms
sflash_160321.jpg
1634 ms
sflash_160308.jpg
1912 ms
sflash_160303.jpg
1890 ms
sflash_160319.jpg
1936 ms
sflash_160301.jpg
1795 ms
sflash_160310.jpg
1810 ms
sflash_160330.jpg
1841 ms
sflash_160320.jpg
1998 ms
sflash_160411.jpg
2017 ms
sflash_160417.jpg
2256 ms
sflash_160418.jpg
2085 ms
sflash_160404.jpg
2128 ms
sflash_160427.jpg
2113 ms
sflash_160401.jpg
2204 ms
sflash_160420.jpg
2430 ms
sflash_160410.jpg
2464 ms
sflash_160407.jpg
2290 ms
sflash_160415.jpg
2546 ms
sflash_160419.jpg
2408 ms
sflash_160413.jpg
2301 ms
common.css
197 ms
top.css
381 ms
info.css
556 ms
schedule.css
734 ms
faq.css
832 ms
facilities.css
833 ms
access.css
391 ms
recruit.css
574 ms
sitemap.css
584 ms
eat.css
927 ms
price.css
779 ms
kinezo.css
789 ms
rule.css
903 ms
suica.css
959 ms
adticket.css
983 ms
banner315.jpg
561 ms
sflash_160412.jpg
1600 ms
sflash_160409.jpg
1866 ms
sflash_160414.jpg
1849 ms
sflash_160326.jpg
1662 ms
sflash_160423.jpg
1660 ms
sflash_160501.jpg
1859 ms
sflash_160406.jpg
1565 ms
sflash_160402.jpg
2803 ms
sflash_160405.jpg
1479 ms
sflash_160416.jpg
1551 ms
sflash_160424.jpg
1570 ms
sflash_160403.jpg
1557 ms
sflash_160408.jpg
1782 ms
sflash_160504.jpg
1603 ms
sflash_160502.jpg
1926 ms
sflash_160425.jpg
1605 ms
sflash_160426.jpg
1619 ms
sflash_160506.jpg
1614 ms
sflash_160509.jpg
1620 ms
sflash_160507.jpg
1615 ms
sflash_160503.jpg
1612 ms
sflash_160505.jpg
1710 ms
sflash_160510.jpg
1714 ms
sflash_160508.jpg
1675 ms
sflash_160607.jpg
1697 ms
sflash_160606.jpg
2216 ms
sflash_160603.jpg
1733 ms
sflash_160601.jpg
1709 ms
sflash_160605.jpg
1671 ms
sflash_160602.jpg
1674 ms
sflash_160604.jpg
1742 ms
sflash_160705.jpg
1645 ms
sflash_160701.jpg
1667 ms
sflash_160704.jpg
1666 ms
sflash_160702.jpg
1769 ms
burg13.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Burg13.com 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 Burg13.com 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.
burg13.com
Open Graph description is not detected on the main page of Burg 13. 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: