33.2 sec in total
5.6 sec
27.1 sec
486 ms
Click here to check amazing Ht 19820316 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about ht19820316.blog.163.com
Visit ht19820316.blog.163.comWe analyzed Ht19820316.blog.163.com page load time and found that the first response time was 5.6 sec and then it took 27.6 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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ht19820316.blog.163.com performance score
5584 ms
44 ms
75 ms
8 ms
11 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ht19820316.blog.163.com, 36% (28 requests) were made to B.bst.126.net and 21% (16 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.
Page size can be reduced by 594.5 kB (57%)
1.0 MB
449.3 kB
In fact, the total size of Ht19820316.blog.163.com main page is 1.0 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 449.0 kB which makes up the majority of the site volume.
Potential reduce by 125.4 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 125.4 kB or 82% of the original size.
Potential reduce by 9.3 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. Ht 19820316 Blog 163 images are well optimized though.
Potential reduce by 310.5 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 310.5 kB or 69% of the original size.
Potential reduce by 149.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. Ht19820316.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.4 kB or 82% of the original size.
Number of requests can be reduced by 42 (58%)
73
31
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ht 19820316 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 16 to 1 for JavaScripts and as a result speed up the page load time.
ht19820316.blog.163.com
5584 ms
c.css
44 ms
nb.css
75 ms
icon.png
8 ms
bg.jpg
11 ms
top.jpg
1389 ms
a1.gif
1191 ms
a3.gif
31 ms
lnkbar.png
43 ms
6630133180817252049.jpg
512 ms
image.png
8 ms
arrow24.png
16 ms
newtopbaricon8.png
15 ms
xcode.png
11 ms
1.0.0.js
106 ms
pc.js
32 ms
ph.js
29 ms
crossdomain.html
729 ms
crossdomain.html
611 ms
crossdomain.html
462 ms
request.s
620 ms
analyse.png
20364 ms
ava.s
8349 ms
loftericon.png
1029 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
765 ms
nb.css
36 ms
background.gif
11 ms
player_02.gif
7 ms
player_06.gif
11 ms
player_16.gif
9 ms
player_17.gif
11 ms
stopping.gif
19 ms
player_23.gif
13 ms
timeline_1.gif
13 ms
player_29.gif
12 ms
analyse.png
20151 ms
analytics.js
11 ms
collect
14 ms
SetupBeanNew.getResourceModulesData.dwr
1917 ms
HomeBeanNew.getAccessStatistics.dwr
1097 ms
HomeBeanNew.getMonthStatistics.dwr
1115 ms
HomeBeanNew.getWeatherCityCode.dwr
1095 ms
UserBeanNew.getVisitor.dwr
1109 ms
NoteBeanNew.getNotesForPrev.dwr
8715 ms
MusicBeanNew.getPlayList.dwr
1823 ms
NewsBean.getAllOrderedNews.dwr
4304 ms
BlogBeanNew.getBlogClasses.dwr
2958 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1679 ms
blogPhotoAd
19942 ms
close_01.png
22 ms
top_bg.png
19 ms
bottom_bg.png
25 ms
left_bg.png
35 ms
right_bg.png
30 ms
left_top.png
28 ms
right_top.png
29 ms
left_bottom.png
27 ms
right_bottom.png
38 ms
shadow.png
35 ms
BgsBean.getBgsUserByUserId.dwr
1537 ms
.gif
53 ms
ava.s
777 ms
ava.s
826 ms
ava.s
2374 ms
ava.s
4976 ms
ava.s
1164 ms
ava.s
5099 ms
ava.s
1577 ms
ava.s
1820 ms
ava.s
2424 ms
ava.s
12527 ms
ava.s
2770 ms
ava.s
4484 ms
ava.s
3194 ms
ava.s
4962 ms
ava.s
5657 ms
list_line.gif
16 ms
face42.gif
308 ms
ht19820316.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 Ht19820316.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 Ht19820316.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.
ht19820316.blog.163.com
Open Graph description is not detected on the main page of Ht 19820316 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: