48.8 sec in total
9.9 sec
38.5 sec
451 ms
Welcome to lzc369.com homepage info - get ready to check Lzc 369 best content right away, or after learning these important things about lzc369.com
龙之藏论坛 ,龙之藏|金银器|古币|古泉|老银器|老银|古玩|收藏|瓷器|老银饰|杂件|玉器|龙网|古董|点翠|烧蓝|龙币|铜镜|香炉|银器|金器|论坛
Visit lzc369.comWe analyzed Lzc369.com page load time and found that the first response time was 9.9 sec and then it took 39 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lzc369.com performance score
9855 ms
2755 ms
1423 ms
3716 ms
789 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 68% of them (100 requests) were addressed to the original Lzc369.com, 5% (7 requests) were made to Cpro.baidustatic.com and 3% (5 requests) were made to T12.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Lzc369.com.
Page size can be reduced by 339.9 kB (66%)
513.2 kB
173.4 kB
In fact, the total size of Lzc369.com main page is 513.2 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. Javascripts take 352.2 kB which makes up the majority of the site volume.
Potential reduce by 109.5 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 109.5 kB or 84% of the original size.
Potential reduce by 2.7 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, Lzc 369 needs image optimization as it can save up to 2.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 219.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 219.8 kB or 62% of the original size.
Potential reduce by 7.9 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. Lzc369.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 76% of the original size.
Number of requests can be reduced by 24 (45%)
53
29
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lzc 369. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
forum.php
9855 ms
style_1_common.css
2755 ms
style_1_forum_index.css
1423 ms
common.js
3716 ms
style_1_widthauto.css
789 ms
forum.js
4061 ms
logging.js
1129 ms
logincode
1169 ms
logincode.jsp
1160 ms
background.png
360 ms
logo.png
331 ms
collapsed_no.gif
325 ms
forum.gif
332 ms
common_757_icon.jpg
452 ms
common_623_icon.jpg
19659 ms
common_32_icon.jpg
646 ms
common_5717_icon.jpg
688 ms
common_168_icon.jpg
688 ms
common_5715_icon.jpg
701 ms
common_5716_icon.jpg
904 ms
common_1653_icon.gif
965 ms
common_529_icon.jpg
1017 ms
common_5561_icon.jpg
1013 ms
common_5563_icon.jpg
1041 ms
common_5562_icon.jpg
1347 ms
common_5564_icon.jpg
1293 ms
common_5565_icon.jpg
1340 ms
common_314_icon.jpg
1343 ms
common_338_icon.jpg
1380 ms
common_213_icon.jpg
1617 ms
common_328_icon.jpg
1667 ms
px.png
1658 ms
pn.png
1777 ms
nv.png
1692 ms
qmenu.png
1917 ms
nv_a.png
1974 ms
search.png
1978 ms
pt_item.png
1929 ms
chart.png
2126 ms
titlebg.png
2150 ms
common_5655_icon.bmp
3878 ms
common_5550_icon.gif
1949 ms
common_1131_icon.gif
2007 ms
common_680_icon.bmp
3753 ms
collapsed_no.gif
2237 ms
common_1953_icon.gif
2277 ms
forum.gif
2020 ms
common_53_icon.gif
2226 ms
d636f32bef7b92fd1a4c3b05d8d681bf.jpg
1913 ms
nophoto.gif
2034 ms
9f4a8a54838e9d85cbcae290b455c4bc.jpg
2196 ms
common_extra.js
2638 ms
5679e659473638bf6fdcf16b815df1a5.jpg
2372 ms
49d7d78ab95adddc5d04acdf00069aad.jpg
2517 ms
306f3a2e93953f6da25127a577e0f413.jpg
2715 ms
afeb2a658b996094a909027b224e923b.jpg
2838 ms
85b32a3fa82de72b53cc86e76d8a4eed.jpg
3008 ms
5cd9f7e04fba531b3d286a8121700f50.jpg
3055 ms
23a2ed510bf5bdfe30cbcd6d5e740af4.jpg
3163 ms
dot.gif
3235 ms
sortnum.png
3232 ms
c.js
8157 ms
crystal2.js
680 ms
f.js
2589 ms
avatar.php
20385 ms
discuz_tips.js
480 ms
85_avatar_small.jpg
11138 ms
76_avatar_small.jpg
11307 ms
title.png
11383 ms
19_avatar_small.jpg
11553 ms
86_avatar_small.jpg
10940 ms
85_avatar_small.jpg
10817 ms
05_avatar_small.jpg
10760 ms
00_avatar_small.jpg
10958 ms
noavatar_small.gif
10490 ms
26_avatar_small.jpg
12411 ms
38_avatar_small.jpg
9762 ms
08_avatar_small.jpg
10113 ms
65_avatar_small.jpg
9420 ms
95_avatar_small.jpg
9736 ms
noavatar_small.gif
9868 ms
73_avatar_small.jpg
9399 ms
ad_close.gif
9559 ms
11_avatar_small.jpg
9543 ms
03_avatar_small.jpg
9453 ms
26_avatar_small.jpg
9285 ms
99_avatar_small.jpg
9565 ms
06_avatar_small.jpg
11573 ms
dcjm
957 ms
lview
506 ms
79_avatar_small.jpg
9208 ms
dcjm
1019 ms
h.js
2564 ms
18_avatar_small.jpg
9153 ms
noavatar_small.gif
9189 ms
41_avatar_small.jpg
8816 ms
dcjm
889 ms
noavatar_small.gif
8745 ms
dcjm
1094 ms
xuanfu_close.png
501 ms
noavatar_small.gif
8301 ms
adx.php
1159 ms
reduce_bd-logo1_oper.png
532 ms
u=662189644,3791736431&fm=76
1635 ms
u=1220490986,1734641401&fm=76
2790 ms
u=4145121219,3946490636&fm=76
3145 ms
u=756295746,3901080679&fm=76
7649 ms
u=1044407971,1445958440&fm=76
2428 ms
u=1583915054,2119113219&fm=76
2874 ms
u=881015465,1128160215&fm=76
2436 ms
adx.php
1296 ms
cube_1.jpg
481 ms
u=897475877,4216309806&fm=76
8159 ms
u=686788604,3755966190&fm=76
2219 ms
21.gif
1004 ms
hm.gif
416 ms
weiboshare.html
1395 ms
25_avatar_small.jpg
6773 ms
share_btn_iframe.js
13 ms
noavatar_small.gif
6037 ms
weiboshare.html
938 ms
95_avatar_small.jpg
5483 ms
08_avatar_small.jpg
5346 ms
app_iframe.css
287 ms
share_button.js
1829 ms
58_avatar_small.jpg
5065 ms
d636f32bef7b92fd1a4c3b05d8d681bf.jpg
5007 ms
nophoto.gif
4780 ms
9f4a8a54838e9d85cbcae290b455c4bc.jpg
4871 ms
5679e659473638bf6fdcf16b815df1a5.jpg
4560 ms
49d7d78ab95adddc5d04acdf00069aad.jpg
4637 ms
06_avatar_small.jpg
4396 ms
scrolltop.png
4616 ms
btn_trans.gif
1507 ms
transparent.gif
1815 ms
tmp.gif
1066 ms
shorten.json
1224 ms
closefeedback.min.js
254 ms
reduce_promotion_oper.png
493 ms
bd_logo.png
501 ms
bg_rb.png
522 ms
o.htm
1960 ms
hm.gif
899 ms
wh.js
757 ms
ac.js
544 ms
fp.htm
1315 ms
fp.htm
811 ms
lzc369.com SEO score
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lzc369.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 Lzc369.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.
lzc369.com
Open Graph description is not detected on the main page of Lzc 369. 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: