4.5 sec in total
1.2 sec
3 sec
241 ms
Welcome to okimotomasakazu.com homepage info - get ready to check Okimotomasakazu best content for Japan right away, or after learning these important things about okimotomasakazu.com
もっとオモシロクいきましょうよ
Visit okimotomasakazu.comWe analyzed Okimotomasakazu.com page load time and found that the first response time was 1.2 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
okimotomasakazu.com performance score
1214 ms
334 ms
381 ms
531 ms
23 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 19% of them (17 requests) were addressed to the original Okimotomasakazu.com, 21% (19 requests) were made to Apis.google.com and 13% (12 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Infotop.jp.
Page size can be reduced by 125.9 kB (29%)
428.1 kB
302.2 kB
In fact, the total size of Okimotomasakazu.com main page is 428.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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 255.4 kB which makes up the majority of the site volume.
Potential reduce by 64.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 64.7 kB or 82% of the original size.
Potential reduce by 12.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. Okimotomasakazu images are well optimized though.
Potential reduce by 38.3 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 38.3 kB or 47% of the original size.
Potential reduce by 10.2 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. Okimotomasakazu.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 80% of the original size.
Number of requests can be reduced by 26 (32%)
82
56
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Okimotomasakazu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
okimotomasakazu.com
1214 ms
style.css
334 ms
twitter-feed.css
381 ms
click.js
531 ms
analytics.js
23 ms
sdk.js
220 ms
kei200-foot10-1-kado.gif
595 ms
s-03_125x125.jpg
215 ms
20120206162650074-150x150.jpg
216 ms
20130907190006-150x150.jpg
214 ms
6c0053e598ec3103fb6009bf49f738d7-150x150.png
920 ms
045441-3-600-150x150.jpg
474 ms
screen568x568-150x150.jpeg
474 ms
1aa0c86876dc5e2fdef9ddf89ad5743b1-150x150.png
473 ms
3ec03949d56e5a3777ecc9c44055b29c1-150x150.png
473 ms
screenshot10-150x149.png
477 ms
ScreenClip6-150x150.png
603 ms
080305_pinpon-150x150.jpg
603 ms
banner_mm.png
604 ms
banner_dogamon.png
602 ms
kei200-foot10-2-kado.gif
589 ms
banner2_61605.jpg
1328 ms
banner5_22402.gif
472 ms
widgets.js
83 ms
collect
11 ms
feed.png
617 ms
collect
74 ms
ga-audiences
152 ms
rateAndChartSide_view.pl
1174 ms
ga.js
35 ms
widget_v2.134.js
67 ms
plusone.js
212 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
330 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
424 ms
__utm.gif
197 ms
__$$__stringtable_lang_ja.js
87 ms
198 ms
xd_arbiter.php
195 ms
xd_arbiter.php
489 ms
collect
120 ms
like.php
229 ms
like.php
412 ms
cb=gapi.loaded_0
64 ms
cb=gapi.loaded_1
103 ms
fastbutton
190 ms
fastbutton
189 ms
fastbutton
187 ms
fastbutton
184 ms
fastbutton
181 ms
fastbutton
179 ms
fastbutton
371 ms
fastbutton
395 ms
fastbutton
372 ms
fastbutton
366 ms
fastbutton
370 ms
like.php
349 ms
like.php
342 ms
like.php
346 ms
like.php
367 ms
like.php
369 ms
like.php
724 ms
ga-audiences
76 ms
postmessageRelay
307 ms
like.php
613 ms
follow.php
615 ms
like.php
613 ms
rs=AGLTcCPp65oTnX7XI_ISus95mcUHkH7hXw
44 ms
kei200-top10-kado.gif
784 ms
kei200-bg10-kado.gif
784 ms
wy1X4hBW7e7.js
808 ms
LVx-xkvaJ0b.png
769 ms
syndication
631 ms
511842633933524992
639 ms
cb=gapi.loaded_0
207 ms
cb=gapi.loaded_1
210 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
538 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
526 ms
3193398744-postmessagerelay.js
409 ms
rpc:shindig_random.js
407 ms
avatar_simple_visitor.png
175 ms
qeKvIRsJabD.js
314 ms
aL63HcygAAVYuCCsAAA==
2 ms
tuuka-200.gif
294 ms
USDJPY_1_170.png
372 ms
5hun200-10.jpg
372 ms
15hun200-10h.jpg
397 ms
60hun200-10h.jpg
490 ms
cb=gapi.loaded_0
4 ms
jot.html
42 ms
okimotomasakazu.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Okimotomasakazu.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Okimotomasakazu.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.
okimotomasakazu.com
Open Graph data is detected on the main page of Okimotomasakazu. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: