54.4 sec in total
6.7 sec
47.4 sec
355 ms
Click here to check amazing 191 content for China. Otherwise, check out these important facts you probably never knew about 191.cn
191农资人网论坛频道为您提供:农药信息、农药登记、农药残留、植物保护技术、植保信息、病虫害防治、化肥行情信息、叶面肥、微肥、有机肥、植保会等交流区。
Visit 191.cnWe analyzed 191.cn page load time and found that the first response time was 6.7 sec and then it took 47.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
191.cn performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value6.0 s
13/100
25%
Value10.1 s
9/100
10%
Value40 ms
100/100
30%
Value0.191
64/100
15%
Value5.8 s
67/100
10%
6710 ms
3467 ms
2001 ms
2381 ms
1967 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 17% of them (22 requests) were addressed to the original 191.cn, 33% (42 requests) were made to Pos.baidu.com and 26% (33 requests) were made to Ubmcmm.baidustatic.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Att.191.cn.
Page size can be reduced by 543.0 kB (32%)
1.7 MB
1.1 MB
In fact, the total size of 191.cn main page is 1.7 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 77.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 77.6 kB or 79% of the original size.
Potential reduce by 97.4 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. 191 images are well optimized though.
Potential reduce by 329.8 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 329.8 kB or 67% of the original size.
Potential reduce by 38.3 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. 191.cn needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 78% of the original size.
Number of requests can be reduced by 59 (53%)
111
52
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 191. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and as a result speed up the page load time.
www.191.cn
6710 ms
pw_core.css
3467 ms
style.css
2001 ms
core.js
2381 ms
pw_ajax.js
1967 ms
jquery-1.8.2.min.js
5714 ms
m.js
842 ms
ds.js
1052 ms
jquery.tabso.bbs.js
1610 ms
global.js
1790 ms
new_userbinding.js
417 ms
jquery.2016home.js
1955 ms
zh_cn.js
1266 ms
hm.js
761 ms
20160408014204.jpg
8348 ms
indx-sprite.png
753 ms
mortx.jpg
4891 ms
nfd0.png
3315 ms
jdlogo.png
385 ms
A31.jpg
3554 ms
ebl.png
331 ms
icb.png
1041 ms
member.png
743 ms
auth.png
1099 ms
20160408092857.png
12221 ms
20160315015901.jpg
19732 ms
20160407071322.jpg
19731 ms
20160331090304.png
19732 ms
20160402045736.jpg
19732 ms
20160404085638.jpg
10073 ms
20160408023647.jpg
10946 ms
20160331055906.png
19731 ms
20160330053747.png
19731 ms
20160318013115.png
19733 ms
20160304053135.png
19733 ms
20160401072926.png
19734 ms
20160330062000.jpg
19734 ms
20160330061941.jpg
19734 ms
20160330061914.jpg
19736 ms
20160407023105.jpg
19736 ms
20160318122020.jpg
19738 ms
uctm
898 ms
hm.gif
371 ms
0f0000JeCcpJq-qBCatl10.png
1620 ms
0f000rzcP368LBovTxfur6.png
1915 ms
0f0002xZExzogiqgUBISns.png
1432 ms
0f0002xZExBogiqgUBIS5s.png
1595 ms
0f0007ZRkxXoCNWeqBwksf.png
2472 ms
0f0002xZEXzogiqgUBIScs.png
2596 ms
uctm
484 ms
barrier.js
972 ms
0f000AD9VgG5b1QDMic2D0.png
1044 ms
0f000rLa9Fl_S3Oq3o_ZQ0.png
829 ms
rm-control.gif
784 ms
show
656 ms
uctm
448 ms
uctm
894 ms
uctm
1049 ms
uctm
1271 ms
uctm
1045 ms
uctm
2285 ms
uctm
1596 ms
uctm
1565 ms
uctm
1841 ms
uctm
2088 ms
uctm
2103 ms
uctm
2120 ms
uctm
2428 ms
uctm
2422 ms
uctm
2637 ms
uctm
2646 ms
uctm
2641 ms
uctm
2712 ms
uctm
2926 ms
uctm
3153 ms
uctm
3147 ms
uctm
3141 ms
uctm
3148 ms
uctm
3142 ms
uctm
4598 ms
uctm
3636 ms
uctm
3594 ms
uctm
3662 ms
uctm
3898 ms
uctm
3655 ms
uctm
4026 ms
uctm
4100 ms
uctm
4140 ms
uctm
4177 ms
uctm
4643 ms
uctm
5616 ms
top.png
1104 ms
0f000nTu6IaUXiFfpq-CKs.png
1015 ms
uctm
4194 ms
0f000KE8OyZZYmmODqj2Es.png
772 ms
uctm
3802 ms
uctm
3765 ms
0f000QtU4NuSOVuJTOCDj6.jpg
435 ms
0f0002fFSfqZg8Qrz1__n0.png
507 ms
0f000PpQkMpIC5y4-_kMAs.png
749 ms
0f000rTh7wI_lLn97MGVS0.png
696 ms
0f000cs60mSNNBSO3ffA3s.png
721 ms
0f000ji2up3JWmRajKvIl6.png
268 ms
0f0005r4S5qpX2nnKpTjk6.png
280 ms
0f000Zt-OyeYAM-2KBdlJ0.jpg
507 ms
0f000AgvAjwE6SqZVf_sn6.png
568 ms
0f000FO50hRZeQ_DWvRezs.png
555 ms
0f000Q1WFCD7qCgM3jw0Kf.png
462 ms
0f000Kc2zRgxQw02TXNcqs.png
274 ms
0f0000I31ldu64WMMNwGQ6.png
565 ms
0f000nGEQGpkME1mdqsn3s.png
561 ms
0f000auMIQE8w9omzqY57s.png
524 ms
0f000ntnp06VmWMXmTK7j0.png
729 ms
0f000a-ouOnsf8DUOLDxt6.png
625 ms
0f000Q4BuTC-MS0-2gnMYs.png
584 ms
0f000DEpf2RmikZsJj_RSs.jpg
868 ms
0f000jPKoFmpXZZCQTCVl6.png
521 ms
0f000KTEyHkJ-ItR-xqvS6.jpg
822 ms
0f000KTEyiwJ-ItR-xqv36.jpg
722 ms
0f000Ajvf18nd0ZNL5fNts.jpg
477 ms
o.htm
2358 ms
hm.gif
15660 ms
wh.js
757 ms
ac.js
510 ms
fp.htm
860 ms
fp.htm
430 ms
191.cn accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
191.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
191.cn SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 191.cn 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 191.cn main page’s claimed encoding is gbk. 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.
191.cn
Open Graph description is not detected on the main page of 191. 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: