Tools & Wizards About Us
wecenter.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

wecenter.com

WeCenter创建你的知识社区 | 一款开源知识社区问答程序

Page Load Speed

11.5 sec in total

First Response

929 ms

Resources Loaded

10.4 sec

Page Rendered

205 ms

wecenter.com screenshot

About Website

Welcome to wecenter.com homepage info - get ready to check We Center best content for China right away, or after learning these important things about wecenter.com

WeCenter 是一款开源知识型的社交化问答社区程序，专注于社区内容的整理、归类和检索，并通过连接微信公众平台，移动APP进行内容分发。

Visit wecenter.com

Key Findings

We analyzed Wecenter.com page load time and found that the first response time was 929 ms and then it took 10.6 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

wecenter.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

wecenter.com

929 ms

www.wecenter.com

1037 ms

bootstrap.css

3623 ms

style.css

608 ms

jquery.js

922 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 88% of them (15 requests) were addressed to the original Wecenter.com, 6% (1 request) were made to Wenda.wecenter.com and 6% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Wecenter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.6 kB (34%)

Content Size

520.4 kB

After Optimization

345.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wecenter.com main page is 520.4 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 335.0 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 6.8 kB

  • Original 11.1 kB
  • After minification 10.7 kB
  • After compression 4.3 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 6.8 kB or 61% of the original size.

Image Optimization

-11%

Potential reduce by 36.1 kB

  • Original 335.0 kB
  • After minification 298.9 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, We Center needs image optimization as it can save up to 36.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

-44%

Potential reduce by 18.2 kB

  • Original 40.9 kB
  • After minification 35.5 kB
  • After compression 22.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 18.2 kB or 44% of the original size.

CSS Optimization

-85%

Potential reduce by 113.4 kB

  • Original 133.4 kB
  • After minification 111.3 kB
  • After compression 20.0 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. Wecenter.com needs all CSS files to be minified and compressed as it can save up to 113.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wecenter.com

wecenter.com

929 ms

www.wecenter.com

www.wecenter.com

1037 ms

bootstrap.css

bootstrap.css

3623 ms

style.css

style.css

608 ms

jquery.js

jquery.js

922 ms

bootstrap.js

bootstrap.js

621 ms

html5shiv.js

html5shiv.js

1508 ms

limit-6

limit-6

970 ms

logo.png

logo.png

304 ms

index.png

index.png

2422 ms

homepage_settings.png

homepage_settings.png

909 ms

homepage_developer.png

homepage_developer.png

607 ms

homepage_route.png

homepage_route.png

3020 ms

homepage_bootstrap.png

homepage_bootstrap.png

4771 ms

customers.png

customers.png

1818 ms

homepage_qr_code.png

homepage_qr_code.png

911 ms

ga.js

ga.js

5 ms

Accessibility Review

wecenter.com accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

wecenter.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wecenter.com SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecenter.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 Wecenter.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

wecenter.com

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