8.3 sec in total
700 ms
6.3 sec
1.3 sec
Visit understanding.jp now to see the best up-to-date Understanding content and also check out these interesting facts you probably never knew about understanding.jp
『たのしいインフォグラフィック入門』著者サイト。ドラッカー著書の図解、インフォグラフィックの作り方や事例を紹介。
Visit understanding.jpWe analyzed Understanding.jp page load time and found that the first response time was 700 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
understanding.jp performance score
700 ms
1338 ms
188 ms
198 ms
385 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Understanding.jp, 49% (33 requests) were made to Visualthinking.jp and 4% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 638.1 kB (49%)
1.3 MB
674.2 kB
In fact, the total size of Understanding.jp main page is 1.3 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. 55% of websites need less resources to load. Images take 472.2 kB which makes up the majority of the site volume.
Potential reduce by 48.3 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 48.3 kB or 80% of the original size.
Potential reduce by 3.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. Understanding images are well optimized though.
Potential reduce by 299.0 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 299.0 kB or 69% of the original size.
Potential reduce by 287.4 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. Understanding.jp needs all CSS files to be minified and compressed as it can save up to 287.4 kB or 83% of the original size.
Number of requests can be reduced by 38 (61%)
62
24
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Understanding. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
understanding.jp
700 ms
www.visualthinking.jp
1338 ms
css
188 ms
twentyfifteen.css
198 ms
styles.css
385 ms
mediaelementplayer.min.css
398 ms
wp-mediaelement.css
401 ms
style.css
621 ms
genericons.css
639 ms
style.css
638 ms
wpp.css
590 ms
twentyfifteen.css
603 ms
jetpack.css
628 ms
jquery.js
1001 ms
jquery-migrate.min.js
782 ms
spin.js
799 ms
jquery.spin.js
800 ms
infinity.js
798 ms
jquery.cycle.js
808 ms
slideshow-shortcode.js
963 ms
photon.js
1135 ms
jquery.form.min.js
994 ms
scripts.js
1071 ms
devicepx-jetpack.js
63 ms
jetpack-carousel.js
1133 ms
mediaelement-and-player.min.js
1362 ms
wp-mediaelement.js
1201 ms
gprofiles.js
120 ms
wpgroho.js
1201 ms
skip-link-focus-fix.js
1199 ms
functions.js
1201 ms
wp-embed.min.js
1215 ms
e-201613.js
60 ms
wp-emoji-release.min.js
389 ms
Lingo2.jpg
150 ms
NewsPicks_jyukensapri.png
110 ms
visage5.jpg
170 ms
paypalmafia1.jpg
141 ms
catch_snapchat_infographics.png
142 ms
vt_logo_l@2x.png
361 ms
book_bnr@2x.png
937 ms
fb_button@2x.png
363 ms
tw_button@2x.png
365 ms
NewsPicks_daiwa-01.png
142 ms
NewsPicks_google.png
139 ms
widgets.js
93 ms
erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf
282 ms
PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf
377 ms
g.gif
140 ms
all.js
346 ms
ga.js
136 ms
hovercard.css
111 ms
services.css
114 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
199 ms
__utm.gif
18 ms
collect
159 ms
follow_button.64a917b4a230f163048902c783e1530f.ja.html
37 ms
269 ms
jot
250 ms
xd_arbiter.php
354 ms
xd_arbiter.php
657 ms
xd_arbiter.php
176 ms
like.php
71 ms
like.php
101 ms
ZJkxn0orVLU.js
802 ms
LVx-xkvaJ0b.png
895 ms
ZJkxn0orVLU.js
1788 ms
understanding.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Understanding.jp 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 Understanding.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.
understanding.jp
Open Graph data is detected on the main page of Understanding. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: