47.4 sec in total
2.3 sec
44.5 sec
600 ms
Visit wzsee.com now to see the best up-to-date Wzsee content for China and also check out these interesting facts you probably never knew about wzsee.com
温商网 - 温州经济新闻门户网,是报道温州经济,温商,温州商人,温州商机,温商商机,温州资讯,经济新闻,温州财经资讯,房产的全球温商资讯交流平台
Visit wzsee.comWe analyzed Wzsee.com page load time and found that the first response time was 2.3 sec and then it took 45.1 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 26 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
wzsee.com performance score
2269 ms
4709 ms
19580 ms
1178 ms
3592 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 28% of them (40 requests) were addressed to the original Wzsee.com, 17% (24 requests) were made to Img.wzsee.com and 10% (14 requests) were made to Epaper.wzsee.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Img.wzsee.com.
Page size can be reduced by 437.5 kB (39%)
1.1 MB
694.1 kB
In fact, the total size of Wzsee.com main page is 1.1 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. 40% of websites need less resources to load. Images take 541.5 kB which makes up the majority of the site volume.
Potential reduce by 72.0 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 72.0 kB or 81% of the original size.
Potential reduce by 32.8 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. Wzsee images are well optimized though.
Potential reduce by 246.2 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 246.2 kB or 62% of the original size.
Potential reduce by 86.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. Wzsee.com needs all CSS files to be minified and compressed as it can save up to 86.5 kB or 83% of the original size.
Number of requests can be reduced by 45 (41%)
110
65
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wzsee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wzsee.com
2269 ms
www.wzsee.com
4709 ms
jquery.min2.js
19580 ms
config.js
1178 ms
common.js
3592 ms
login.js
1184 ms
jquery.KinSlideshow-1.1.js
3760 ms
scroshow.js
1770 ms
home_2015.js
2437 ms
communal.js
2996 ms
jquery.marquee.js
3571 ms
stlye_2015.css
4262 ms
jquery.slideBox.css
6299 ms
js.php
1353 ms
js.php
1182 ms
js.php
1316 ms
api.php
7858 ms
jquery.slideBox.min.js
4192 ms
link_3.js
7022 ms
link_2.js
3764 ms
stat.php
807 ms
buttonLite.js
101 ms
cxy6428_b.jpg
3329 ms
20160408093046498.jpg
14400 ms
20160401100923807.png
20310 ms
20151217062204914.jpg
20311 ms
20151217055429918.jpg
5455 ms
20151217055235854.jpg
20310 ms
20151204014257269.jpg
3430 ms
20151204013756864.jpg
6993 ms
20151203052448688.jpg
20311 ms
20150317084855436.jpg
20311 ms
20150317083028698.jpg
20311 ms
20150317082453906.jpg
20311 ms
20150317081624373.jpg
20312 ms
20131021044147413.jpg
20312 ms
20141017024018822.jpg
20311 ms
20140718115029559.jpg
20312 ms
20150323011501493.png
20312 ms
20141231054735632.jpg
20313 ms
20150213105542949.jpg
20312 ms
20150126104422703.jpg
20312 ms
20150126103824341.jpg
20313 ms
20150112092122462.jpg
20313 ms
chenj6422_b.jpg
7049 ms
wry6421_b.jpg
5467 ms
llz6438_b.jpg
9498 ms
zyb6426_b.jpg
19819 ms
cxy6432_b.jpg
20312 ms
601-1_b.jpg
4322 ms
zyb6420_b.jpg
5564 ms
cxy649_b.jpg
7214 ms
cxy6430_b.jpg
9331 ms
hn648_b.jpg
10400 ms
%E7%8E%8B%E5%8A%9B_b.jpg
9346 ms
1_b.jpg
13093 ms
wzsb2016040801_b.jpg
20310 ms
logo_wsw.jpg
2991 ms
ico_2_2015.jpg
614 ms
fm1.jpg
20311 ms
ico_3_2015.jpg
611 ms
20130705021033628.jpg
20311 ms
pic1_1.jpg
6391 ms
pic1_2.jpg
1785 ms
pic1_3.jpg
1798 ms
pic1_4.jpg
2964 ms
pic1_5.jpg
7779 ms
iwzsee.jpg
5974 ms
20151230025808162.jpg
20308 ms
index.php
526 ms
sh_icon.jpg
3568 ms
blank
33 ms
index_icon_1.gif
4857 ms
news_bg1.jpg
6486 ms
news_bg3.jpg
7152 ms
20151103025815902.gif
20218 ms
20151103030037214.jpg
20185 ms
h2_1124.gif
8685 ms
ico_3_2015.gif
12585 ms
h2_1125.gif
8295 ms
164518gi7mimm32aryr0me.jpg
20183 ms
an3.jpg
9435 ms
index.php
3446 ms
index_icon1.png
8835 ms
icon_prod.png
14897 ms
h2_1126.gif
10055 ms
botTools.png
20130 ms
stat.htm
254 ms
core.php
946 ms
mobile.css
1578 ms
jquery-1.8.2.min.js
1651 ms
pic1.gif
789 ms
ico_scroll.png
15690 ms
bsStatic.js
57 ms
fingerprint2.min.js
63 ms
bs-engine.js
63 ms
bshare_box_sprite2.gif
35 ms
bshareS1.js
31 ms
background-opaque-dark.gif
29 ms
b0.png
64 ms
h.js
1884 ms
weiboShow.css
2963 ms
skin_default.css
2961 ms
gaea_1_19.js
22 ms
show.js
7 ms
suda.js
6 ms
21.gif
811 ms
b0.png
40 ms
hm.gif
801 ms
background-opaque-dark.png
579 ms
bshare_view
2168 ms
hm.gif
456 ms
1
96 ms
a716fd45gw1f2pduwbzheg20al07r1l2.gif
92 ms
8b207e62gw1f2pcf2qy21j20b40etae5.jpg
317 ms
71a79003jw1f2nwuk8av7j206g00q747.jpg
88 ms
71a79003jw1f2o5eil3dvj20b40d70tn.jpg
86 ms
6a918093jw1f2m0a13lllj20hs0dcq4k.jpg
85 ms
87e580degw1f2ljk27zqcj20m80et0w4.jpg
83 ms
icon_user.png
80 ms
btns_bg.png
79 ms
icon_follow.png
80 ms
71a79003jw1f2o5e26tj7j206g00q747.jpg
87 ms
71a79003jw1f2nwvz45qbj206g00q747.jpg
85 ms
71a79003jw1f2nwvlqbfbj20b407vjrw.jpg
86 ms
71a79003jw1f2lnycrb43j206g00q747.jpg
84 ms
bg_trans.png
8 ms
icon_tips.png
5 ms
a.gif
1242 ms
tmp.gif
1113 ms
cm.html
35 ms
pixel
1131 ms
rm.gif
1291 ms
cm.gif
1377 ms
t.gif
818 ms
cm.fastapi.net
1451 ms
cms.gif
1049 ms
cms.gif
813 ms
cms.gif
979 ms
cms.gif
863 ms
cms.gif
901 ms
cms.gif
1113 ms
m.gif
453 ms
cms.gif
366 ms
cms.gif
3086 ms
wzsee.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wzsee.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 Wzsee.com main page’s claimed encoding is gb2312. 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.
wzsee.com
Open Graph description is not detected on the main page of Wzsee. 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: