Tools & Wizards About Us
wecash.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wecash.net

Wecash - 一家基于B2B2C模式的新型科技平台

Page Load Speed

17.7 sec in total

First Response

1.8 sec

Resources Loaded

15.6 sec

Page Rendered

330 ms

wecash.net screenshot

About Website

Welcome to wecash.net homepage info - get ready to check Wecash best content for Vietnam right away, or after learning these important things about wecash.net

Wecash创立于2013年10月，通过大数据技术、机器学习技术和人工智能等技术，帮助银行和非银行金融机构实现智能营销，降低获客成本，提高决策效率；为金融机构、场景商户和用户提供智能化的交易解决方案。

Visit wecash.net

Key Findings

We analyzed Wecash.net page load time and found that the first response time was 1.8 sec and then it took 15.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

wecash.net performance score

0

Network Requests Diagram

wecash.net

1813 ms

www.wecash.net

6643 ms

common.css

548 ms

jquery.js

2731 ms

index.css

3288 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 92% of them (22 requests) were addressed to the original Wecash.net, 8% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Wecash.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.1 kB (40%)

Content Size

341.5 kB

After Optimization

205.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wecash.net main page is 341.5 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. Images take 233.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 4.0 kB

  • Original 5.7 kB
  • After minification 4.7 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 1.0 kB, which is 18% 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 4.0 kB or 70% of the original size.

Image Optimization

-28%

Potential reduce by 65.1 kB

  • Original 233.9 kB
  • After minification 168.8 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, Wecash needs image optimization as it can save up to 65.1 kB or 28% 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 62.3 kB

  • Original 95.8 kB
  • After minification 95.8 kB
  • After compression 33.4 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 62.3 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 4.7 kB

  • Original 6.1 kB
  • After minification 4.0 kB
  • After compression 1.4 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. Wecash.net needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wecash. According to our analytics all requests are already optimized.

Network Requests Diagram

wecash.net

wecash.net

1813 ms

www.wecash.net

www.wecash.net

6643 ms

common.css

common.css

548 ms

jquery.js

jquery.js

2731 ms

index.css

index.css

3288 ms

hm.js

hm.js

1399 ms

logo.png

logo.png

546 ms

banner01.png

banner01.png

2619 ms

download.png

download.png

547 ms

close.png

close.png

1090 ms

downloadcode2.png

downloadcode2.png

2181 ms

downloadcode.png

downloadcode.png

1637 ms

ios.png

ios.png

2178 ms

android.png

android.png

2178 ms

banner02.png

banner02.png

2180 ms

banner03.png

banner03.png

2175 ms

banner04.png

banner04.png

2708 ms

banner06.png

banner06.png

3251 ms

wechat.png

wechat.png

2711 ms

wechatcode.png

wechatcode.png

3802 ms

weibo.png

weibo.png

2711 ms

customsupport.png

customsupport.png

3155 ms

address.png

address.png

3246 ms

hm.gif

hm.gif

349 ms

SEO Factors

wecash.net SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecash.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Wecash.net 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

wecash.net

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