71.8 sec in total
3.4 sec
67.8 sec
616 ms
Welcome to shalang.cn homepage info - get ready to check Shalang best content right away, or after learning these important things about shalang.cn
龟,鳖,金钱龟,石龟,安南龟,鳄龟
Visit shalang.cnWe analyzed Shalang.cn page load time and found that the first response time was 3.4 sec and then it took 68.4 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 35 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
shalang.cn performance score
name
value
score
weighting
Value3.4 s
39/100
10%
Value3.4 s
68/100
25%
Value7.5 s
26/100
10%
Value1,900 ms
8/100
30%
Value0.001
100/100
15%
Value8.0 s
42/100
10%
3448 ms
2791 ms
432 ms
1340 ms
897 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 85% of them (93 requests) were addressed to the original Shalang.cn, 2% (2 requests) were made to Fp.fraudmetrix.cn and 2% (2 requests) were made to Tcss.qq.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Shalang.cn.
Page size can be reduced by 241.6 kB (39%)
624.9 kB
383.3 kB
In fact, the total size of Shalang.cn main page is 624.9 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 343.1 kB which makes up the majority of the site volume.
Potential reduce by 76.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 76.6 kB or 81% of the original size.
Potential reduce by 41.0 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, Shalang needs image optimization as it can save up to 41.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 120.5 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 120.5 kB or 66% of the original size.
Potential reduce by 3.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. Shalang.cn needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 68% of the original size.
Number of requests can be reduced by 18 (25%)
71
53
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shalang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
www.shalang.cn
3448 ms
clear.png
2791 ms
fm.js
432 ms
style_7_common.css
1340 ms
style_7_forum_index.css
897 ms
style.css
895 ms
common.js
19867 ms
forum.js
4379 ms
a.jpg
1349 ms
logging.js
1585 ms
profile.json
2106 ms
ping.js
531 ms
discuz_tips.js
482 ms
1.jpg
545 ms
logo.gif
4646 ms
1634248z93g8w9w1qqwqtp.gif
12056 ms
logo.gif
1393 ms
bg_body.jpg
20445 ms
bg_toptb.png
465 ms
logo.png
2339 ms
qq_login.gif
459 ms
ps1.gif
5286 ms
sygg.gif
3194 ms
nn.gif
4436 ms
lxtx.gif
14211 ms
kl.gif
4643 ms
hzh.gif
5421 ms
hx.gif
11677 ms
022.gif
7622 ms
011546bn3hzipmummj18eu.jpg
20442 ms
011411zjmmnqi6p0xhvbhq.jpg
20443 ms
94d22580ef04e383ba0f85d2271a9890.jpg
20159 ms
899c50a213e1c3b3e13d1d4508c166ea.jpg
20442 ms
ebe86a7cb0ecd33d310f543f76f4697a.jpg
20442 ms
b346963a92cb368de39042f8585bdca1.jpg
20444 ms
3754b7f3790308f738c057d0bc19ab13.jpg
20445 ms
cb850ffc8d7eabecd0f16eb5232834a3.jpg
20446 ms
0bca8cf1872149f10cfc093eb642d625.jpg
20446 ms
c0df72f41af7017433a0a33f9dc91b9d.jpg
20445 ms
yestoday.gif
20446 ms
replay.gif
20447 ms
members.gif
20448 ms
welcome.gif
20448 ms
collapsed_no.gif
20449 ms
common_5_icon.jpg
20450 ms
new.gif
20451 ms
common_11_icon.jpg
20454 ms
common_6_icon.jpg
20454 ms
common_9_icon.jpg
20455 ms
common_10_icon.jpg
20455 ms
common_78_icon.jpg
20455 ms
common_7_icon.jpg
20455 ms
common_79_icon.jpg
20449 ms
MzE4NTQ2MA==.js
281 ms
z_stat.php
1369 ms
common_14_icon.jpg
20013 ms
common_58_icon.jpg
20008 ms
bg_link.jpg
3420 ms
stat.htm
229 ms
core.php
1200 ms
common_8_icon.jpg
20108 ms
9.gif
898 ms
pic1.gif
790 ms
common_13_icon.jpg
19924 ms
app.gif
867 ms
common_57_icon.jpg
16900 ms
common_12_icon.jpg
19798 ms
common_15_icon.jpg
20156 ms
common_16_icon.jpg
20020 ms
common_18_icon.jpg
14724 ms
common_19_icon.jpg
11121 ms
1634248z93g8w9w1qqwqtp.gif
7788 ms
common_27_icon.jpg
9037 ms
common_26_icon.jpg
7531 ms
common_28_icon.jpg
11691 ms
common_29_icon.jpg
3255 ms
common_43_icon.jpg
5079 ms
common_39_icon.jpg
5492 ms
banzhu.png
5460 ms
common_40_icon.jpg
5866 ms
common_41_icon.jpg
6605 ms
common_53_icon.jpg
8933 ms
common_81_icon.jpg
11808 ms
common_84_icon.jpg
8326 ms
common_22_icon.jpg
11219 ms
common_32_icon.jpg
10763 ms
common_31_icon.jpg
10171 ms
common_30_icon.jpg
19984 ms
common_33_icon.jpg
12076 ms
common_46_icon.jpg
13602 ms
common_50_icon.jpg
12655 ms
common_36_icon.jpg
13122 ms
common_59_icon.jpg
13158 ms
common_37_icon.jpg
13020 ms
common_38_icon.jpg
14502 ms
common_65_icon.jpg
17519 ms
233313reg3ub1gejvu3ppw.gif
14474 ms
165755hzn0hfh09qd73ntr.jpg
19973 ms
161132fsnnkne5xvm5nsza.jpg
19972 ms
ad_close.gif
14909 ms
144337lifmm8404d2m700m.gif
20105 ms
switch_width.png
13510 ms
pn.png
13856 ms
nv.gif
13951 ms
nv_a.gif
14080 ms
search.png
14397 ms
pt_item.png
14393 ms
sortnum.png
14003 ms
chart.png
13096 ms
scrolltop.png
13453 ms
shalang.cn accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Links do not have a discernible name
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.
shalang.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
shalang.cn 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 uses legible font sizes
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shalang.cn 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 Shalang.cn main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
shalang.cn
Open Graph description is not detected on the main page of Shalang. 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: