Access wechatwiki.com. WeChat Wiki - understand and leverage WeChat for businesses

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

wechatwiki.com

428 ms

gtm.js

76 ms

wp-emoji-release.min.js

304 ms

style.min.css

316 ms

style.min.css

320 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 98% of them (42 requests) were addressed to the original Wechatwiki.com, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Wechatwiki.com.

Content Size

222.7 kB

After Optimization

153.0 kB

In fact, the total size of Wechatwiki.com main page is 222.7 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. CSS take 61.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.9 kB

Original 60.4 kB
After minification 53.7 kB
After compression 11.5 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 6.7 kB, which is 11% 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 48.9 kB or 81% of the original size.

Image Optimization

-41%

Potential reduce by 18.4 kB

Original 44.6 kB
After minification 26.2 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 Chat Wiki needs image optimization as it can save up to 18.4 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 1.3 kB

Original 56.3 kB
After minification 56.3 kB
After compression 55.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.1 kB

Original 61.3 kB
After minification 61.3 kB
After compression 60.3 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. Wechatwiki.com has all CSS files already compressed.

Requests Now

After Optimization

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