73.8 sec in total
11.5 sec
59.7 sec
2.6 sec
Visit qdtz.miniban.cn now to see the best up-to-date Qdtz Miniban content for China and also check out these interesting facts you probably never knew about qdtz.miniban.cn
四海兄弟.青岛同志,青岛同志聊天室, 青岛gay,同性恋,拉拉,同志交友,青岛同性爱,arian,四海,四海兄弟,青岛boy
Visit qdtz.miniban.cnWe analyzed Qdtz.miniban.cn page load time and found that the first response time was 11.5 sec and then it took 62.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
qdtz.miniban.cn performance score
11461 ms
19956 ms
1202 ms
1209 ms
2350 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 9% of them (14 requests) were addressed to the original Qdtz.miniban.cn, 56% (83 requests) were made to Static.miniban.cn and 13% (19 requests) were made to Cache.miniban.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Cache.miniban.cn.
Page size can be reduced by 998.7 kB (72%)
1.4 MB
389.4 kB
In fact, the total size of Qdtz.miniban.cn main page is 1.4 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. 35% of websites need less resources to load. HTML takes 587.8 kB which makes up the majority of the site volume.
Potential reduce by 554.4 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 299.3 kB, which is 51% 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 554.4 kB or 94% of the original size.
Potential reduce by 9.9 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. Qdtz Miniban images are well optimized though.
Potential reduce by 343.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 343.0 kB or 65% of the original size.
Potential reduce by 91.5 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. Qdtz.miniban.cn needs all CSS files to be minified and compressed as it can save up to 91.5 kB or 84% of the original size.
Number of requests can be reduced by 87 (67%)
129
42
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qdtz Miniban. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
qdtz.miniban.cn
11461 ms
Form.css
19956 ms
Global.css
1202 ms
Import.css
1209 ms
Layout.css
2350 ms
Pager.css
7092 ms
HomeLogin.css
2157 ms
Global.js
2849 ms
jquery-1.7.2.min.js
10246 ms
jquery.cookie.js
2193 ms
jquery-ui-1.8.24.custom.min.js
18095 ms
UI.js
5179 ms
Common.js
3458 ms
Front.js
6165 ms
jquery.blockUI.js
11826 ms
jquery.colorbox.min.js
10861 ms
jquery.confirmModal.js
19947 ms
List.js
16280 ms
jquery.confirm.js
11431 ms
jquery.inputlimiter.1.2.1.min.js
13398 ms
VideoUrl.js
14459 ms
jquery.poshytip.min.js
15110 ms
jquery.flash.min.js
18617 ms
jquery.json.min.js
15708 ms
jquery.dropDownList.js
16257 ms
imgReady.js
16814 ms
List.css
16852 ms
kindeditor-min.js
19943 ms
zh_CN.js
19334 ms
Editor.js
19941 ms
Common.js
19941 ms
MessageEditor.css
19940 ms
WebForms.js
200 ms
MicrosoftAjax.zh-Hans.js
393 ms
MicrosoftAjaxWebForms.zh-Hans.js
489 ms
Default.css
19745 ms
Common.css
19744 ms
jquery-ui-1.8.24.custom.edit.css
19647 ms
colorbox.css
19743 ms
tip-yellow.css
19744 ms
c.js
2323 ms
stat.php
896 ms
BGRepeat.png
462 ms
ScriptResource.axd
3442 ms
Logo.png
1595 ms
e8d19382a4a145f59613bf6d51866462_s.jpg
1145 ms
Blank.gif
540 ms
1.gif
821 ms
2.gif
2113 ms
Activepower.gif
954 ms
2cb425a313774ee9a02fcbba1860a6bf_s.jpg
3337 ms
c4eded61caa54687b592891f2239082d_s.jpg
1184 ms
9a5629acc9c0443d86f0cdead9dffb77_s.jpg
4226 ms
3b5072b9b5934e53a526e08d0f1bed82_s.jpg
11353 ms
e6c93fe71a994c6fb33c189dad65e698_s.jpg
20479 ms
0d50fb192a104ef6848cf45f8f37d98b_s.jpg
1708 ms
ad976e17db524ac69980b38324d37b85_s.jpg
20476 ms
fa15e6454cdd49e98fe6b0873bd6b73e_s.jpg
4475 ms
f8202e416469441ebca511713b1167c6_s.jpg
14459 ms
439ff12f75dc4d839319aae9f525d520_s.jpg
5546 ms
ef86224deb544711a897433046841ee5_s.jpg
5134 ms
2867ff32511346789f44b9e35e087e5e_s.jpg
5963 ms
8274938803a24af7a8c1ec43d9410d6f_s.jpg
5969 ms
5f13b87a30834931902e83b2d7e57b39_s.jpg
6681 ms
2d1b8ba95c3b401b9347c9407a2ec37e_s.jpg
11349 ms
cb94e0784ce04a89882392f82cd1bea4_s.jpg
10305 ms
9fcc60e5caab4402a064be91dbd88afa_s.jpg
11355 ms
284f5099d2f840c1b97f1cae1cf42833_s.jpg
20455 ms
DefaultRegUserFace.jpg
2220 ms
DefaultGuestFace_s.jpg
929 ms
DefaultGuestFace.jpg
1585 ms
DefaultRegUserFace_s.jpg
1054 ms
ScriptResource.axd
2004 ms
TopNavBG.png
529 ms
NavHome.png
542 ms
NavSplit.png
955 ms
NavQQLogin.png
956 ms
NavLogin.png
2609 ms
NavReg.png
962 ms
ADHomeTop.png
1322 ms
eccm
3878 ms
PosterWrapper.png
1250 ms
FaceBox.png
1281 ms
SelectGuestFace.png
1647 ms
NicknameSplit.gif
1711 ms
NicknameTextBG.png
1719 ms
NicknameInput.png
1807 ms
TitleTextBG.png
2093 ms
TitleLong.png
2494 ms
BottomInfoContainer.png
2484 ms
PostButton.png
2474 ms
RootMessagePostProgress.gif
3396 ms
HotTopic.png
2640 ms
HotTopicWrapperSplit.png
2660 ms
BoardNavBar.png
2665 ms
BoardNavButtonOn.gif
4145 ms
TopNewsContentBG.png
4159 ms
TopNews.png
20288 ms
SearchBoxBG.png
6222 ms
ArrowDown.png
6921 ms
SearchButton.png
3840 ms
MessageListWrapper.png
4383 ms
MessageListItemWrapper.png
7468 ms
MessageListItemBottom.png
4568 ms
UserInfo-Username.png
5586 ms
MessageListItemContentRightCorner.gif
5031 ms
TopBarDotted.png
5551 ms
ReplyIcon.png
6144 ms
FavoriteStar.png
6040 ms
ThumbnailBox.gif
6566 ms
eccm
876 ms
ReplyListArrow.png
6238 ms
ReplyListDotted.gif
6034 ms
ADContentBottom.gif
6267 ms
PageNum.png
6263 ms
PagerNextPage.png
6541 ms
eccm
1775 ms
stat.htm
201 ms
core.php
1158 ms
eccm
1649 ms
PagerLastPage.png
6342 ms
ADListBottom-Repeat.png
6359 ms
ADListBottom-Top.png
6315 ms
9.gif
1897 ms
ga.js
359 ms
Ajax_GetViewStat.ashx
449 ms
TopCenterBG.png
19832 ms
ui-bg_flat_75_ffffff_40x100.png
5595 ms
ui-icons_222222_256x240.png
6160 ms
__utm.gif
256 ms
sync.htm
1545 ms
ctm3.js
1506 ms
eccm
2549 ms
0.gif
1130 ms
9.gif
1734 ms
2.gif
1415 ms
6.gif
1620 ms
8.gif
1441 ms
eccm
4182 ms
app.gif
989 ms
sync_pos.htm
364 ms
sync2r.htm
2404 ms
s.htm
549 ms
sync.html
2334 ms
0f0002fcSNIrp5EFz1__76.jpg
849 ms
o.htm
1749 ms
wh.js
790 ms
ac.js
563 ms
qdtz.miniban.cn SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qdtz.miniban.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 Qdtz.miniban.cn 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.
qdtz.miniban.cn
Open Graph description is not detected on the main page of Qdtz Miniban. 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: