27 sec in total
3.3 sec
23.2 sec
501 ms
Welcome to wenbei.blogchina.com homepage info - get ready to check Wenbei Blogchina best content for China right away, or after learning these important things about wenbei.blogchina.com
种过地,当过兵,做过工,现退休。
Visit wenbei.blogchina.comWe analyzed Wenbei.blogchina.com page load time and found that the first response time was 3.3 sec and then it took 23.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.
wenbei.blogchina.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value2.4 s
92/100
25%
Value5.9 s
48/100
10%
Value20 ms
100/100
30%
Value0.08
94/100
15%
Value2.8 s
97/100
10%
3301 ms
626 ms
3681 ms
966 ms
3683 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wenbei.blogchina.com, 29% (35 requests) were made to Js1.blogchina.com and 17% (21 requests) were made to Avatar.blogchina.com. The less responsive or slowest element that took the longest time to load (8.9 sec) relates to the external source Pos.baidu.com.
Page size can be reduced by 463.9 kB (53%)
877.7 kB
413.8 kB
In fact, the total size of Wenbei.blogchina.com main page is 877.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. 40% of websites need less resources to load. Javascripts take 504.9 kB which makes up the majority of the site volume.
Potential reduce by 65.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. This page needs HTML code to be minified as it can gain 10.6 kB, which is 13% 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 65.0 kB or 83% of the original size.
Potential reduce by 7.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. Wenbei Blogchina images are well optimized though.
Potential reduce by 325.1 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 325.1 kB or 64% of the original size.
Potential reduce by 66.4 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. Wenbei.blogchina.com needs all CSS files to be minified and compressed as it can save up to 66.4 kB or 80% of the original size.
Number of requests can be reduced by 65 (56%)
116
51
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wenbei Blogchina. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wenbei.blogchina.com
3301 ms
top.css
626 ms
common.css
3681 ms
index.css
966 ms
gonggao.css
3683 ms
m.js
1023 ms
vamaker.js
6398 ms
c.js
1021 ms
jquery-1.7.2.min.js
1956 ms
jquery.pin.min.js
1250 ms
swfobject.js
1946 ms
web_socket.js
1886 ms
top.js
1609 ms
common.js
2402 ms
home.js
1784 ms
index.js
1893 ms
MsgBox.js
2105 ms
54320da6fb01fdc09d2df867bac36cd3!big
546 ms
bodyimg.png
717 ms
toTop_03.png
710 ms
logo.jpg
2098 ms
input_bg_03.jpg
804 ms
login_sub_03.jpg
971 ms
new_reg.jpg
1008 ms
rs2.png
1016 ms
i_c_num_bg_11.jpg
1146 ms
erweima_03.jpg
1615 ms
m_l_text_bg_24.jpg
2222 ms
m_l_day_23.jpg
2325 ms
m_l_t_more_11.jpg
1335 ms
column_bg_06.jpg
3328 ms
scom
1849 ms
default60.html
18 ms
0f0005DvC00dQdFpKT7tEs.gif
805 ms
date_bg_14.jpg
321 ms
ad-tag.png
1405 ms
b
4905 ms
scom
378 ms
scom
793 ms
scom
984 ms
scom
376 ms
scom
457 ms
scom
2940 ms
scom
457 ms
scom
479 ms
h.js
1035 ms
scom
8941 ms
hm.gif
333 ms
embed.js
249 ms
635 ms
3642 ms
3550 ms
3542 ms
3567 ms
3559 ms
3537 ms
3874 ms
3864 ms
3874 ms
page_li_bg1_03.jpg
326 ms
page_li_bg2_03.jpg
330 ms
counts.json
1975 ms
sync.htm
774 ms
ctm3.js
687 ms
show_ads.js
148 ms
ca-pub-5090666702087250.js
289 ms
zrt_lookup.html
441 ms
show_ads_impl.js
363 ms
ads
258 ms
sync_pos.htm
355 ms
osd.js
142 ms
embed.default.css
123 ms
vamaker_return.html
1167 ms
sync2r.htm
900 ms
b
933 ms
lanmu_bg.jpg
372 ms
date_tit_07.jpg
370 ms
1a17a8de457c7d74c16626bb2fae36b0!middle
317 ms
c49150162856aafdbfd6ca7972264296!middle
109 ms
3b3b5bfd7ffc992be972e3e310a1c0b6!middle
106 ms
009ecd2bb7965f080bba582529f07f37!middle
128 ms
d8538fbeabf5054116eb495a42c14d8c!middle
105 ms
4b727e6a03aa939f3773d062c7563628!middle
575 ms
d38ac0c7fa4438acf7ba759d685f4b87!middle
156 ms
1050419e941b800536f56a5ccddca0e9!middle
450 ms
8fd73bef8cb38017dcfcb70c4b921e72!middle
147 ms
772ee4d7abb56574859055d2e53c065e!middle
540 ms
4fae2728ec6e9b25cc7755fe2fcb53e4!middle
210 ms
86608b796127caf4589797be3a9b4b01!middle
218 ms
1dbec4182a2545b5e8154ae7751d784a!middle
260 ms
8032f5f50a9158412e577a52d7a77df4!middle
679 ms
b7fb290d2520d276a56634c976b3a1fb!middle
896 ms
378dd4b9fa8d932f63b9945e9fd0e8b2!middle
591 ms
fb7b34d1ccb2db6fe12e832d1f91e5b4!middle
476 ms
92fd5a187e4e56429caf0ac58a57c0b7!middle
491 ms
34c1578814fa4bbecb20b0a2af927bd5!middle
524 ms
37ed4d963c8cba2a5c8f3a068991582f!middle
545 ms
fenxiang4_10.jpg
1250 ms
fenxiang2_10.jpg
668 ms
bdzh_tm.png
391 ms
photoimg.jpg
5178 ms
cpc.js
334 ms
cpcunion
1989 ms
J.min.js
33 ms
turns.center.js
58 ms
bot-patch.min.js
95 ms
click.min.js
93 ms
logo.jpg
782 ms
53ba3868Nea2f6c42.png
124 ms
mgets
1772 ms
rBEhVFJYrDAIAAAAAAAHoRFcOGsAAECrwP_uYQAAAe5174.png
103 ms
logo.jpg
1743 ms
549b84acNc8c7a33e.jpg
104 ms
s.htm
816 ms
sync.html
731 ms
55e40d3fN2a01189f.png
104 ms
o.htm
360 ms
5624b925N751250b1.jpg
38 ms
wh.js
770 ms
ac.js
505 ms
hm.gif
1196 ms
fp.htm
728 ms
wenbei.blogchina.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wenbei.blogchina.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
wenbei.blogchina.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wenbei.blogchina.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wenbei.blogchina.com 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.
wenbei.blogchina.com
Open Graph description is not detected on the main page of Wenbei Blogchina. 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: