30.2 sec in total
1.7 sec
26.8 sec
1.6 sec
Click here to check amazing Lsns content. Otherwise, check out these important facts you probably never knew about lsns.net
【汇儿科名医·创百年和谐】广州和谐医院是按照国家三级标准建设的儿童专科,非营利性医保定点医院,专注于儿童抽动症、小儿多动症、发育迟缓等儿童发育行为疾病,健康热线:020-28102120
Visit lsns.netWe analyzed Lsns.net page load time and found that the first response time was 1.7 sec and then it took 28.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
lsns.net performance score
1729 ms
1628 ms
1233 ms
1732 ms
1283 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 94% of them (118 requests) were addressed to the original Lsns.net, 2% (3 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Img.cxmx.com.cn. The less responsive or slowest element that took the longest time to load (14.3 sec) belongs to the original domain Lsns.net.
Page size can be reduced by 453.2 kB (22%)
2.1 MB
1.6 MB
In fact, the total size of Lsns.net main page is 2.1 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 99.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 22.1 kB, which is 19% 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 99.8 kB or 88% of the original size.
Potential reduce by 152.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. Lsns images are well optimized though.
Potential reduce by 146.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 146.4 kB or 65% of the original size.
Potential reduce by 54.8 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. Lsns.net needs all CSS files to be minified and compressed as it can save up to 54.8 kB or 83% of the original size.
Number of requests can be reduced by 25 (20%)
124
99
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lsns. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
lsns.net
1729 ms
www.lsns.net
1628 ms
style.css
1233 ms
jquery-1.7.2.min.js
1732 ms
MSClass.js
1283 ms
pingbi.js
532 ms
jquery.floatDiv.js
257 ms
swt.js
537 ms
js.js
963 ms
foot_ma.png
527 ms
top_logo.jpg
797 ms
banner_yya.jpg
7278 ms
banner_yya_zjb.jpg
2544 ms
ssy.jpg
4095 ms
banner_yya_gy.jpg
6894 ms
gg_yya_zj.jpg
1637 ms
gg_yya_js.jpg
1623 ms
gg_yya_js1.jpg
2457 ms
bd.jpg
2467 ms
dt.jpg
2692 ms
gy.jpg
2702 ms
ad_huodonga.jpg
3856 ms
ad_huodong.jpg
4216 ms
gh_tp-2.jpg
3977 ms
gh_tp-2_1.jpg
6684 ms
960x100-01.jpg
7168 ms
zj_tp3_ar.jpg
4581 ms
zj_tp2_xl.jpg
4701 ms
zj_tp1.jpg
5165 ms
zj_tp4.jpg
5581 ms
zj_tp5.jpg
6053 ms
zj_tp6.jpg
6412 ms
zj_tp7.jpg
6290 ms
zj_tp8.jpg
6764 ms
kf_tp1.jpg
6654 ms
3-150912150103H8.jpg
6892 ms
3-150912151930V6.jpg
7262 ms
3-150912151U3506.jpg
7048 ms
3-150912151949132.jpg
7737 ms
2-15060F91945b6.jpg
7171 ms
2-15060F9210Q46.jpg
9143 ms
2-15060F91Z63A.jpg
12926 ms
3-150912113P24I.jpg
7744 ms
3-150912113JI50.jpg
8233 ms
index.php
713 ms
2-15060F9312U11.jpg
8832 ms
b3_pl.jpg
9289 ms
mobile.css
247 ms
jquery-1.8.2.min.js
446 ms
scroll2.js
484 ms
onclick.png
7234 ms
h.js
3707 ms
b3_pl_1.jpg
7945 ms
b3_pl_2.jpg
6927 ms
b3_pl_3.jpg
6390 ms
b3_pl01.jpg
9060 ms
b3_pl02.jpg
6647 ms
b3_pl04.jpg
6740 ms
b3_pl_5.jpg
6778 ms
b3_pl_6.jpg
5863 ms
b3_pl_7.jpg
5798 ms
b3_pl_8.jpg
6036 ms
b3_pl_9.jpg
5817 ms
b3_pl_10.jpg
8183 ms
b3_pl_11.jpg
8038 ms
21.gif
1197 ms
hm.gif
358 ms
b3_pl_12.jpg
5177 ms
b3_pl_13.jpg
4856 ms
b3_pl_14.jpg
5873 ms
b3_wypl.jpg
5292 ms
vdimgck.php
6833 ms
hm.gif
428 ms
b3_subm.jpg
5555 ms
3-15060114550bN.jpg
6300 ms
3-1506011AQ9310.jpg
8324 ms
3-1506011GH50-L.jpg
8640 ms
3-1506011H6030-L.jpg
9640 ms
3-1506011I5130-L.jpg
8527 ms
1-150601092SG04.jpg
7245 ms
6-150ZZZ012553.JPG
14334 ms
1-1506010Z023612.jpg
7948 ms
1-15060109143BO.jpg
8772 ms
1-15060109233DD.jpg
8223 ms
wx_99.png
8255 ms
nav_bg.jpg
7794 ms
bz_bg.jpg
7811 ms
bz_bg2.jpg
7646 ms
gg_bg.png
7405 ms
btn1.png
7428 ms
tab_bg.jpg
7369 ms
mt_bg2.jpg
7270 ms
mt_bg3.jpg
7056 ms
mt_bg4.jpg
7040 ms
mt_bg.jpg
7396 ms
mt_tp2.jpg
7501 ms
a1.jpg
7246 ms
a2.jpg
7199 ms
a3.jpg
7016 ms
a4.jpg
7324 ms
gh_line.jpg
6909 ms
gh_bg.jpg
6814 ms
btn2.png
5771 ms
gh_tp2.jpg
6121 ms
gh_tp21.jpg
5851 ms
gh_tp3.jpg
5301 ms
gh_tp4.jpg
4806 ms
gh_tp5.jpg
4922 ms
gh_tp6.jpg
4815 ms
zj_bg1.png
4815 ms
zj_bg2.png
4672 ms
zj_bg3.jpg
4042 ms
kf_bg1.jpg
3130 ms
kf_bg2.jpg
3295 ms
b3_tbg.png
2515 ms
b3_tit.jpg
2575 ms
b3_xxl1.png
2477 ms
b3_xxl2.png
2450 ms
b3_xxl3.png
2487 ms
b3_xxl4.png
2517 ms
xx_2.png
2600 ms
foot_bg.jpg
2491 ms
foot_bg2.jpg
2527 ms
foot_bg3.jpg
5914 ms
foot_logo.png
3862 ms
bottom.gif
2757 ms
lsns.net 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 Lsns.net 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 Lsns.net 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.
lsns.net
Open Graph description is not detected on the main page of Lsns. 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: