27 sec in total
2.4 sec
24.1 sec
497 ms
Welcome to heimajava.blog.163.com homepage info - get ready to check Heimajava Blog 163 best content for China right away, or after learning these important things about heimajava.blog.163.com
Visit heimajava.blog.163.comWe analyzed Heimajava.blog.163.com page load time and found that the first response time was 2.4 sec and then it took 24.6 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.
heimajava.blog.163.com performance score
2403 ms
11 ms
3083 ms
1109 ms
830 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Heimajava.blog.163.com, 25% (21 requests) were made to Os.blog.163.com and 23% (19 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (19.4 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 605.1 kB (52%)
1.2 MB
564.8 kB
In fact, the total size of Heimajava.blog.163.com main page is 1.2 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. 30% of websites need less resources to load. Javascripts take 521.3 kB which makes up the majority of the site volume.
Potential reduce by 85.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 85.8 kB or 79% of the original size.
Potential reduce by 9.2 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. Heimajava Blog 163 images are well optimized though.
Potential reduce by 358.3 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 358.3 kB or 69% of the original size.
Potential reduce by 151.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. Heimajava.blog.163.com needs all CSS files to be minified and compressed as it can save up to 151.8 kB or 82% of the original size.
Number of requests can be reduced by 36 (43%)
83
47
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Heimajava Blog 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
heimajava.blog.163.com
2403 ms
c.css
11 ms
b.css
3083 ms
1418352407745229409.png
1109 ms
6630133180817252049.jpg
830 ms
xcode.png
422 ms
1.0.0.js
109 ms
pc.js
388 ms
ph.js
402 ms
5774177672242723020.jpg
7854 ms
icon.png
86 ms
5783466346474172233.jpg
2178 ms
5783466346474172116.jpg
18690 ms
5783466346474172115.jpg
1587 ms
5783466346474172117.jpg
1751 ms
5774177672242723043.jpg
3517 ms
5783466346474172118.jpg
2620 ms
5783466346474172131.jpg
4879 ms
5783466346474172119.jpg
7318 ms
5783466346474172121.jpg
3837 ms
5783466346474172120.jpg
4858 ms
5783466346474172189.jpg
5166 ms
5783466346474172079.jpg
9075 ms
5783466346474172083.jpg
7387 ms
5783466346474172259.jpg
19381 ms
5783466346474172086.jpg
7750 ms
5783466346474172175.jpg
10148 ms
5783466346474172180.jpg
10030 ms
5783466346474172179.jpg
8734 ms
lnkbar.png
80 ms
image.png
79 ms
arrow24.png
80 ms
newtopbaricon8.png
80 ms
crossdomain.html
861 ms
crossdomain.html
919 ms
crossdomain.html
1866 ms
request.s
874 ms
analyse.png
1159 ms
ava.s
1099 ms
loftericon.png
363 ms
ava.s
863 ms
analyse.png
2577 ms
analytics.js
13 ms
collect
13 ms
HomeBeanNew.getFriends.dwr
926 ms
UserBeanNew.getVisitor.dwr
4526 ms
NoteBeanNew.getNotesForPrev.dwr
2523 ms
HomeBeanNew.getClassifyModuleData.dwr
1237 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1273 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1678 ms
blogPhotoAd
433 ms
close_01.png
39 ms
top_bg.png
43 ms
bottom_bg.png
46 ms
left_bg.png
46 ms
right_bg.png
45 ms
left_top.png
45 ms
right_top.png
48 ms
left_bottom.png
47 ms
right_bottom.png
48 ms
shadow.png
46 ms
ava.s
518 ms
ava.s
2099 ms
r
902 ms
ava.s
687 ms
ad
10037 ms
close2.png
4 ms
jquery-1.4.2.js
40 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
6779 ms
ava.s
929 ms
ava.s
2155 ms
ava.s
374 ms
ava.s
2865 ms
ava.s
2040 ms
ava.s
1068 ms
ava.s
3083 ms
ava.s
3009 ms
ava.s
1560 ms
ava.s
2006 ms
ava.s
2462 ms
ava.s
2454 ms
ava.s
3067 ms
ava.s
3325 ms
ava.s
4481 ms
heimajava.blog.163.com SEO score
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heimajava.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Heimajava.blog.163.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.
heimajava.blog.163.com
Open Graph description is not detected on the main page of Heimajava Blog 163. 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: