Tools & Wizards About Us
runhesh.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

runhesh.com

灌溉网|雾喷|微喷|滴灌设备生产商|上海润禾节水灌溉技术有限公司

Page Load Speed

37.8 sec in total

First Response

5.5 sec

Resources Loaded

31.9 sec

Page Rendered

281 ms

runhesh.com screenshot

About Website

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

Visit runhesh.com

Key Findings

We analyzed Runhesh.com page load time and found that the first response time was 5.5 sec and then it took 32.2 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

runhesh.com performance score

0

Network Requests Diagram

runhesh.com

5527 ms

css.css

895 ms

css03.js

894 ms

piao.js

937 ms

css01.js

1066 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 62% of them (40 requests) were addressed to the original Runhesh.com, 26% (17 requests) were made to Sysimages.tq.cn and 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Runhesh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.4 kB (52%)

Content Size

201.3 kB

After Optimization

96.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Runhesh.com main page is 201.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. 25% of websites need less resources to load. Javascripts take 98.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.8 kB

  • Original 18.8 kB
  • After minification 18.2 kB
  • After compression 4.9 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 13.8 kB or 74% of the original size.

Image Optimization

-11%

Potential reduce by 8.1 kB

  • Original 75.7 kB
  • After minification 67.6 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, Runhesh needs image optimization as it can save up to 8.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 75.8 kB

  • Original 98.2 kB
  • After minification 97.7 kB
  • After compression 22.5 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 75.8 kB or 77% of the original size.

CSS Optimization

-78%

Potential reduce by 6.6 kB

  • Original 8.6 kB
  • After minification 7.7 kB
  • After compression 1.9 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. Runhesh.com needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

62

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

runhesh.com

runhesh.com

5527 ms

css.css

css.css

895 ms

css03.js

css03.js

894 ms

piao.js

piao.js

937 ms

css01.js

css01.js

1066 ms

css02.js

css02.js

1118 ms

floatcard

floatcard

4149 ms

index_top_2.jpg

index_top_2.jpg

6959 ms

index_top_menu_1.jpg

index_top_menu_1.jpg

427 ms

index_top_menu_2.jpg

index_top_menu_2.jpg

3816 ms

index_top_menu_3.jpg

index_top_menu_3.jpg

2020 ms

index_top_menu_4.jpg

index_top_menu_4.jpg

753 ms

index_top_menu_5.jpg

index_top_menu_5.jpg

877 ms

index_top_menu_6.jpg

index_top_menu_6.jpg

5103 ms

index_top_menu_7.jpg

index_top_menu_7.jpg

1373 ms

index_top_5_2.jpg

index_top_5_2.jpg

1836 ms

index_top_5_4.jpg

index_top_5_4.jpg

2286 ms

search_btn.jpg

search_btn.jpg

2546 ms

index_top_5_7.jpg

index_top_5_7.jpg

2695 ms

index_main_1.jpg

index_main_1.jpg

4696 ms

NewProduct_1.jpg

NewProduct_1.jpg

3522 ms

new_product_3_1.gif

new_product_3_1.gif

3096 ms

new_product_3_2.gif

new_product_3_2.gif

3493 ms

new_product_3_3.gif

new_product_3_3.gif

5906 ms

new_product_3_4.gif

new_product_3_4.gif

4008 ms

new_product_3_5.gif

new_product_3_5.gif

5643 ms

new_product_3_6.gif

new_product_3_6.gif

5841 ms

index_main_4.jpg

index_main_4.jpg

5148 ms

index_main_5.jpg

index_main_5.jpg

12730 ms

index_main_8.jpg

index_main_8.jpg

7682 ms

index_main_10.jpg

index_main_10.jpg

8600 ms

index_04.jpg

index_04.jpg

20036 ms

index_5_1.gif

index_5_1.gif

6362 ms

index_5_3.gif

index_5_3.gif

9198 ms

index_6_1.jpg

index_6_1.jpg

7412 ms

index_6_2.jpg

index_6_2.jpg

9124 ms

index_6_3.jpg

index_6_3.jpg

9568 ms

index_6_4.jpg

index_6_4.jpg

10591 ms

index_6_5.jpg

index_6_5.jpg

9586 ms

index_top_1.jpg

index_top_1.jpg

12850 ms

index_02.jpg

index_02.jpg

19816 ms

all_20100501.js

all_20100501.js

2050 ms

as.js

as.js

772 ms

style.css

style.css

1199 ms

style.css

style.css

1197 ms

float.js

float.js

1819 ms

invite.js

invite.js

2725 ms

h.js

h.js

1436 ms

icooff.gif

icooff.gif

651 ms

off.gif

off.gif

2931 ms

down.gif

down.gif

2504 ms

btm.gif

btm.gif

1389 ms

head.gif

head.gif

760 ms

body.gif

body.gif

1021 ms

21.gif

21.gif

1883 ms

b.js

b.js

1117 ms

hm.gif

hm.gif

415 ms

bg_c1.png

bg_c1.png

4693 ms

accept_c1.png

accept_c1.png

1126 ms

message_c1.png

message_c1.png

1282 ms

call_c1.png

call_c1.png

1732 ms

refuse_c1.png

refuse_c1.png

1872 ms

bw.js

bw.js

2836 ms

bw.css

bw.css

13587 ms

scriptonline.js

scriptonline.js

1384 ms

SEO Factors

runhesh.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runhesh.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 Runhesh.com main page’s claimed encoding is gb2312. 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

runhesh.com

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