8.9 sec in total
468 ms
8 sec
380 ms
Visit 520im.com now to see the best up-to-date 520 Im content and also check out these interesting facts you probably never knew about 520im.com
抖客吧(douke8.com)是一个知名专业的抖音论坛社区,这里有众多抖音短视频爱好者参与交流,短视频平台快手,小红书,视频号短视频论坛,国际版抖音Tiktok论坛。抖音论坛让你施展你的才华,提供短视频变现交流。
Visit 520im.comWe analyzed 520im.com page load time and found that the first response time was 468 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
520im.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.3 s
100/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.3 s
100/100
10%
468 ms
529 ms
72 ms
138 ms
273 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 520im.com, 71% (70 requests) were made to Bbs.520im.com and 4% (4 requests) were made to Tjs.sjs.sinajs.cn. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Cnzz.mmstat.com.
Page size can be reduced by 339.9 kB (35%)
975.4 kB
635.6 kB
In fact, the total size of 520im.com main page is 975.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. 50% of websites need less resources to load. Images take 617.5 kB which makes up the majority of the site volume.
Potential reduce by 84.8 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 84.8 kB or 86% of the original size.
Potential reduce by 93.5 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, 520 Im needs image optimization as it can save up to 93.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 97.3 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 97.3 kB or 55% of the original size.
Potential reduce by 64.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. 520im.com needs all CSS files to be minified and compressed as it can save up to 64.3 kB or 77% of the original size.
Number of requests can be reduced by 33 (35%)
94
61
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 520 Im. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
520im.com
468 ms
bbs.520im.com
529 ms
style_2_common.css
72 ms
style_2_forum_index.css
138 ms
common.js
273 ms
blue_c_1.css
139 ms
forum.js
141 ms
logging.js
140 ms
md5.js
140 ms
mo_weibo_dzx.js
204 ms
ping.js
477 ms
stat.php
1992 ms
discuz_tips.js
600 ms
558a07381cd2ed575677e5e09ace19a0
1653 ms
repeat-x.jpg
73 ms
logo.png
73 ms
qq_login.gif
75 ms
weibo_login.png
74 ms
qqgroup.png
106 ms
220752l12uy4tc32o5yyy5.jpg
208 ms
77_avatar_small.jpg
133 ms
64_avatar_small.jpg
137 ms
85_avatar_small.jpg
136 ms
4.gif
137 ms
48_avatar_small.jpg
144 ms
collapsed_no.gif
204 ms
common_81_icon.png
202 ms
common_53_icon.jpg
271 ms
common_11_icon.jpg
272 ms
common_47_icon.jpg
276 ms
common_144_icon.jpg
269 ms
common_8_icon.png
268 ms
common_133_icon.jpg
278 ms
common_74_icon.png
337 ms
103623q4ogg0gy4ozvbok3.png
471 ms
common_15_icon.png
338 ms
common_174_icon.png
338 ms
common_165_icon.png
341 ms
common_22_icon.jpg
343 ms
common_103_icon.jpg
404 ms
common_163_icon.jpg
405 ms
common_49_icon.png
406 ms
common_4_icon.png
408 ms
common_197_icon.jpg
410 ms
common_13_icon.png
474 ms
common_77_icon.jpg
475 ms
common_73_icon.jpg
476 ms
common_19_icon.jpg
477 ms
common_41_icon.jpg
479 ms
common_33_icon.jpg
526 ms
followbutton.php
1100 ms
plugin.php
502 ms
LOGO_1.gif
482 ms
anxsoft.gif
481 ms
softice.gif
448 ms
52pojie.gif
429 ms
tt86.gif
477 ms
qqsky.gif
494 ms
d4s.gif
493 ms
luckerer.gif
485 ms
switch_width.png
485 ms
MTUxMDA4NzI=.js
252 ms
h.js
1364 ms
px.png
433 ms
newarow.gif
472 ms
pn.png
482 ms
nv.png
419 ms
qmenu.png
418 ms
newnv_on.png
418 ms
nv_a.png
430 ms
search.png
466 ms
arrwd.gif
474 ms
ann.gif
418 ms
pt_item.png
417 ms
titlebg.png
417 ms
release.png
430 ms
noavatar_small.gif
469 ms
wb.js
8 ms
loading1.gif
472 ms
bundle.js
6 ms
client.js
3 ms
iframeWidget.js
3 ms
aj_relationship.php
921 ms
followButton.css
10 ms
sso.js
3 ms
followButton.js
5 ms
suda.js
5 ms
b.gif
1069 ms
bg_flbtn.png
2 ms
followbutton.php
888 ms
hm.gif
446 ms
stat.htm
162 ms
core.php
1002 ms
b.gif
535 ms
9.gif
2400 ms
pic1.gif
1177 ms
scrolltop.png
70 ms
app.gif
1648 ms
520im.com 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
520im.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
520im.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 520im.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 520im.com 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.
520im.com
Open Graph description is not detected on the main page of 520 Im. 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: