4.1 sec in total
662 ms
3.2 sec
274 ms
Click here to check amazing WHO DID IT content for Japan. Otherwise, check out these important facts you probably never knew about whodidit.jp
Who did it? Who did that creative project?
Visit whodidit.jpWe analyzed Whodidit.jp page load time and found that the first response time was 662 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whodidit.jp performance score
662 ms
320 ms
7 ms
726 ms
332 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 36% of them (54 requests) were addressed to the original Whodidit.jp, 26% (40 requests) were made to O.twimg.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Whodidit.jp.
Page size can be reduced by 848.6 kB (19%)
4.5 MB
3.6 MB
In fact, the total size of Whodidit.jp main page is 4.5 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 112.2 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 112.2 kB or 81% of the original size.
Potential reduce by 505.6 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, WHO DID IT needs image optimization as it can save up to 505.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 174.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 174.1 kB or 52% of the original size.
Potential reduce by 56.8 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. Whodidit.jp needs all CSS files to be minified and compressed as it can save up to 56.8 kB or 86% of the original size.
Number of requests can be reduced by 71 (47%)
151
80
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHO DID IT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
whodidit.jp
662 ms
style.css
320 ms
adsbygoogle.js
7 ms
jquery.min.js
726 ms
main.js
332 ms
bookmark_button.js
531 ms
pinit.js
4 ms
wp-emoji-release.min.js
367 ms
322 ms
logo.gif
318 ms
btn_idi.gif
322 ms
btn_search.gif
334 ms
separator.gif
333 ms
t_thumb_160314_01_01.jpg
804 ms
icn_category_graphic.gif
469 ms
icn_new_window.gif
826 ms
index_tx_views.gif
512 ms
t_thumb_160208_01.jpg
1102 ms
icn_category_web.gif
803 ms
t_thumb_160205_01.png
1175 ms
icn_category_pv.gif
803 ms
icn_category_other.gif
947 ms
t_thumb_161119_01_01.jpg
947 ms
icn_day.png
945 ms
t_thumb_160112.jpg
999 ms
icn_category_mobile.gif
1069 ms
t_thumb_160104_01.jpg
1234 ms
t_thumb_151204_01_01.png
1274 ms
t_thumb_151130_011.jpg
1148 ms
t_thumb_151130_01.jpg
1369 ms
t_thumb_151129_01_01.jpg
1972 ms
t_thumb_151125_01.jpg
1482 ms
t_thumb_151028_01.jpg
1342 ms
t_thumb_151015_01_01.jpg
1562 ms
t_thumb_151009_01.jpg
1618 ms
t_thumb_151008_01.jpg
1667 ms
t_thumb_151006_01_01.jpg
1833 ms
dot_line_1.gif
1625 ms
topic_ad_it.gif
1712 ms
ca-pub-2352812480475924.js
267 ms
zrt_lookup.html
53 ms
show_ads_impl.js
54 ms
topic_diders.gif
1723 ms
icn_square.gif
1715 ms
topic_resent_entries.gif
1758 ms
all.js
167 ms
topic_archives.gif
1769 ms
ads
628 ms
osd.js
32 ms
ads
251 ms
copyright.gif
1645 ms
32 ms
xd_arbiter.php
132 ms
xd_arbiter.php
469 ms
701574646078936886
65 ms
abg.js
30 ms
m_js_controller.js
27 ms
googlelogo_color_112x36dp.png
61 ms
s
27 ms
redir.html
321 ms
x_button_blue2.png
209 ms
widgets.js
370 ms
plusone.js
419 ms
btn.js
312 ms
ga.js
296 ms
btn_ydi.gif
1264 ms
index_tx_cl.gif
1276 ms
index_tx_ag.gif
1291 ms
index_tx_pd.gif
1332 ms
index_tx_cd.gif
1408 ms
index_tx_ad.gif
1440 ms
index_tx_pl.gif
1441 ms
pinit_main.js
105 ms
8076383889473585579
61 ms
index_tx_pr.gif
1342 ms
index_tx_c.gif
1367 ms
index_tx_d.gif
1406 ms
like_box.php
346 ms
iframe.html
80 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
32 ms
inpage_linkid.js
57 ms
index_tx_de.gif
1444 ms
__utm.gif
33 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
138 ms
index_tx_pg.gif
1351 ms
index_tx_ot.gif
1381 ms
index_tx_aw.gif
1383 ms
cb=gapi.loaded_0
16 ms
syndication
119 ms
277991659164278785
224 ms
hQThvcX2PmE.css
165 ms
fhXOZkY3D9G.css
216 ms
FAHeNGXgPup.js
321 ms
ehA1CqzHyzE.js
364 ms
0wM5s1Khldu.js
319 ms
1bNoFZUdlYZ.js
320 ms
proxy.jpg
51 ms
proxy.jpg
48 ms
proxy.jpg
45 ms
proxy.jpg
44 ms
proxy.jpg
43 ms
proxy.jpg
45 ms
proxy.jpg
90 ms
proxy.jpg
52 ms
proxy.jpg
53 ms
proxy.jpg
51 ms
proxy.jpg
50 ms
proxy.jpg
51 ms
proxy.jpg
69 ms
proxy.jpg
69 ms
proxy.jpg
61 ms
proxy.jpg
69 ms
proxy.jpg
70 ms
proxy.jpg
87 ms
proxy.jpg
87 ms
proxy.jpg
86 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
66 ms
wdi_twitter_icon_normal.jpg
242 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
48 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
53 ms
proxy.jpg
4 ms
429497_403159029701106_176317917_n.jpg
181 ms
249539_229540240396320_247190_n.jpg
221 ms
484697_4523851939375_1134432406_n.jpg
270 ms
10620775_10205026773494954_6325622459297737226_n.jpg
294 ms
424639_179476515550421_209011797_n.jpg
295 ms
10414502_582728501872296_4568680130840656633_n.jpg
301 ms
wL6VQj7Ab77.png
48 ms
s7jcwEQH7Sx.png
47 ms
proxy.jpg
14 ms
proxy.jpg
8 ms
proxy.jpg
5 ms
proxy.jpg
3 ms
proxy.jpg
7 ms
proxy.jpg
12 ms
proxy.jpg
7 ms
proxy.jpg
4 ms
proxy.jpg
3 ms
proxy.jpg
5 ms
proxy.jpg
3 ms
proxy.jpg
4 ms
proxy.jpg
7 ms
proxy.jpg
6 ms
proxy.jpg
4 ms
proxy.jpg
8 ms
proxy.jpg
9 ms
proxy.jpg
14 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
78 ms
proxy.jpg
13 ms
activeview
17 ms
whodidit.jp SEO score
![]()
EN
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whodidit.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Whodidit.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.
whodidit.jp
Open Graph data is detected on the main page of WHO DID IT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: