106 sec in total
16.4 sec
88.9 sec
787 ms
Welcome to qbj.cc homepage info - get ready to check Qbj best content for China right away, or after learning these important things about qbj.cc
青白江论坛是青白江地区家喻户晓的本地门户网站!涵盖青白江区吃喝玩乐,樱花节,二手交易,同城交友,法律服务等版块的交流平台。我们主旨是:为青白江百姓提供优质的网络服务,做一个有生活态度的青白江门户网站!
Visit qbj.ccWe analyzed Qbj.cc page load time and found that the first response time was 16.4 sec and then it took 89.7 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 57 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
qbj.cc performance score
16360 ms
19586 ms
19590 ms
19220 ms
19591 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 81% of them (101 requests) were addressed to the original Qbj.cc, 3% (4 requests) were made to Static.css.weather.com.cn and 2% (3 requests) were made to Ext.weather.com.cn. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Qbj.cc.
Page size can be reduced by 201.6 kB (54%)
376.7 kB
175.1 kB
In fact, the total size of Qbj.cc main page is 376.7 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. 20% of websites need less resources to load. HTML takes 149.3 kB which makes up the majority of the site volume.
Potential reduce by 118.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 118.8 kB or 80% of the original size.
Potential reduce by 14.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. Qbj images are well optimized though.
Potential reduce by 27.9 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 27.9 kB or 64% of the original size.
Potential reduce by 40.7 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. Qbj.cc needs all CSS files to be minified and compressed as it can save up to 40.7 kB or 85% of the original size.
Number of requests can be reduced by 28 (43%)
65
37
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qbj. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
qbj.cc
16360 ms
jquery-1.8.3.min.js
19586 ms
style_2_common.css
19590 ms
style_2_forum_index.css
19220 ms
common.js
19591 ms
123.css
8803 ms
forum.js
12246 ms
logging.js
11780 ms
md5.js
19610 ms
global.css
12349 ms
66677.js
875 ms
imc_access_pop.css
9908 ms
extend_common.css
9422 ms
jqueryad.min.js
20145 ms
loginbar.css
17496 ms
stat.php
1285 ms
discuz_tips.js
443 ms
20160317z.jpg
13586 ms
212223nerjr0jczygjyul8.png
5801 ms
qq_login.gif
4146 ms
wechat_login.png
8462 ms
ad1.jpg
19982 ms
tfic2016111.jpg
19983 ms
fatie.jpg
19099 ms
31b7f8687c8b6717ae484955ef125c06.jpg
12870 ms
d0788a6d5dc599e4d07d5240a0ff5c46.jpg
19825 ms
ec414fa3b9fbecfbe3e6c80fb911cda4.jpg
13035 ms
3f3671b535e2092fb456732467bf20bb.jpg
19982 ms
b2aa7a00004ff59b8f14fb2f7f44a17f.jpg
19983 ms
50d27b120ad5efbbf5a5353b33075717.jpg
19986 ms
da058681fdbec06256f859ce15b4d529.jpg
19987 ms
475852313d8d566f57ec752730c4f1a2.jpg
19988 ms
68d9a831fcc58ae42f112cf1804f2125.jpg
19989 ms
1cd454ee842332365b812a9234069971.jpg
19990 ms
acaf9e9ed22e036379e106e93bc57564.jpg
19992 ms
1d360b4d958c9fa90cc629cbe08ae330.jpg
19992 ms
2bfcf905667677298dff9922c3dae38b.jpg
19993 ms
117b15be69c2ff6649ebccc7b2957e0e.jpg
19995 ms
2sc.jpg
19995 ms
3gcpjtl.jpg
19996 ms
1ce1a136a41aab9c655cfffae50e1600.jpg
19995 ms
24019ce0d41c7b2e49a49d4f301275d5.jpg
19996 ms
03823526a2e13970dde15461a193df0d.jpg
19996 ms
3e4637b24b90b50009f3f966d7ebfe95.jpg
19996 ms
eab2e295aa62da1d0c2ae9f43dbb5492.jpg
19997 ms
423382226683b88c029522255e215f42.jpg
19997 ms
jiaxiaoAD.jpg
19998 ms
757d6737f9abbf9385ecf7e5c9a2e14c.jpg
19998 ms
42806df79cb867506059e60df77a323e.jpg
19998 ms
20160317y.jpg
19998 ms
2bab697fc5e5ff1fc6a390bc3017e1b5.jpg
19998 ms
7cd408ffa229fb2c74af6cfc6ebc543c.jpg
19986 ms
66677.html
2199 ms
hao123.css
1788 ms
jquery.js
9353 ms
b.js
2449 ms
hao123.js
8079 ms
b.css
574 ms
56a806e42e6901c36d05c43ce8cf724b.jpg
19845 ms
ec15a99af530b9f0164009e564641eac.jpg
19839 ms
835370a8abf1303116b30e45fabfa262.jpg
20184 ms
01d45a1c08f14f09996bfa4cd6a7eac7.jpg
18699 ms
stat.htm
171 ms
core.php
2784 ms
0f7ec89fa47065a07859eebe3de8e34e.jpg
19988 ms
bf5d31d3cdc1be4aa5fa873a53cc2efa.jpg
19522 ms
9.gif
814 ms
pic.gif
1502 ms
app.gif
1100 ms
h.js
538 ms
101270101.json
2079 ms
hm.gif
276 ms
collapsed_no.gif
13076 ms
common_75_icon.jpg
17567 ms
pluginlog.aspx
1201 ms
index_icon.gif
559 ms
small.gif
19689 ms
lmz.png
7856 ms
chwl.png
10639 ms
tcjy.png
18550 ms
qgsj.png
13315 ms
gysj.png
13530 ms
ylgx.png
13025 ms
zpqz.png
15513 ms
fwzs.png
18258 ms
common_144_icon.png
13880 ms
common_145_icon.png
16442 ms
gegz.png
15017 ms
flfw.png
19405 ms
common_146_icon.png
19982 ms
yhdyc.png
17408 ms
%E8%99%9A%E4%BD%8D%E4%BB%A5%E5%BE%85.png
19981 ms
common_143_icon.jpg
19981 ms
dcy.png
19981 ms
mtc.png
19981 ms
cyh.png
19980 ms
lzjx.png
19981 ms
wxd.png
19980 ms
yy.png
19980 ms
common_141_icon.jpg
19979 ms
yydr.png
19979 ms
bdxw.png
19978 ms
gnxw.png
19978 ms
gjxw.png
19978 ms
zwgk.png
19974 ms
tsjy.png
19998 ms
bkp.png
17282 ms
reg_bg.jpg
19622 ms
collapsed_yes.gif
15512 ms
ad_close.gif
19115 ms
security.png
17701 ms
site_qq.jpg
14260 ms
1.gif
19513 ms
2.gif
20374 ms
chart.png
12684 ms
comiis_ngtonbg.gif
15702 ms
comiis_ngtbg.gif
12748 ms
list.gif
15635 ms
hm.gif
529 ms
comiis_idzh.gif
11831 ms
titlebg.png
11923 ms
comiis_bm_h.gif
11571 ms
djz52top3.png
11797 ms
noavatar_big.gif
19923 ms
qbj.cc SEO score
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qbj.cc 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 Qbj.cc 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.
qbj.cc
Open Graph description is not detected on the main page of Qbj. 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: