10 sec in total
1.1 sec
7.8 sec
1.1 sec
Click here to check amazing Ee Otoku content. Otherwise, check out these important facts you probably never knew about ee-otoku.com
フレッツ光にお申込み・加入でPS3 PlayStation3(プレイステーション3)・液晶テレビ無料プレゼントキャンペーン
Visit ee-otoku.comWe analyzed Ee-otoku.com page load time and found that the first response time was 1.1 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ee-otoku.com performance score
1098 ms
346 ms
377 ms
344 ms
342 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 98% of them (107 requests) were addressed to the original Ee-otoku.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Ee-otoku.com.
Page size can be reduced by 47.5 kB (8%)
612.7 kB
565.2 kB
In fact, the total size of Ee-otoku.com main page is 612.7 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. 35% of websites need less resources to load. Images take 554.3 kB which makes up the majority of the site volume.
Potential reduce by 25.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. This page needs HTML code to be minified as it can gain 5.3 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 25.3 kB or 80% of the original size.
Potential reduce by 14.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. Ee Otoku images are well optimized though.
Potential reduce by 3.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 3.0 kB or 15% of the original size.
Potential reduce by 5.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. Ee-otoku.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 86% of the original size.
Number of requests can be reduced by 12 (11%)
108
96
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ee Otoku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
ee-otoku.com
1098 ms
style.css
346 ms
java.js
377 ms
bt_top.jpg
344 ms
bt_top2.jpg
342 ms
bt_ryoukin.jpg
357 ms
bt_ryoukin2.jpg
360 ms
bt_flow.jpg
375 ms
bt_flow2.jpg
371 ms
bt_whatfree.jpg
674 ms
bt_whatfree2.jpg
690 ms
bt_qa.jpg
692 ms
bt_qa2.jpg
712 ms
bt_mail.jpg
716 ms
bt_mail2.jpg
738 ms
bt_mousikomi.gif
1038 ms
bt2_mousikomi.gif
1039 ms
bt_soudan.gif
1041 ms
bt2_soudan.gif
1054 ms
bt_kouzihimuryou.gif
1086 ms
bt_kouzihimuryou2.gif
1070 ms
bt_gettugakufree.gif
1370 ms
bt_gettugakufree2.gif
1373 ms
bt_rswc.gif
1396 ms
bt_rswc2.gif
1395 ms
bt_yobitisiki.gif
1419 ms
bt_yobitisiki2.gif
1428 ms
bt_cashback.gif
1867 ms
bt_cashback2.gif
1895 ms
bt_side_ntt_s.gif
1737 ms
bt_side_ntt_s2.gif
1742 ms
bt_side_ntt_w.gif
1754 ms
bt_side_ntt_w2.gif
1790 ms
bt_s_otoku.gif
2085 ms
bt_s_otoku2.gif
2092 ms
bt_s_mail.gif
2118 ms
bt_s_mail2.gif
2120 ms
bt_s_gaiyou.gif
2240 ms
ga.js
38 ms
bt_s_gaiyou2.gif
2095 ms
__utm.gif
13 ms
bt_s_pb.gif
2097 ms
bt_s_pb2.gif
2119 ms
back.gif
2111 ms
back.jpg
2311 ms
logo.gif
2220 ms
tel.gif
2240 ms
main-image.jpg
3105 ms
title_mottootoku.gif
2104 ms
syohin_tv.gif
2118 ms
syohin_game.gif
2223 ms
syohin_pc.gif
2261 ms
back_syohin.gif
2303 ms
icon_syoin.gif
2122 ms
bar.jpg
2123 ms
pic_getugaku.gif
2726 ms
bt_side_flets.gif
2287 ms
bt_side_ichord.gif
2338 ms
bt_side_ace.gif
2441 ms
bt_side_hikaritv.gif
2162 ms
pic_irasuto.gif
2635 ms
bar-main.jpg
2364 ms
nav01.png
2463 ms
nav02.png
2478 ms
nav03.png
2664 ms
nav04.png
2374 ms
nav05.png
2396 ms
nav06.png
2477 ms
nav46.png
2474 ms
nav07.png
2475 ms
nav08.png
2531 ms
nav09.png
2360 ms
nav10.png
2415 ms
nav11.png
2461 ms
nav12.png
2508 ms
nav13.png
2436 ms
nav14.png
2537 ms
nav15.png
2390 ms
nav16.png
2393 ms
nav17.png
2477 ms
nav18.png
2397 ms
nav19.png
2417 ms
nav20.png
2471 ms
nav21.png
2366 ms
nav22.png
2390 ms
nav23.png
2342 ms
nav24.png
2340 ms
nav25.png
2335 ms
nav26.png
2320 ms
nav27.png
2343 ms
nav28.png
2225 ms
nav29.png
2205 ms
nav30.png
2150 ms
nav31.png
2190 ms
nav32.png
2089 ms
nav33.png
2076 ms
nav34.png
2127 ms
nav35.png
2146 ms
nav36.png
2131 ms
nav37.png
2081 ms
nav38.png
2080 ms
nav39.png
2068 ms
nav47.png
2126 ms
nav40.png
2106 ms
nav45.png
2129 ms
nav41.png
2093 ms
nav42.png
2114 ms
nav43.png
2102 ms
nav44.png
2119 ms
ee-otoku.com SEO score
N/A
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ee-otoku.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 Ee-otoku.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ee-otoku.com
Open Graph description is not detected on the main page of Ee Otoku. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: