6.5 sec in total
369 ms
5.5 sec
635 ms
Welcome to kotaku.jp homepage info - get ready to check Kotaku best content for Japan right away, or after learning these important things about kotaku.jp
アクション系エンタメサイト「コタク・ジャパン」では映画、ゲーム、音楽、アニメ...
Visit kotaku.jpWe analyzed Kotaku.jp page load time and found that the first response time was 369 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kotaku.jp performance score
369 ms
158 ms
302 ms
163 ms
155 ms
Our browser made a total of 181 requests to load all elements on the main page. We found that 19% of them (35 requests) were addressed to the original Kotaku.jp, 8% (14 requests) were made to Cs.adingo.jp and 4% (8 requests) were made to Yads.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Sync.fout.jp.
Page size can be reduced by 692.7 kB (26%)
2.7 MB
2.0 MB
In fact, the total size of Kotaku.jp main page is 2.7 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 47.7 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 47.7 kB or 79% of the original size.
Potential reduce by 52.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. Kotaku images are well optimized though.
Potential reduce by 442.9 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 442.9 kB or 61% of the original size.
Potential reduce by 149.9 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. Kotaku.jp needs all CSS files to be minified and compressed as it can save up to 149.9 kB or 86% of the original size.
Number of requests can be reduced by 120 (71%)
168
48
The browser has sent 168 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kotaku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kotaku.jp
369 ms
cmn_layout_pc.css
158 ms
cmn_layout_tb.css
302 ms
cmn_layout_sp.css
163 ms
cmn_layout_sp350.css
155 ms
cmn_style.css
159 ms
jquery.js
342 ms
jquery.lazyload.min.js
305 ms
jquery.heightLine.js
309 ms
jquery.cookie.js
456 ms
magnific-popup.css
314 ms
jquery.magnific-popup.min.js
451 ms
common.js
468 ms
social.js
625 ms
config.js
466 ms
pjs.js
357 ms
cse.js
31 ms
cse.js
53 ms
sh.adingo.jp
354 ms
yads.js
591 ms
2-2754627-s.js
59 ms
58690X1381572.skimlinks.js
50 ms
cse.js
50 ms
cse.js
39 ms
dc.js
73 ms
cx.js
42 ms
logo_sp_header01.png
42 ms
61rqNmNpwjL.jpg
68 ms
51LuuLcF1iL.jpg
63 ms
51mQ3XosnZL.jpg
63 ms
51Yc10tuNkL.jpg
40 ms
41sddLFW4JL.jpg
36 ms
logo_sp_header02.png
36 ms
logo_sp_header03.png
38 ms
logo_sp_header04.png
39 ms
logo_sp_header05.png
61 ms
logo_sp_header06.png
33 ms
logo_sp_header07.png
63 ms
logo_orange_330x92.png
61 ms
loader.gif
62 ms
160328movietracksuits.jpg
63 ms
160325_teapotmetal.jpg
63 ms
160324ktrobotscover.jpg
66 ms
kotakutan_300x300.png
134 ms
gtm.js
134 ms
sdk.js
56 ms
jsapi
139 ms
btn_pc_hd01.png
40 ms
ico_pc_hd01.gif
41 ms
ico_pc_hd02.png
33 ms
__utm.gif
48 ms
p1.html
39 ms
158 ms
xd_arbiter.php
52 ms
xd_arbiter.php
109 ms
default+en.css
26 ms
default.css
54 ms
default+en.I.js
100 ms
p1.js
63 ms
default.css
25 ms
rep.gif
56 ms
sync
1015 ms
sync
362 ms
push_sync
846 ms
cm
360 ms
sync
84 ms
i.adingo.jp
383 ms
bg_pc_bdr01.gif
4 ms
i.adingo.jp
376 ms
yads_vimps-1.4.1.js
541 ms
tag
415 ms
sync
5 ms
770 ms
760 ms
728 ms
485 ms
443 ms
kotaku.js
264 ms
p-H-xmHxQy1p8Ku.gif
241 ms
187 ms
449 ms
495 ms
iframe
431 ms
160331thankyouandbyebye-thumb-640x640-109660.jpg
174 ms
160330moviesaudienceswalkedout-thumb-640x480-109661.jpg
89 ms
160318_drum1-thumb-640x359-109486.jpg
39 ms
search
115 ms
162 ms
152 ms
popin_discovery5-min.js
86 ms
833ffa90deebc7fd38df14a781e5ca538d6c18a503bb6d5de5c5639efabc1b17.jpg
37 ms
log.gif
335 ms
p.skimresources.com
32 ms
show_ads.js
16 ms
sh.adingo.jp
469 ms
ca-pub-9494435551872814.js
126 ms
zrt_lookup.html
111 ms
show_ads_impl.js
63 ms
sh.adingo.jp
570 ms
ads
221 ms
link
31 ms
track.php
29 ms
osd.js
17 ms
m_js_controller.js
41 ms
abg.js
54 ms
googlelogo_color_112x36dp.png
33 ms
nessie_icon_thin_arrow_short_white.png
26 ms
s
15 ms
x_button_blue2.png
10 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
5 ms
sync
235 ms
pixel.htm
60 ms
pixel
65 ms
cm
429 ms
sync
7 ms
sync
42 ms
sg.gif
384 ms
yads.js
499 ms
i.adingo.jp
431 ms
184 ms
ddc.htm
29 ms
179 ms
activeview
26 ms
Pug
31 ms
pixel
36 ms
rtset
40 ms
rum
24 ms
u.php
79 ms
64 ms
um
21 ms
177 ms
merge
21 ms
sync
27 ms
rum
23 ms
mapuser
20 ms
xrefid.xgi
25 ms
sd
18 ms
bd
60 ms
lr.gif
18 ms
tap.php
52 ms
NAX7020779800748740044
48 ms
pixel.htm
21 ms
sync
9 ms
i.adingo.jp
346 ms
bd
84 ms
ddc.htm
50 ms
g.js
73 ms
pixel
48 ms
4499
216 ms
8194545715463106768
85 ms
pixel.gif
91 ms
205 ms
-6672385123512703293
125 ms
52 ms
108 ms
fd065707-a551-4800-8de4-d65a50d612e6
137 ms
bde3629030e33ffca2aebc198a33b3e5
139 ms
38 ms
demconf.jpg
88 ms
appnexus
87 ms
demconf.jpg
88 ms
appnexus
82 ms
adsct
137 ms
cs
83 ms
cb2faa584971230ea72fc039225f07be
116 ms
3bcaa751-fd86-11e5-956f-005056a21b2a
68 ms
152 ms
xrefid.xgi
56 ms
match
13 ms
VB3bb840c4-fd86-11e5-8033-0eb5520a55dd
20 ms
tag
386 ms
tag
412 ms
149 ms
yads-iframe.html
171 ms
yads-iframe.html
308 ms
tag
401 ms
tag
385 ms
152 ms
oi
392 ms
oi
399 ms
QC_300_250.jpg
694 ms
kotaku.jp SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kotaku.jp 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 Kotaku.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.
kotaku.jp
Open Graph data is detected on the main page of Kotaku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: