5.8 sec in total
887 ms
4.1 sec
839 ms
Click here to check amazing Ototsuma Officialblog content for Japan. Otherwise, check out these important facts you probably never knew about ototsuma.officialblog.jp
Visit ototsuma.officialblog.jpWe analyzed Ototsuma.officialblog.jp page load time and found that the first response time was 887 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ototsuma.officialblog.jp performance score
887 ms
455 ms
352 ms
466 ms
466 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Ototsuma.officialblog.jp, 15% (18 requests) were made to Parts.blog.livedoor.jp and 9% (11 requests) were made to Widgets.getpocket.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Livedoor.blogimg.jp.
Page size can be reduced by 314.7 kB (21%)
1.5 MB
1.2 MB
In fact, the total size of Ototsuma.officialblog.jp main page is 1.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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 92.8 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. This page needs HTML code to be minified as it can gain 18.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 92.8 kB or 86% of the original size.
Potential reduce by 26.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. Ototsuma Officialblog images are well optimized though.
Potential reduce by 142.4 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 142.4 kB or 50% of the original size.
Potential reduce by 53.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. Ototsuma.officialblog.jp needs all CSS files to be minified and compressed as it can save up to 53.4 kB or 82% of the original size.
Number of requests can be reduced by 42 (37%)
115
73
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ototsuma Officialblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ototsuma.officialblog.jp
887 ms
template.css
455 ms
site.css
352 ms
import.js
466 ms
c2.js
466 ms
smartphone.js
481 ms
ad.js
364 ms
loader_20151029.min.js
233 ms
bookmark_button.js
311 ms
widgets.js
94 ms
popular_articles_with_image_plugin.js
539 ms
adsbygoogle.js
5 ms
plugins.css
256 ms
template_6thgen.css
270 ms
jquery-1.7.1.min.js
611 ms
design.js
147 ms
ga.js
44 ms
a9881a14.png
606 ms
button-only.gif
156 ms
vqCWXYjd_400x400.jpg
135 ms
banner_22.gif
447 ms
8b2e5397.jpg
1338 ms
0c7689fa.jpg
1065 ms
82986c87.png
1238 ms
267dd7c5.jpg
1588 ms
b6521827.png
1461 ms
b9497508.jpg
1065 ms
d41c7aa2.jpg
1223 ms
ef9da035.png
2045 ms
782f26ed.png
2248 ms
4f864965.jpg
1598 ms
btn_add_twitter.png
178 ms
btn_add_facebook.png
169 ms
btn_add_line.png
187 ms
btn_add_feedly.png
176 ms
c
644 ms
__utm.gif
27 ms
collect
60 ms
275 ms
btn.js
48 ms
like.php
318 ms
icon_next.png
174 ms
icon_next_end.png
165 ms
popular_articles.json
470 ms
htmlbanner
1130 ms
like.php
301 ms
like.php
376 ms
like.php
305 ms
list.png
171 ms
ca-pub-7995775518165279.js
149 ms
zrt_lookup.html
119 ms
show_ads_impl.js
52 ms
like.php
286 ms
like.php
340 ms
jsonloader.js
165 ms
like.php
404 ms
like.php
385 ms
like.php
386 ms
like.php
375 ms
ads
317 ms
osd.js
25 ms
reset.css
16 ms
entry-button.css
17 ms
button-counter.gif
23 ms
c
437 ms
c
412 ms
c
558 ms
ads
307 ms
to_pagetop.png
227 ms
u.js
523 ms
197 ms
button
608 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
276 ms
qeKvIRsJabD.js
502 ms
LVx-xkvaJ0b.png
522 ms
button
126 ms
button
155 ms
button
153 ms
button
212 ms
button
195 ms
button
194 ms
button
209 ms
button
202 ms
button
206 ms
button
259 ms
369 ms
372 ms
460 ms
415 ms
466 ms
488 ms
486 ms
500 ms
625 ms
button.css
165 ms
shared.js
165 ms
button.js
174 ms
4419b1f4-s.jpg
1010 ms
f13e1694-s.jpg
955 ms
c76191ba-s.jpg
1109 ms
8b2e5397.jpg
890 ms
a9e0055a-s.jpg
1009 ms
m_js_controller.js
92 ms
abg.js
110 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
162 ms
pocket_button.png
34 ms
favicon
158 ms
googlelogo_color_112x36dp.png
162 ms
nessie_icon_thin_arrow_big_white.png
131 ms
s
129 ms
x_button_blue2.png
120 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
button
682 ms
jot.html
31 ms
0d.jpeg
384 ms
button_1450674110.js
71 ms
ja.png
59 ms
ja@2x.png
14 ms
ototsuma.officialblog.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ototsuma.officialblog.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 Ototsuma.officialblog.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.
ototsuma.officialblog.jp
Open Graph data is detected on the main page of Ototsuma Officialblog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: