Tools & Wizards About Us
weangel.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

weangel.com

Page Load Speed

49.5 sec in total

First Response

1.4 sec

Resources Loaded

47.8 sec

Page Rendered

353 ms

weangel.com screenshot

About Website

Welcome to weangel.com homepage info - get ready to check Weangel best content right away, or after learning these important things about weangel.com

微天使是一个以社群协作模式来帮助创业者快速组建团队、获得资金、管理股权的创业平台。我们认为只要加上一剂配料，原本只适合于非盈利项目的维基百科、GitHub的社群协作模式就能在其他领域大放异彩。我们来自数字货币社区，我们掌握了这剂配料。因此，我们提出了“开放公司”的概念，像协同编写开源软件一样建立开放的公司。

Visit weangel.com

Key Findings

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

Performance Metrics

weangel.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

weangel.com

1378 ms

weangel.com

15026 ms

bootstrap.min.css

19839 ms

styles.css

12989 ms

WeAngel.js

19838 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 76% of them (26 requests) were addressed to the original Weangel.com, 18% (6 requests) were made to Ajax.aspnetcdn.com and 3% (1 request) were made to Res.wx.qq.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Weangel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (86%)

Content Size

1.2 MB

After Optimization

168.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weangel.com main page is 1.2 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. HTML takes 957.2 kB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 904.6 kB

  • Original 957.2 kB
  • After minification 902.0 kB
  • After compression 52.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 904.6 kB or 95% of the original size.

Image Optimization

-13%

Potential reduce by 5.0 kB

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

JavaScript Optimization

-51%

Potential reduce by 73.0 kB

  • Original 143.9 kB
  • After minification 135.9 kB
  • After compression 70.8 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 73.0 kB or 51% of the original size.

CSS Optimization

-80%

Potential reduce by 51.6 kB

  • Original 64.8 kB
  • After minification 53.9 kB
  • After compression 13.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. Weangel.com needs all CSS files to be minified and compressed as it can save up to 51.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weangel.com

weangel.com

1378 ms

weangel.com

weangel.com

15026 ms

bootstrap.min.css

bootstrap.min.css

19839 ms

styles.css

styles.css

12989 ms

WeAngel.js

WeAngel.js

19838 ms

v2.css

v2.css

8584 ms

WebForms.js

WebForms.js

122 ms

MicrosoftAjax.zh-Hans.js

MicrosoftAjax.zh-Hans.js

385 ms

MicrosoftAjaxWebForms.zh-Hans.js

MicrosoftAjaxWebForms.zh-Hans.js

485 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

270 ms

bootstrap.min.js

bootstrap.min.js

248 ms

WebUIValidation.js

WebUIValidation.js

248 ms

qrcode.min.js

qrcode.min.js

6940 ms

jquery.qrcode.min.js

jquery.qrcode.min.js

7346 ms

js

js

9188 ms

headroom.js

headroom.js

3216 ms

wxLogin.js

wxLogin.js

2592 ms

blank

blank

5 ms

logo-nav.png

logo-nav.png

9574 ms

banner-img.png

banner-img.png

5227 ms

banner2.png

banner2.png

19994 ms

banner3.jpg

banner3.jpg

19995 ms

1b1.jpg

1b1.jpg

1757 ms

noavatar.jpg

noavatar.jpg

5114 ms

logo-footer.png

logo-footer.png

3989 ms

36kr.gif

36kr.gif

4367 ms

qq.gif

qq.gif

6233 ms

sina.gif

sina.gif

9380 ms

siilu.gif

siilu.gif

5633 ms

sootoo.gif

sootoo.gif

6039 ms

techweb.gif

techweb.gif

6445 ms

ScriptResource.axd

ScriptResource.axd

11702 ms

ScriptResource.axd

ScriptResource.axd

1911 ms

iconfont.woff

iconfont.woff

8102 ms

Accessibility Review

weangel.com accessibility score

85

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

weangel.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

weangel.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Weangel.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 Weangel.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

weangel.com

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