Tools & Wizards About Us
ruilve.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ruilve.com

瑞略资讯网

Page Load Speed

55 sec in total

First Response

2.3 sec

Resources Loaded

52.5 sec

Page Rendered

196 ms

ruilve.com screenshot

About Website

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

瑞略资讯网是中国证监会指定的上市公司信息披露网站,平台提供上市公司公告、公司资讯、公司互动、股东大会网络投票等内容功能,一站式服务资本市场投资者。

Visit ruilve.com

Key Findings

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

Performance Metrics

ruilve.com performance score

0

Network Requests Diagram

ruilve.com

2265 ms

css.css

1427 ms

jquery1.42.min.js

1546 ms

jquery.SuperSlide.2.1.1.js

1126 ms

dbj.jpg

775 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 47% of them (29 requests) were addressed to the original Ruilve.com, 15% (9 requests) were made to Qiao.baidu.com and 6% (4 requests) were made to Skin.54kefu.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Lxbjs.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.1 kB (19%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ruilve.com main page is 1.5 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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 20.6 kB

  • Original 28.3 kB
  • After minification 26.5 kB
  • After compression 7.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 20.6 kB or 73% of the original size.

Image Optimization

-12%

Potential reduce by 150.8 kB

  • Original 1.3 MB
  • After minification 1.1 MB

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, Ruilve needs image optimization as it can save up to 150.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 63.6 kB

  • Original 97.3 kB
  • After minification 97.2 kB
  • After compression 33.7 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 63.6 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 40.0 kB

  • Original 48.1 kB
  • After minification 36.7 kB
  • After compression 8.1 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. Ruilve.com needs all CSS files to be minified and compressed as it can save up to 40.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (41%)

Requests Now

58

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ruilve.com

ruilve.com

2265 ms

css.css

css.css

1427 ms

jquery1.42.min.js

jquery1.42.min.js

1546 ms

jquery.SuperSlide.2.1.1.js

jquery.SuperSlide.2.1.1.js

1126 ms

dbj.jpg

dbj.jpg

775 ms

mabj.jpg

mabj.jpg

2518 ms

logo.jpg

logo.jpg

1380 ms

letter.jpg

letter.jpg

746 ms

tel.jpg

tel.jpg

1004 ms

nav_bj.jpg

nav_bj.jpg

1251 ms

nav_gx.jpg

nav_gx.jpg

1423 ms

banner01.jpg

banner01.jpg

2182 ms

banner02.jpg

banner02.jpg

3389 ms

banner03.jpg

banner03.jpg

3185 ms

banner04.jpg

banner04.jpg

3323 ms

zx01.jpg

zx01.jpg

2297 ms

xiangxi.png

xiangxi.png

2526 ms

zx02.jpg

zx02.jpg

2873 ms

zx03.jpg

zx03.jpg

3184 ms

zx04.jpg

zx04.jpg

3405 ms

grow1.jpg

grow1.jpg

3340 ms

red.png

red.png

3552 ms

zx05.jpg

zx05.jpg

3858 ms

grow2.jpg

grow2.jpg

3818 ms

green.png

green.png

3583 ms

zx06.jpg

zx06.jpg

3900 ms

link_bj.jpg

link_bj.jpg

3853 ms

dihang_gx.jpg

dihang_gx.jpg

3883 ms

gs.png

gs.png

3933 ms

stat.php

stat.php

2717 ms

stat.htm

stat.htm

612 ms

core.php

core.php

1060 ms

9.gif

9.gif

1126 ms

pic.gif

pic.gif

567 ms

652447.js

652447.js

830 ms

getonline

getonline

15528 ms

url.js

url.js

721 ms

652447_code.js

652447_code.js

884 ms

app.gif

app.gif

878 ms

skin.css

skin.css

832 ms

top.gif

top.gif

5376 ms

bottom.gif

bottom.gif

1243 ms

h.js

h.js

1317 ms

r.gif

r.gif

872 ms

21.gif

21.gif

757 ms

lxb.js

lxb.js

19744 ms

b.js

b.js

715 ms

hm.gif

hm.gif

441 ms

bsl.js

bsl.js

2793 ms

Enter.php

Enter.php

3299 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

8383 ms

main.css

main.css

3740 ms

fix.css

fix.css

993 ms

version.js

version.js

900 ms

button_old_11.gif

button_old_11.gif

467 ms

12.png

12.png

14961 ms

m-webim-lite.css

m-webim-lite.css

534 ms

m-webim-lite.js

m-webim-lite.js

1792 ms

Refresh.php

Refresh.php

6053 ms

stat.gif

stat.gif

2394 ms

0.png

0.png

4994 ms

Refresh.php

Refresh.php

421 ms

SEO Factors

ruilve.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 Ruilve.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 Ruilve.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

ruilve.com

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