Tools & Wizards About Us
we.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

we.com

页面不存在

Page Load Speed

78.1 sec in total

First Response

1 sec

Resources Loaded

76.7 sec

Page Rendered

368 ms

we.com screenshot

About Website

Click here to check amazing We content for Egypt. Otherwise, check out these important facts you probably never knew about we.com

Wealth Evolution( www.we.com) (简称人人贷WE理财)是人人贷公司旗下的理财品牌。人人贷WE理财作为原人人贷平台(www.renrendai.com)理财端的升级，为广大理财用户提供更多元的投资选择与更优质的综合理财服务。投资理财用户可通过WE官方网站进行散标投资、加入U计划、薪计划、购买债权转让等方式进行投资获得稳定收益。

Visit we.com

Key Findings

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

Performance Metrics

we.com performance score

0

Network Requests Diagram

we.com

1031 ms

www.we.com

7192 ms

base_4c6d945.css

15568 ms

video-js_f377876.css

1084 ms

vendors_8a6040f.js

2757 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 94% of them (44 requests) were addressed to the original We.com, 6% (3 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 We.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.0 kB (71%)

Content Size

95.8 kB

After Optimization

27.8 kB

  • HTML

In fact, the total size of We.com main page is 95.8 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. 30% of websites need less resources to load. HTML takes 95.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 68.0 kB

  • Original 95.8 kB
  • After minification 84.6 kB
  • After compression 27.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 11.2 kB, which is 12% 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 68.0 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

39

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

we.com

we.com

1031 ms

www.we.com

www.we.com

7192 ms

base_4c6d945.css

base_4c6d945.css

15568 ms

video-js_f377876.css

video-js_f377876.css

1084 ms

vendors_8a6040f.js

vendors_8a6040f.js

2757 ms

video_41dc322.js

video_41dc322.js

2133 ms

common_widget_a1e249e.css

common_widget_a1e249e.css

3362 ms

home_widget_c5b638f.css

home_widget_c5b638f.css

3624 ms

invest_widget_c55c581.css

invest_widget_c55c581.css

4315 ms

index_358777c.css

index_358777c.css

2549 ms

require_2f19223.js

require_2f19223.js

1047 ms

common_widget_8e0233d.js

common_widget_8e0233d.js

18880 ms

home_widget_a8e3652.js

home_widget_a8e3652.js

1473 ms

index_9c382c0.js

index_9c382c0.js

1910 ms

we-logo_79fb26f.png

we-logo_79fb26f.png

2969 ms

weixin_l.jpg

weixin_l.jpg

2673 ms

we-weixing_334069c.png

we-weixing_334069c.png

3593 ms

app-weixin_32107fa.png

app-weixin_32107fa.png

421 ms

loading.gif

loading.gif

1971 ms

6d405bc3-25af-45b7-9eb6-8ef005577f25.jpg

6d405bc3-25af-45b7-9eb6-8ef005577f25.jpg

5396 ms

a312150a-31e0-4f26-8d01-0dcdf596d01c.jpg

a312150a-31e0-4f26-8d01-0dcdf596d01c.jpg

19709 ms

19addf8c-8893-45f1-b5d4-ccb891aa9c81.jpg

19addf8c-8893-45f1-b5d4-ccb891aa9c81.jpg

14135 ms

35acd6fe-eace-4dcd-ac97-99338c6166dd.jpg

35acd6fe-eace-4dcd-ac97-99338c6166dd.jpg

19710 ms

9cfafc23-00da-47da-bb89-9ade4c2b7b5e.jpg

9cfafc23-00da-47da-bb89-9ade4c2b7b5e.jpg

14351 ms

4c2f6e4f-3097-4bef-8e13-bdd98e0a9378.png

4c2f6e4f-3097-4bef-8e13-bdd98e0a9378.png

12312 ms

24956745-7cf7-4227-9ad8-9595ea6d2681.jpg

24956745-7cf7-4227-9ad8-9595ea6d2681.jpg

8265 ms

d183f882-423d-45c6-a968-0e1817cb294e.jpg

d183f882-423d-45c6-a968-0e1817cb294e.jpg

10785 ms

icon_4538046.png

icon_4538046.png

11208 ms

index-newbee_c8a8f93.png

index-newbee_c8a8f93.png

12262 ms

index-fund_31cc444.png

index-fund_31cc444.png

12684 ms

index-uplan_6f5d126.png

index-uplan_6f5d126.png

12763 ms

index-fixed-plan_20bce3c.png

index-fixed-plan_20bce3c.png

13104 ms

index-loan-list_f46f84d.png

index-loan-list_f46f84d.png

13222 ms

icon-snow_736f306.png

icon-snow_736f306.png

13461 ms

footer-icons_4cd624d.png

footer-icons_4cd624d.png

16674 ms

footer-icons.png

footer-icons.png

15565 ms

icomoon_b8f3270.ttf

icomoon_b8f3270.ttf

14981 ms

helveticaneuelt_19059dc.woff

helveticaneuelt_19059dc.woff

17476 ms

hm.js

hm.js

724 ms

hm.gif

hm.gif

764 ms

loading-icon_c721125.gif

loading-icon_c721125.gif

11262 ms

order_01.png

order_01.png

10726 ms

order_05.png

order_05.png

11146 ms

loantypes_be5510f.png

loantypes_be5510f.png

11569 ms

a312150a-31e0-4f26-8d01-0dcdf596d01c.jpg

a312150a-31e0-4f26-8d01-0dcdf596d01c.jpg

19969 ms

hm.gif

hm.gif

2106 ms

35acd6fe-eace-4dcd-ac97-99338c6166dd.jpg

35acd6fe-eace-4dcd-ac97-99338c6166dd.jpg

19969 ms

SEO Factors

we.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise We.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that We.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

we.com

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