56.3 sec in total
5.7 sec
50.2 sec
463 ms
Welcome to 35yao.com homepage info - get ready to check 35 Yao best content right away, or after learning these important things about 35yao.com
找药网网是医药健康产业,为医药企业优质服务,入驻热线:400-678-0778
Visit 35yao.comWe analyzed 35yao.com page load time and found that the first response time was 5.7 sec and then it took 50.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
35yao.com performance score
5692 ms
805 ms
1122 ms
1801 ms
1138 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 72% of them (108 requests) were addressed to the original 35yao.com, 12% (18 requests) were made to Qiao.baidu.com and 3% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Qiao.baidu.com.
Page size can be reduced by 302.3 kB (46%)
660.1 kB
357.8 kB
In fact, the total size of 35yao.com main page is 660.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. 35% of websites need less resources to load. Images take 305.9 kB which makes up the majority of the site volume.
Potential reduce by 54.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. 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 54.8 kB or 80% of the original size.
Potential reduce by 44.9 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. Obviously, 35 Yao needs image optimization as it can save up to 44.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 126.1 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 126.1 kB or 66% of the original size.
Potential reduce by 76.6 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. 35yao.com needs all CSS files to be minified and compressed as it can save up to 76.6 kB or 80% of the original size.
Number of requests can be reduced by 63 (44%)
142
79
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 35 Yao. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.35yao.com
5692 ms
style.css
805 ms
layout.css
1122 ms
zhaoshang.css
1801 ms
detail.css
1138 ms
jquery.js
2722 ms
index20110925_mini.js
1140 ms
jquery-hcheckbox.js
1392 ms
jquery.jqzoom.js
1702 ms
use_jqzoom.js
1634 ms
lang.js
2389 ms
config.js
1890 ms
common.js
2206 ms
page.js
2267 ms
style.js
2419 ms
A8.js
2515 ms
kefu.js
4146 ms
stat.php
1130 ms
ujian.js
597 ms
pa
20113 ms
body_bg.jpg
624 ms
head_bg_left.jpg
580 ms
head_bg_center.jpg
566 ms
zh_logo.jpg
4821 ms
fb_botton_01.jpg
1736 ms
fb_botton_02.jpg
1808 ms
15-07-30-64-365.gif
1863 ms
15-05-07-51-365.jpg
1237 ms
17-11-26-44-365.jpg
1809 ms
17-11-02-89-365.jpg
2483 ms
17-10-35-35-365.jpg
2822 ms
17-10-07-76-365.jpg
3322 ms
17-09-02-80-365.jpg
2897 ms
10-46-24-24-365.jpg
4232 ms
10-45-20-39-365.jpg
4164 ms
17-18-36-71-365.jpg
4035 ms
17-19-24-21-365.jpg
3893 ms
17-19-55-95-365.jpg
4809 ms
17-16-20-22-365.jpg
4916 ms
17-16-42-89-365.jpg
4761 ms
17-17-29-15-365.jpg
4851 ms
17-18-12-57-365.jpg
5106 ms
17-13-41-34-365.jpg
7058 ms
17-14-24-66-365.jpg
6741 ms
10-38-49-40-365.jpg
6390 ms
10-37-50-43-365.jpg
5904 ms
10-37-05-35-365.jpg
6248 ms
11-01-31-73-365.jpg
7335 ms
11-00-58-46-365.jpg
7084 ms
11-00-33-53-365.jpg
7110 ms
10-59-29-82-365.jpg
7266 ms
14-41-34-22-2394.gif
8206 ms
10-52-40-64-365.jpg
20100 ms
10-56-37-39-365.jpg
20100 ms
nopic.gif
7674 ms
15-50-19-45-1653.jpg
7394 ms
more.jpg
7779 ms
db_04.jpg
7610 ms
db_02.jpg
8951 ms
stat.htm
701 ms
core.php
1321 ms
db_03.jpg
7894 ms
db_01.jpg
7040 ms
db_06.jpg
7237 ms
db_08.jpg
8202 ms
db_07.jpg
8242 ms
db_05.jpg
7937 ms
9.gif
805 ms
pic1.gif
796 ms
h.js
2601 ms
db_12.jpg
8942 ms
db_10.jpg
8671 ms
db_11.jpg
7652 ms
app.gif
927 ms
db_09.jpg
8593 ms
gs.jpg
8043 ms
ygba.jpg
9113 ms
wj.jpg
8615 ms
btn.jpg
7886 ms
head_bg_right.jpg
8246 ms
menu_bg_left.jpg
8411 ms
menu_bg_center.jpg
8617 ms
menu_bg_li.jpg
8714 ms
shell_v2.js
576 ms
menu_hover.jpg
8848 ms
21.gif
690 ms
b.js
691 ms
hm.gif
312 ms
api.ujian.cc
727 ms
plugin.client.js
598 ms
bds_s_v2.js
323 ms
navbg.jpg
7949 ms
bdsstyle.css
352 ms
l1.gif
718 ms
bsl.js
1335 ms
menu_bg_right.jpg
7789 ms
4.png
713 ms
logger.js
354 ms
nav_bg_left.jpg
7803 ms
nav_bg_center.jpg
7680 ms
serch_botton.jpg
7412 ms
nav_bg_right.jpg
7522 ms
nav_title_bg.jpg
7805 ms
lm_bg_left.jpg
7653 ms
lm_bg_center.jpg
7743 ms
Enter.php
641 ms
main_icon_invite_mess_api.js
6450 ms
main.css
575 ms
fix.css
2599 ms
version.js
13436 ms
h1_01.jpg
8252 ms
lm_bg_right.jpg
8044 ms
li_bg.jpg
7299 ms
nav_bg_bottom.jpg
7448 ms
h1_02.jpg
7755 ms
li_bg_01.jpg
7479 ms
h1_03.jpg
7771 ms
h1_04.jpg
8740 ms
index_otcbj.gif
6680 ms
cont1234.gif
6724 ms
index_zhbj.gif
8452 ms
i_zhbg.gif
7002 ms
nav_bg.jpg
6419 ms
zs_03.jpg
6439 ms
title_02.jpg
6221 ms
li_01.jpg
6575 ms
bg.png
7540 ms
libg.jpg
6015 ms
san1.gif
6363 ms
san2.gif
6173 ms
title_01.jpg
6800 ms
li_1.jpg
6509 ms
h1_05.jpg
7873 ms
wb_35.jpg
7279 ms
m-webim-lite.css
2281 ms
m-webim-lite.js
20197 ms
Refresh.php
434 ms
12.jpg
4282 ms
12.jpg
2194 ms
09.png
1786 ms
icon.png
2324 ms
icon_close.png
4330 ms
stat.gif
2670 ms
04.png
3341 ms
mess-text.png
3029 ms
04_normal.png
3573 ms
mess.gif
5850 ms
04_send_normal.png
5762 ms
btn.png
10208 ms
Refresh.php
19733 ms
35yao.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 35yao.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 35yao.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.
35yao.com
Open Graph description is not detected on the main page of 35 Yao. 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: