5 sec in total
802 ms
3.7 sec
538 ms
Click here to check amazing Yondoku content for Japan. Otherwise, check out these important facts you probably never knew about yondoku.com
詳しくは投稿をご覧ください。
Visit yondoku.comWe analyzed Yondoku.com page load time and found that the first response time was 802 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
yondoku.com performance score
802 ms
174 ms
325 ms
340 ms
342 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 52% of them (65 requests) were addressed to the original Yondoku.com, 8% (10 requests) were made to I1.wp.com and 8% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Yondoku.com.
Page size can be reduced by 393.1 kB (20%)
1.9 MB
1.5 MB
In fact, the total size of Yondoku.com main page is 1.9 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.3 MB which makes up the majority of the site volume.
Potential reduce by 60.5 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 60.5 kB or 79% of the original size.
Potential reduce by 42.0 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. Yondoku images are well optimized though.
Potential reduce by 201.8 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 201.8 kB or 52% of the original size.
Potential reduce by 88.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. Yondoku.com needs all CSS files to be minified and compressed as it can save up to 88.8 kB or 81% of the original size.
Number of requests can be reduced by 36 (30%)
120
84
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yondoku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
yondoku.com
802 ms
layout.css
174 ms
general.css
325 ms
happynews.css
340 ms
flexslider.css
342 ms
wordpress.css
548 ms
jquery.js
727 ms
jquery.page-scroller.js
553 ms
smartRollover.js
558 ms
heightLine.js
561 ms
jquery.flexslider.js
584 ms
masonry.js
714 ms
jquery.infinitescroll.min.js
749 ms
common.js
325 ms
widget.css
784 ms
pagenavi-css.css
784 ms
css
26 ms
wpp.css
878 ms
jetpack.css
899 ms
lightbox.min.css
888 ms
jquery.js
1079 ms
jquery-migrate.min.js
906 ms
style.css
943 ms
analytics.js
31 ms
wp-emoji-release.min.js
273 ms
collect
12 ms
collect
65 ms
admin-ajax.php
1168 ms
logo.gif
213 ms
%E5%B3%B6%E5%BD%A9%E3%80%85.jpg
19 ms
2016%E5%B9%B402%E6%9C%8810%E6%97%A5%E5%A4%9511.jpg
23 ms
HAPPYNEWS%E3%83%BB20160217.jpg
20 ms
C2016020400000022200.jpg
19 ms
K201511180A0M406X00002_C.jpg
21 ms
%E7%84%A1%E6%96%99%E3%83%90%E3%82%B9.jpg
21 ms
2015122228.jpg
32 ms
%E9%9D%99%E5%B2%A1%E6%96%B0%E8%81%9E%E3%83%BB%E5%88%9D%E3%81%AE%E7%A7%BB%E4%BD%8F%E5%AE%B6%E6%97%8F.jpg
30 ms
%E7%A6%8F%E4%BA%95%E6%96%B0%E8%81%9E%EF%BC%91%EF%BC%92%E6%9C%88%EF%BC%92%EF%BC%94%E6%97%A5%E3%83%91%E3%83%B3%E3%83%95.jpg
37 ms
banner_shinbunkatsuyo.png
37 ms
banner_cheer.jpg
44 ms
%E3%83%8F%E3%83%83%E3%83%94%E3%83%BC%E3%83%8B%E3%83%A5%E3%83%BC%E3%82%B9IMG_1572.jpg
29 ms
%E6%96%B0%E5%85%83%E7%B4%A0.jpg
30 ms
20160107%E6%AC%BD%E3%81%A1%E3%82%83%E3%82%9314%E9%9D%A2.jpg
29 ms
banner_report.jpg
37 ms
banner_happyscrap.jpg
38 ms
2016%E5%B9%B401%E6%9C%8824%E6%97%A5%E6%9C%9D22%E7%86%8A%E6%9C%AC%E7%9C%8C%E7%89%88.jpg
35 ms
2016012226.jpg
36 ms
ufo.jpg
38 ms
kikizake.jpg
35 ms
%E3%82%B9%E3%82%B4%E3%82%A4%E3%81%AE%E3%81%AB%E5%A3%B2%E3%82%8C%E3%81%AA%E3%81%84%E3%81%8A%E3%81%98%E3%81%84%E3%81%A1%E3%82%83%E3%82%93%E3%81%AE%E3%83%8E%E3%83%BC%E3%83%88.jpg
35 ms
20160104%E4%BD%99%E9%8C%B2.jpg
35 ms
%E8%8A%A6%E5%8C%97%E3%81%8B%E3%82%89%E3%82%AB%E3%83%B3%E3%83%9C%E3%82%B8%E3%82%A2%E3%81%B8.jpg
38 ms
kyoto.jpg
41 ms
banner_2016.jpg
38 ms
sp_logo.png
333 ms
sp_menu_icon.png
446 ms
g_navi01_out.gif
206 ms
g_navi02_out.gif
207 ms
g_navi03_out.gif
206 ms
g_navi04_out.gif
331 ms
g_navi05_out.gif
448 ms
menu01_out.gif
449 ms
menu02_out.gif
442 ms
menu03_out.gif
505 ms
menu04_out.gif
507 ms
menu06_out.gif
571 ms
img_hptop.jpg
1111 ms
img_message.jpg
1023 ms
btn_archive.jpg
1022 ms
s_h2_news.png
664 ms
s_h2_img02.png
670 ms
banner_event5.jpg
1425 ms
banner_int.jpg
1332 ms
s_h2_img03.png
1021 ms
page_top.png
1111 ms
sdk.js
287 ms
widgets.js
180 ms
cse.js
17 ms
g_navi01_over.gif
1069 ms
g_navi02_over.gif
1068 ms
g_navi03_over.gif
1165 ms
g_navi04_over.gif
1201 ms
g_navi05_over.gif
1221 ms
menu_bg.gif
1226 ms
menu01_over.gif
1336 ms
menu02_over.gif
1365 ms
menu03_over.gif
1396 ms
menu04_over.gif
1402 ms
menu06_over.gif
1442 ms
h2_bg.gif
1505 ms
list_ul_bg.png
1526 ms
img_boxfooter.gif
1548 ms
noimage-b.jpg
186 ms
cse.js
183 ms
like.php
248 ms
line02.png
1423 ms
icon07.png
1447 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
215 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
263 ms
s_h2_img03.png
1496 ms
jsapi
37 ms
default+ja.css
10 ms
default.css
49 ms
default+ja.I.js
49 ms
default.css
116 ms
icon01.gif
1412 ms
132 ms
xd_arbiter.php
269 ms
xd_arbiter.php
655 ms
async-ads.js
130 ms
google_custom_search_watermark.gif
67 ms
rU2ubZ6l1Q5.js
590 ms
small-logo.png
67 ms
search_box_icon.png
67 ms
clear.gif
67 ms
nav_logo114.png
91 ms
LVx-xkvaJ0b.png
670 ms
syndication
167 ms
450141990240260096
243 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
64 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
30 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
166 ms
AC8LCTfl_normal.jpg
237 ms
jot.html
27 ms
yondoku.com SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yondoku.com 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 Yondoku.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.
yondoku.com
Open Graph data is detected on the main page of Yondoku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: