Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

191.cn

论坛_191农资人 - 农技社区服务平台

Page Load Speed

54.4 sec in total

First Response

6.7 sec

Resources Loaded

47.4 sec

Page Rendered

355 ms

About Website

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.cn

Key Findings

We 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 a poor result, as 95% 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.

Performance Metrics

191.cn performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

www.191.cn

6710 ms

pw_core.css

3467 ms

style.css

2001 ms

core.js

2381 ms

pw_ajax.js

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 Optimization Overview & Recommendations

Page size can be reduced by 543.0 kB (32%)

Content Size

1.7 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 77.6 kB

  • Original 98.3 kB
  • After minification 94.6 kB
  • After compression 20.7 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.

Image Optimization

-9%

Potential reduce by 97.4 kB

  • Original 1.0 MB
  • After minification 946.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. 191 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 329.8 kB

  • Original 491.6 kB
  • After minification 463.8 kB
  • After compression 161.9 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.

CSS Optimization

-78%

Potential reduce by 38.3 kB

  • Original 48.9 kB
  • After minification 43.9 kB
  • After compression 10.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. 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.

Requests Breakdown

Number of requests can be reduced by 59 (53%)

Requests Now

111

After Optimization

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.

Accessibility Review

191.cn accessibility score

45

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

191.cn best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

191.cn SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: