8.6 sec in total
1 sec
7.4 sec
165 ms
Click here to check amazing Binbinke content. Otherwise, check out these important facts you probably never knew about binbinke.com
智承论坛,智承大课堂交流论坛,我们提供最新的智承大课堂信息及会员间的交流服务。
Visit binbinke.comWe analyzed Binbinke.com page load time and found that the first response time was 1 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
binbinke.com performance score
1026 ms
827 ms
666 ms
453 ms
678 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Binbinke.com, 75% (44 requests) were made to Bbs.binbinke.com and 17% (10 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Binbinke.com.
Page size can be reduced by 295.5 kB (64%)
463.9 kB
168.4 kB
In fact, the total size of Binbinke.com main page is 463.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. 30% of websites need less resources to load. Javascripts take 256.3 kB which makes up the majority of the site volume.
Potential reduce by 46.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 46.8 kB or 81% of the original size.
Potential reduce by 19.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, Binbinke needs image optimization as it can save up to 19.2 kB or 46% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 143.8 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 143.8 kB or 56% of the original size.
Potential reduce by 85.6 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. Binbinke.com needs all CSS files to be minified and compressed as it can save up to 85.6 kB or 80% of the original size.
Number of requests can be reduced by 21 (38%)
56
35
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Binbinke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
binbinke.com
1026 ms
forum.php
827 ms
style_2_common.css
666 ms
style_2_forum_index.css
453 ms
common.js
678 ms
jquery.min.js
677 ms
forum.js
688 ms
logging.js
455 ms
pc_proxy.php
828 ms
dbank_plugin.js
1451 ms
superslide.2.1.js
471 ms
discuz_tips.js
555 ms
logo.jpg
4055 ms
bg.jpg
231 ms
logo.png
223 ms
list_7ree.gif
224 ms
collapsed_no.gif
997 ms
forum.gif
1020 ms
online_admin.gif
1053 ms
online_supermod.gif
1054 ms
online_moderator.gif
1066 ms
online_member.gif
1209 ms
security.png
1248 ms
search.png
1247 ms
noavatar_small.gif
998 ms
noavatar_small.gif
994 ms
noavatar_small.gif
801 ms
noavatar_small.gif
938 ms
noavatar_small.gif
971 ms
67_avatar_small.jpg
920 ms
noavatar_small.gif
932 ms
noavatar_small.gif
933 ms
noavatar_small.gif
757 ms
noavatar_small.gif
888 ms
noavatar_small.gif
909 ms
noavatar_small.gif
879 ms
60_avatar_small.jpg
880 ms
noavatar_small.gif
881 ms
search.png
766 ms
pt_item.png
891 ms
chart.png
933 ms
1rss.png
930 ms
1douban.png
924 ms
1renren.png
933 ms
1qzone.png
969 ms
1qqweibo.png
1087 ms
1weibo.png
1130 ms
share.js
935 ms
totop.png
2671 ms
noavatar_small.gif
1136 ms
share_api.js
230 ms
share_view.js
455 ms
select_api.js
457 ms
select_view.js
464 ms
tangram.js
1662 ms
api_base.js
450 ms
view_base.js
232 ms
partners.js
234 ms
share_style0_24.css
235 ms
binbinke.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Binbinke.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 Binbinke.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.
binbinke.com
Open Graph description is not detected on the main page of Binbinke. 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: