82.9 sec in total
15.3 sec
67.2 sec
419 ms
Visit weixinsucai.net now to see the best up-to-date Weixinsucai content and also check out these interesting facts you probably never knew about weixinsucai.net
Visit weixinsucai.netWe analyzed Weixinsucai.net page load time and found that the first response time was 15.3 sec and then it took 67.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. This domain responded with an error, which can significantly jeopardize Weixinsucai.net rating and web reputation
weixinsucai.net performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.905
3/100
15%
Value0
0/100
10%
15271 ms
18194 ms
6120 ms
1242 ms
2452 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 40% of them (45 requests) were addressed to the original Weixinsucai.net, 11% (12 requests) were made to Pos.baidu.com and 9% (10 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Weixinsucai.net.
Page size can be reduced by 418.7 kB (39%)
1.1 MB
666.5 kB
In fact, the total size of Weixinsucai.net main page is 1.1 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. 40% of websites need less resources to load. Images take 536.4 kB which makes up the majority of the site volume.
Potential reduce by 160.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 160.6 kB or 83% of the original size.
Potential reduce by 26.1 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. Weixinsucai images are well optimized though.
Potential reduce by 159.6 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 159.6 kB or 59% of the original size.
Potential reduce by 72.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. Weixinsucai.net needs all CSS files to be minified and compressed as it can save up to 72.4 kB or 87% of the original size.
Number of requests can be reduced by 36 (35%)
104
68
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weixinsucai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
weixinsucai.net
15271 ms
style_2_common.css
18194 ms
common.js
6120 ms
jquery.min.js
1242 ms
portal.js
2452 ms
logging.js
1435 ms
csu_zk.css
1841 ms
nav.js
1526 ms
portaldiy.css
5549 ms
superslide.2.1.js
7207 ms
c.js
2176 ms
jiathis_r.js
449 ms
ujian.js
450 ms
discuz_tips.js
1150 ms
background.png
700 ms
wx_jqr.gif
608 ms
logo.png
5486 ms
8a1081a3a1686bb35a64fe589b4c2784.jpg
20232 ms
1212aa4d94febf870c1c11be9e8537c2.jpg
3661 ms
513b752ed14092377d3e2c03c046381d.jpg
1843 ms
7d0a53b1b522ab26962bc1fc4e1ed780.jpg
6012 ms
71c2137a7696fdf28af02685c116a2cc.jpg
6345 ms
b2098978fa0ded51bd6857a0ab43fda6.jpg
3652 ms
5acb799765c6d44db6837eef40a1c810.jpg
6428 ms
2ce747e15a7d6e060566339d81b8905c.jpg
5538 ms
9dddb7b2ae4c56bbbf751a7c9e0177b6.jpg
6109 ms
5a7fac6036e09b765133ae04fd745898.jpg
7401 ms
86e718b7548088651aca673803950493.jpg
7473 ms
99243a86433f07f5172558d9e9ba7f80.jpg
10623 ms
adcd54f38409054958ce8e3092c67e53.jpg
20230 ms
3a73f72e78068db6a8d06cfe010768f7.jpg
7664 ms
2f0d9926780344f4151b969ce1292468.jpg
8632 ms
36501a5e0d7a6b985c50dd4f652896b5.jpg
12313 ms
182607oour99rijomnzmzw.jpg
18920 ms
132019t175h7h5sv3pv9yy.jpg
10489 ms
131531am5z9yyjj48f8hfy.jpg
16601 ms
170231ovl35tlw5kl5ksm5.jpg
18024 ms
54bc573b8aeb159f5c8342b9922c5f11.jpg
20229 ms
130828xwbw54x5eqwxe5tz.jpg
20230 ms
150008nkkggymbygrbzgbm.jpg
20230 ms
2229b2177ed1bb343d1587364ded5ff8.jpg
20231 ms
ocim
731 ms
titlebg.jpg
3085 ms
ocim
692 ms
ocim
991 ms
ocim
1012 ms
ocim
2397 ms
jiathis_utility.html
4 ms
jiathis_share.css
15 ms
ckepop.js
5 ms
ckecenterpop.js
7 ms
plugin.client.js
6 ms
l.gif
6 ms
img_exit.gif
9 ms
api.ujian.cc
1187 ms
img_012.gif
10 ms
z_stat.php
2195 ms
jiathis_ico.png
14 ms
ocim
862 ms
ocim
1116 ms
ocim
1530 ms
ocim
1544 ms
mini_4732f41ec53ed55c8436_120_120.jpg
4209 ms
mini_41c9849e11edf19b5334_120_120.jpg
4203 ms
mini_f6ec36fa1924b514fe2f_120_120.jpg
4304 ms
mini_c11a84947ca044f1fbfa_120_120.jpg
6938 ms
mini_95f4628805638a4cd6b2_120_120.jpg
4226 ms
1.png
3893 ms
sync.htm
461 ms
ctm3.js
1204 ms
search.png
19600 ms
adx.php
1243 ms
sync_pos.htm
339 ms
stat.htm
168 ms
core.php
1356 ms
sync2r.htm
5027 ms
ocim
1029 ms
adx.php
1740 ms
u=1370778259,1709333503&fm=76
3631 ms
u=123778001,498062122&fm=76
3784 ms
u=2693019750,997452953&fm=76
1509 ms
bg.png
457 ms
u=1624846737,2114168580&fm=76
2470 ms
u=13589941,4864211&fm=76
2048 ms
u=3839857201,3764131613&fm=76
1261 ms
u=1658998879,2212093810&fm=76
1772 ms
u=1579780471,2190071743&fm=76
3664 ms
u=2053575326,2288407978&fm=76
1208 ms
u=1116736256,1399090194&fm=76
4080 ms
reduce_bd-logo1_oper.png
489 ms
adx.php
966 ms
native_ad.png
475 ms
0f000j1FY_bkyl3FJ2tGa6.jpg
2300 ms
adx.php
749 ms
closefeedback.min.js
484 ms
foot_point.png
17795 ms
9.gif
4390 ms
h.js
1317 ms
reduce_promotion_oper.png
444 ms
bd_logo.png
442 ms
bg_rb.png
448 ms
21.gif
799 ms
hm.gif
442 ms
foot_ico01.png
16367 ms
foot_ico02.png
18924 ms
foot_ico03.png
15932 ms
foot_ico04.png
16045 ms
scrolltop.png
15959 ms
app.gif
5820 ms
o.htm
781 ms
hm.gif
891 ms
wh.js
630 ms
ac.js
424 ms
weixinsucai.net accessibility score
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
weixinsucai.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
weixinsucai.net SEO score
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
Document doesn't use legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weixinsucai.net 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 Weixinsucai.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.
weixinsucai.net
Open Graph description is not detected on the main page of Weixinsucai. 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: