Tools & Wizards About Us
yinongdai.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yinongdai.com

宜农贷-爱心公益_慈善活动_扶贫助农献爱心_公益助农项目

Page Load Speed

20.8 sec in total

First Response

2.3 sec

Resources Loaded

18.2 sec

Page Rendered

296 ms

yinongdai.com screenshot

About Website

Visit yinongdai.com now to see the best up-to-date Yinongdai content and also check out these interesting facts you probably never knew about yinongdai.com

宜农贷是针对农村贫困妇女发起的公益性小额信用借款助农项目,通过宜农贷公益助农项目,有爱心的人可直接帮助贫困地区的农村借款人,爱心助农扶贫就上宜农贷!

Visit yinongdai.com

Key Findings

We analyzed Yinongdai.com page load time and found that the first response time was 2.3 sec and then it took 18.5 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.

Performance Metrics

yinongdai.com performance score

0

Network Requests Diagram

yinongdai.com

2300 ms

www.yinongdai.com

1703 ms

common.css

719 ms

common-ui.css

733 ms

doyoo.css

1064 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 85% of them (71 requests) were addressed to the original Yinongdai.com, 6% (5 requests) were made to Assets.yinongdai.com and 2% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Yinongdai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.5 kB (50%)

Content Size

253.3 kB

After Optimization

126.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yinongdai.com main page is 253.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. 35% of websites need less resources to load. Images take 107.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 63.8 kB

  • Original 76.6 kB
  • After minification 66.4 kB
  • After compression 12.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 10.2 kB, which is 13% 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 63.8 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 10.7 kB

  • Original 107.9 kB
  • After minification 97.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. Yinongdai images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 19.9 kB

  • Original 31.4 kB
  • After minification 31.4 kB
  • After compression 11.6 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 19.9 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 32.1 kB

  • Original 37.4 kB
  • After minification 24.1 kB
  • After compression 5.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. Yinongdai.com needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (39%)

Requests Now

79

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yinongdai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yinongdai.com

yinongdai.com

2300 ms

www.yinongdai.com

www.yinongdai.com

1703 ms

common.css

common.css

719 ms

common-ui.css

common-ui.css

733 ms

doyoo.css

doyoo.css

1064 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

2150 ms

main.js

main.js

1104 ms

jquery.ajaxSetup.js

jquery.ajaxSetup.js

749 ms

index.css

index.css

737 ms

notice.css

notice.css

1062 ms

video-js.css

video-js.css

1075 ms

video.js

video.js

3719 ms

purl.js

purl.js

1075 ms

jquery.numeric.js

jquery.numeric.js

1439 ms

listLoan.js

listLoan.js

1105 ms

jquery.cookie-1.4.1.js

jquery.cookie-1.4.1.js

1418 ms

commheader.js

commheader.js

1431 ms

116794.js

116794.js

930 ms

seallogo.dll

seallogo.dll

618 ms

memberCenter.css

memberCenter.css

1116 ms

jquery.token.js

jquery.token.js

1115 ms

icon_helpCard2.png

icon_helpCard2.png

404 ms

logo_slogan.png

logo_slogan.png

402 ms

scroll_bg.png

scroll_bg.png

416 ms

leave.gif

leave.gif

407 ms

inline

inline

1259 ms

inline

inline

816 ms

inline

inline

1237 ms

inline

inline

6181 ms

inline

inline

1686 ms

inline

inline

1258 ms

inline

inline

6171 ms

inline

inline

2067 ms

inline

inline

2114 ms

one_click.gif

one_click.gif

6173 ms

inline

inline

2111 ms

inline

inline

6169 ms

inline

inline

6170 ms

inline

inline

6178 ms

inline

inline

6173 ms

inline

inline

6170 ms

inline

inline

6175 ms

inline

inline

6176 ms

inline

inline

6172 ms

inline

inline

6173 ms

inline

inline

6183 ms

img0018.png

img0018.png

6176 ms

img01018.png

img01018.png

6177 ms

captcha1.png

captcha1.png

6179 ms

captcha2.png

captcha2.png

6184 ms

index_f2.gif

index_f2.gif

6185 ms

yndspfm.jpg

yndspfm.jpg

825 ms

icon_phone.png

icon_phone.png

6180 ms

icon_helpCard.gif

icon_helpCard.gif

6174 ms

icon_buyCar.gif

icon_buyCar.gif

6176 ms

icon_buyNum.gif

icon_buyNum.gif

6177 ms

hm.js

hm.js

6158 ms

looyu.css

looyu.css

653 ms

looyu.js

looyu.js

2345 ms

index_dot.png

index_dot.png

3798 ms

banner_bottom_left.gif

banner_bottom_left.gif

3799 ms

banner_bottom_right.gif

banner_bottom_right.gif

3800 ms

brand1.gif

brand1.gif

3801 ms

brand2.gif

brand2.gif

4498 ms

brand3.gif

brand3.gif

3802 ms

f_shopcart_1.jpg

f_shopcart_1.jpg

3803 ms

dian.gif

dian.gif

3820 ms

icon_top1.gif

icon_top1.gif

4556 ms

icon_num2.gif

icon_num2.gif

3838 ms

icon_num3.gif

icon_num3.gif

3952 ms

icon_num4.gif

icon_num4.gif

4177 ms

icon_num5.gif

icon_num5.gif

4194 ms

footer_top.gif

footer_top.gif

4236 ms

cnnic_en.png

cnnic_en.png

3745 ms

banner56_bg.jpg

banner56_bg.jpg

2198 ms

s

s

2254 ms

fontello.woff

fontello.woff

603 ms

index_custom.png

index_custom.png

833 ms

dialogYND_bg.png

dialogYND_bg.png

838 ms

gotop.gif

gotop.gif

1896 ms

customerService.gif

customerService.gif

1008 ms

index_btn.gif

index_btn.gif

1125 ms

index_dotCur.png

index_dotCur.png

4641 ms

hm.gif

hm.gif

2053 ms

SEO Factors

yinongdai.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yinongdai.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 Yinongdai.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.

Social Sharing Optimization

yinongdai.com

Open Graph description is not detected on the main page of Yinongdai. 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: