7.1 sec in total
651 ms
6.2 sec
263 ms
Click here to check amazing Eyebon content. Otherwise, check out these important facts you probably never knew about eyebon.jp
あなたの健康な瞳のために。アイボンは、洗眼薬のパイオニアです。
Visit eyebon.jpWe analyzed Eyebon.jp page load time and found that the first response time was 651 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eyebon.jp performance score
651 ms
944 ms
309 ms
478 ms
321 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eyebon.jp, 56% (59 requests) were made to Kobayashi.co.jp and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Kobayashi.co.jp.
Page size can be reduced by 185.6 kB (16%)
1.2 MB
974.3 kB
In fact, the total size of Eyebon.jp main page is 1.2 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 884.7 kB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 73% of the original size.
Potential reduce by 45.7 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. Eyebon images are well optimized though.
Potential reduce by 113.6 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 113.6 kB or 47% of the original size.
Potential reduce by 5.7 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. Eyebon.jp needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 73% of the original size.
Number of requests can be reduced by 36 (37%)
97
61
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyebon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
eyebon.jp
651 ms
944 ms
default.css
309 ms
base.css
478 ms
top.css
321 ms
jquery.min.js
1428 ms
socialbutton.js
359 ms
rollover.js
459 ms
script.js
479 ms
jquery.min.js
42 ms
tool.js
537 ms
share.js
293 ms
jquery-cookie.js
293 ms
169 ms
188 ms
cmn_company_logo.gif
194 ms
logo.png
173 ms
sub_gnav_product.png
167 ms
sub_gnav_qa.png
194 ms
gnav01.png
170 ms
gnav02.png
192 ms
gnav02_sub01.png
309 ms
gnav02_sub02.png
333 ms
gnav02_sub03.png
331 ms
gnav02_sub04.png
363 ms
gnav03.png
365 ms
gnav06.png
364 ms
gnav05.png
460 ms
top_catch.png
650 ms
top_pkg01.png
1163 ms
top_pkg02.png
1248 ms
top_pkg03.png
1255 ms
top_pkg04.png
725 ms
top_pkg05.png
1372 ms
top_pkg06.png
1323 ms
top_pkg07.png
1084 ms
top_bnr01.jpg
1263 ms
cmn_foot_company_logo.gif
1322 ms
cmn_foot_txt.gif
1425 ms
cmn_foot_list01.gif
1432 ms
cmn_foot_list02.gif
1443 ms
cmn_foot_list03.gif
1482 ms
cmn_foot_list04.gif
1481 ms
cmn_foot_list05.gif
1523 ms
cmn_foot_list06.gif
1601 ms
cmn_foot_list07.gif
1610 ms
cmn_foot_list08.gif
1620 ms
cmn_foot_list09.gif
1642 ms
cmn_foot_list10.gif
1642 ms
cmn_foot_list11.gif
1675 ms
widgets.js
140 ms
cmn_foot_list12.gif
1772 ms
plusone.js
69 ms
btn_share_now.png
222 ms
share_button.html
312 ms
ga.js
22 ms
like.php
111 ms
tag.js
22 ms
mone.4b0faeb6979_1294.js
423 ms
__utm.gif
22 ms
cb=gapi.loaded_0
10 ms
cb=gapi.loaded_1
33 ms
fastbutton
87 ms
tag
35 ms
postmessageRelay
61 ms
TY3MhkXpWJ-.js
60 ms
LVx-xkvaJ0b.png
49 ms
cmn_address.gif
1630 ms
bg_top.jpg
2175 ms
cmn_foot_arow.gif
1639 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
21 ms
3193398744-postmessagerelay.js
16 ms
rpc:shindig_random.js
26 ms
cb=gapi.loaded_0
3 ms
bt_check_1.png
6 ms
kobayashi.js
72 ms
ya.js
309 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
137 ms
popin_discovery5-min.js
58 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
combo
184 ms
149 ms
jot
76 ms
pb.js
530 ms
333 ms
lognos.js
351 ms
pb.html
4 ms
pixel
15 ms
302 ms
602 ms
pixel
14 ms
149 ms
pixel
15 ms
150 ms
utm.png
90 ms
gnav01_o.png
180 ms
rep
148 ms
gnav02_o.png
321 ms
gnav02_sub02_o.png
156 ms
gnav02_sub03_o.png
182 ms
gnav02_sub04_o.png
163 ms
gnav03_o.png
182 ms
gnav06_o.png
307 ms
gnav05_o.png
322 ms
eyebon.jp SEO score
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyebon.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 Eyebon.jp 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.
eyebon.jp
Open Graph description is not detected on the main page of Eyebon. 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: