10.1 sec in total
402 ms
8.7 sec
937 ms
Welcome to puchibus.jp homepage info - get ready to check Puchibus best content for Japan right away, or after learning these important things about puchibus.jp
1人でも4人でも超楽しい!ぶっ放し協力バトル「崖っぷちバスターズ」の公式サイト。
Visit puchibus.jpWe analyzed Puchibus.jp page load time and found that the first response time was 402 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
puchibus.jp performance score
402 ms
325 ms
152 ms
300 ms
303 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 35% of them (39 requests) were addressed to the original Puchibus.jp, 19% (21 requests) were made to Pbs.twimg.com and 16% (18 requests) were made to Img.puchibus.jp.s3-website-ap-northeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Img.puchibus.jp.s3-website-ap-northeast-1.amazonaws.com.
Page size can be reduced by 883.4 kB (7%)
12.6 MB
11.7 MB
In fact, the total size of Puchibus.jp main page is 12.6 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 11.8 MB which makes up the majority of the site volume.
Potential reduce by 28.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. 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 28.0 kB or 76% of the original size.
Potential reduce by 333.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. Puchibus images are well optimized though.
Potential reduce by 273.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 273.5 kB or 62% of the original size.
Potential reduce by 248.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. Puchibus.jp needs all CSS files to be minified and compressed as it can save up to 248.5 kB or 83% of the original size.
Number of requests can be reduced by 39 (37%)
105
66
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Puchibus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
puchibus.jp
402 ms
www.puchibus.jp
325 ms
normalize.css
152 ms
base.css
300 ms
layout.css
303 ms
module.css
300 ms
state.css
303 ms
theme_top.css
300 ms
style.css
302 ms
conversion.js
15 ms
line-button.js
576 ms
jquery-1.9.1.min.js
610 ms
jquery.bxslider.min.js
463 ms
jquery.colorbox-min.js
466 ms
script.js
466 ms
jquery.heightLine.js
465 ms
wp-emoji-release.min.js
157 ms
analytics.js
53 ms
61 ms
logo_cliffbusters_017.png
1044 ms
logo_drecom_01.png
349 ms
btn_pagetop_01.png
350 ms
img_app_013.png
1044 ms
txt_app_01.png
465 ms
btn_app_01.png
464 ms
btn_app_02.png
464 ms
movie_0001.png
1041 ms
ttl_twitter_014.png
631 ms
ttl_about_014.png
1226 ms
txt_about_014.png
1040 ms
txt_about_023.png
3554 ms
ttl_about_024.png
1359 ms
txt_about_034.png
4660 ms
txt_about_044.png
2413 ms
txt_about_054.png
1983 ms
txt_about_064.png
2145 ms
ttl_about_034.png
1861 ms
txt_about_073.png
7693 ms
6e1f8704e9573e0a4a9132cb6ee1426f.png
2315 ms
sdk.js
180 ms
bg_wrap_pc.jpg
1807 ms
bd_head_01.png
345 ms
widgets.js
18 ms
bg_app_01.png
1203 ms
bg_twitter_01.png
506 ms
bg_sec_01.png
505 ms
bd_frame1_01.png
733 ms
bd_frame1_02.png
734 ms
zElv50_FoAU
126 ms
bg_frame1_01.png
640 ms
bg_about_01.png
1023 ms
bg_about_02.png
1564 ms
bg_about_04.png
2855 ms
bg_about_03.png
1654 ms
bg_frame2_01.png
1126 ms
bg_frame2_02.png
1274 ms
bd_frame2_01.png
1338 ms
bd_frame2_02.png
1423 ms
collect
28 ms
42 ms
www-embed-player-vflfNyN_r.css
79 ms
www-embed-player.js
98 ms
base.js
234 ms
284 ms
xd_arbiter.php
277 ms
xd_arbiter.php
406 ms
bd_footer_01.png
1250 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
189 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
201 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
53 ms
ad_status.js
72 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
146 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
147 ms
like.php
118 ms
syndication
143 ms
537609715862089730
218 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
57 ms
like.php
103 ms
wy1X4hBW7e7.js
464 ms
LVx-xkvaJ0b.png
418 ms
wy1X4hBW7e7.js
447 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
5 ms
X0GSZJG9_normal.png
263 ms
Cd0ZvPRUEAABXqB.png:small
319 ms
Cdy5oKBUsAAde0f.png:small
312 ms
Cdvd4W5UYAA01r9.png:small
265 ms
CdtwA6pUEAExL0L.png:small
467 ms
CdqiBpRUkAARiG9.png:small
265 ms
CdombgjUMAAyD6W.png:small
265 ms
CdlKsjFUEAA98LC.png:small
266 ms
Cdjc3AJUMAAO2o0.png:small
270 ms
CdgBIVqUkAA2tgV.png:small
273 ms
CdeTQnFUMAIrEvG.png:small
272 ms
Cdapzc5UMAAJD-w.png:small
335 ms
CdZJqLFUsAAt0Rq.png:small
274 ms
CdVgNkrUsAAaHZX.png:small
274 ms
CdUAEUxUsAAyjLl.png:small
282 ms
CdQWoL-UMAAuWDh.png:small
304 ms
CdO2e6SUYAAZNz7.png:small
350 ms
CdLawpUVIAA3Ly1.png:small
334 ms
CdJs5n2UYAAkhvK.png:small
336 ms
CdGRLVgUYAEhTmg.png:small
407 ms
CdEjUA-UsAEAW0-.png:small
408 ms
jot.html
1 ms
base.css
152 ms
layout.css
152 ms
module.css
153 ms
state.css
152 ms
theme_top.css
152 ms
puchibus.jp SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Puchibus.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Puchibus.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.
puchibus.jp
Open Graph data is detected on the main page of Puchibus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: