7.1 sec in total
649 ms
6.2 sec
227 ms
Welcome to loxonin.info homepage info - get ready to check Loxonin best content for Japan right away, or after learning these important things about loxonin.info
Visit loxonin.infoWe analyzed Loxonin.info page load time and found that the first response time was 649 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
loxonin.info performance score
649 ms
320 ms
329 ms
331 ms
517 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 74% of them (71 requests) were addressed to the original Loxonin.info, 19% (18 requests) were made to Medicallibrary-dsc.info and 5% (5 requests) were made to Log1.mobylog.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Loxonin.info.
Page size can be reduced by 155.9 kB (29%)
537.3 kB
381.4 kB
In fact, the total size of Loxonin.info main page is 537.3 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. 25% of websites need less resources to load. Images take 303.3 kB which makes up the majority of the site volume.
Potential reduce by 16.2 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 16.2 kB or 74% of the original size.
Potential reduce by 6.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. Loxonin images are well optimized though.
Potential reduce by 110.2 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 110.2 kB or 60% of the original size.
Potential reduce by 23.5 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. Loxonin.info needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 82% of the original size.
Number of requests can be reduced by 48 (51%)
95
47
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loxonin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
loxonin.info
649 ms
import_lox.css
320 ms
script.js
329 ms
mouseover.js
331 ms
chiphelp.js
517 ms
charset.js
344 ms
JQ.js
653 ms
SSO.js
664 ms
GA.js
656 ms
reset.css
328 ms
textsettings.css
352 ms
b_design.css
891 ms
common.css
657 ms
jquery.min1.8.3.js
1348 ms
navi_01.gif
177 ms
navi_on_01.gif
304 ms
navi_02.gif
327 ms
navi_on_02.gif
336 ms
navi_03.gif
351 ms
navi_on_03.gif
366 ms
navi_04.gif
480 ms
navi_on_04.gif
649 ms
navi_05.gif
650 ms
navi_on_05.gif
686 ms
navi_06.gif
673 ms
navi_on_06.gif
689 ms
navi_07.gif
816 ms
navi_on_07.gif
969 ms
navi_08.gif
976 ms
navi_on_08.gif
1016 ms
navi_09.gif
994 ms
navi_on_09.gif
1029 ms
navi_10.gif
1136 ms
navi_on_10.gif
1278 ms
navi_11.gif
1287 ms
navi_12.gif
1314 ms
navi_on_11.gif
1360 ms
navi_on_12.gif
1372 ms
navi_opioid.gif
1452 ms
navi_opioid_on.gif
1600 ms
navi_13.gif
1608 ms
navi_on_13.gif
1635 ms
navi_14.gif
1702 ms
navi_on_14.gif
1704 ms
bnr_dstv.jpg
1904 ms
bnr_dstv_on.jpg
2071 ms
bnr_aaos.jpg
2248 ms
bnr_aaos_on.jpg
2278 ms
bnr_alacarte.gif
2344 ms
bnr_alacarte_on.gif
2383 ms
bnr_dermatosis_winter_L.jpg
2519 ms
bnr_dermatosis_winter_L_on.jpg
2646 ms
bnr_aaos_L.jpg
2818 ms
bnr_aaos_L_on.jpg
2804 ms
ssologin_on.js
690 ms
ssologin_require.js
565 ms
500241.js
519 ms
ga.js
6 ms
__utm.gif
11 ms
_tag_mobylog.js
173 ms
xd_plugin.js
1107 ms
topframe.html
308 ms
btn_back.gif
498 ms
login_sso.css
519 ms
sso_check
594 ms
title.png
722 ms
btn_register.gif
559 ms
btn_guidance.gif
564 ms
btn_back.gif
1028 ms
cmn_logo002.png
1019 ms
cmn_logo001.gif
1020 ms
cmn_ic001.png
1077 ms
btn_login2.gif
1219 ms
btn_cancel_w180.gif
1257 ms
lox_2010_logo.gif
367 ms
daiichisankyo_logo.gif
405 ms
mainImage_top.jpg
1197 ms
navi_product.gif
617 ms
chiphelp_p01.gif
692 ms
chiphelp_p02.gif
709 ms
chiphelp_p03.gif
826 ms
navi_loxonin-video-pap.gif
829 ms
navi_content.gif
951 ms
chiphelp_c06.gif
1302 ms
chiphelp_c05.gif
1072 ms
chiphelp_c01.gif
1304 ms
chiphelp_c02.gif
1172 ms
chiphelp_p04.gif
1276 ms
bnr_mdshizai.jpg
1523 ms
index_title01.gif
1492 ms
index_title02.gif
1538 ms
login_bg001_sso.gif
448 ms
iconLinkS.gif
468 ms
xd_jquery_selectors.js
429 ms
login_sso.css
346 ms
msb.php
184 ms
loxonin.info SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loxonin.info 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 Loxonin.info 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.
loxonin.info
Open Graph description is not detected on the main page of Loxonin. 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: