9.5 sec in total
251 ms
8.9 sec
295 ms
Visit wosetu.com now to see the best up-to-date Wosetu content for China and also check out these interesting facts you probably never knew about wosetu.com
Visit wosetu.comWe analyzed Wosetu.com page load time and found that the first response time was 251 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wosetu.com performance score
251 ms
124 ms
129 ms
133 ms
321 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 78% of them (69 requests) were addressed to the original Wosetu.com, 7% (6 requests) were made to Bdimg.share.baidu.com and 7% (6 requests) were made to Su.bdimg.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source S56.cnzz.com.
Page size can be reduced by 414.9 kB (20%)
2.1 MB
1.7 MB
In fact, the total size of Wosetu.com main page is 2.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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 40.9 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 40.9 kB or 83% of the original size.
Potential reduce by 140.4 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. Wosetu images are well optimized though.
Potential reduce by 221.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 221.8 kB or 65% of the original size.
Potential reduce by 11.8 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. Wosetu.com needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 68% of the original size.
Number of requests can be reduced by 19 (22%)
86
67
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wosetu. 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.
wosetu.com
251 ms
ankcss.css
124 ms
common.css
129 ms
newindex.css
133 ms
jquery-1.8.1.min.js
321 ms
tab.js
134 ms
jquery.min.js
259 ms
jquery.lazyload.js
186 ms
95.js
192 ms
102.js
197 ms
tongji.js
143 ms
main_bg.jpg
195 ms
logo.jpg
71 ms
20160214155743245_S.jpg
74 ms
20160203164256831_S.jpg
75 ms
20160202170237458_S.jpg
73 ms
20160120151148970_S.jpg
71 ms
20160119150104212_S.jpg
134 ms
20160118155303103_S.jpg
140 ms
20160115155458733_S.jpg
141 ms
20160113154446009_S.jpg
138 ms
20160111152648329_S.jpg
138 ms
20160107161014342_S.jpg
199 ms
20160106162228894_S.jpg
204 ms
20160104155212472_S.jpg
200 ms
20151229154159301_S.jpg
205 ms
20151203145117450_S.jpg
202 ms
20151126145714760_S.jpg
255 ms
20151119143336426.jpg
650 ms
2011041211091308_S.jpg
264 ms
2011051214231714_S.jpg
266 ms
2011042611470527_S.jpg
267 ms
20160201162101409_S.jpg
267 ms
20160129163715678_S.jpg
318 ms
20160128153042656_S.jpg
330 ms
2012121715435652_S.jpg
331 ms
2012020120575909_S.jpg
333 ms
2011120818520769_S.jpg
334 ms
2012031819494775_S.jpg
382 ms
2011052414250844_S.jpg
392 ms
2011013015323841_S.jpg
395 ms
20151223153211212_S.jpg
397 ms
20151215153847575_S.jpg
397 ms
20151204152647787_S.jpg
446 ms
2011052514472499_S.jpg
455 ms
2011123118515529_S.jpg
459 ms
shell_v2.js
610 ms
2012042609123371_S.jpg
452 ms
f.js
710 ms
2010081302492397_S.jpg
401 ms
2011051113345489_S.jpg
447 ms
2011051214282976_S.jpg
456 ms
2011050915595810_S.jpg
459 ms
20121218150320567_S.jpg
461 ms
2012051711570377_S.jpg
402 ms
20160118155721178_S.jpg
445 ms
20160113151735456_S.jpg
453 ms
20160105160217269_S.jpg
458 ms
20160105155201395_S.jpg
459 ms
20160105152250124_S.jpg
410 ms
20151222160459847.jpg
453 ms
nav.jpg
455 ms
search.jpg
458 ms
search_22.jpg
461 ms
search_24.jpg
460 ms
bds_s_v2.js
813 ms
ls.js
239 ms
todaynews.jpg
69 ms
lmfl.gif
66 ms
title_bg.gif
67 ms
line_40.jpg
66 ms
yqlj.jpg
67 ms
stat.php
2368 ms
ls_flowbar.js
242 ms
home
614 ms
bdsstyle.css
229 ms
getnum
518 ms
is_32.png
1127 ms
sc.png
469 ms
jquery_a4373ccd.js
508 ms
arrow_left_60_e700a3bb.png
261 ms
arrow_left_50_1dfda915.png
492 ms
stat.htm
167 ms
core.php
1953 ms
9.gif
1015 ms
grey.gif
67 ms
logger.js
238 ms
app.gif
2172 ms
wosetu.com SEO score
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wosetu.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 Wosetu.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.
wosetu.com
Open Graph description is not detected on the main page of Wosetu. 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: