36 sec in total
6.8 sec
28.9 sec
335 ms
Click here to check amazing 198910 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about 198910.blog.163.com
Visit 198910.blog.163.comWe analyzed 198910.blog.163.com page load time and found that the first response time was 6.8 sec and then it took 29.2 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. 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.
198910.blog.163.com performance score
6776 ms
43 ms
34 ms
50 ms
60 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 198910.blog.163.com, 43% (42 requests) were made to B.bst.126.net and 17% (17 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 724.8 kB (66%)
1.1 MB
379.3 kB
In fact, the total size of 198910.blog.163.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. 30% of websites need less resources to load. Javascripts take 453.8 kB which makes up the majority of the site volume.
Potential reduce by 245.1 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 245.1 kB or 84% of the original size.
Potential reduce by 16.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. 198910 Blog 163 images are well optimized though.
Potential reduce by 313.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 313.1 kB or 69% of the original size.
Potential reduce by 150.2 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. 198910.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.2 kB or 82% of the original size.
Number of requests can be reduced by 52 (56%)
93
41
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 198910 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.
198910.blog.163.com
6776 ms
c.css
43 ms
nb.css
34 ms
banner1.jpg
50 ms
tab.jpg
60 ms
on.gif
59 ms
web_a1_a.gif
59 ms
bg_a.gif
61 ms
bg_a_l.gif
58 ms
web_a3.gif
59 ms
web_a2.gif
64 ms
web_a5.gif
64 ms
web_a4.gif
63 ms
web_a6.gif
64 ms
icon.png
44 ms
web_a1_l.gif
34 ms
6630133180817252049.jpg
2211 ms
1.0.0.js
178 ms
pc.js
55 ms
ph.js
54 ms
goodbloghead.png
16 ms
rssi.png
26 ms
lnkbar.png
29 ms
image.png
23 ms
arrow24.png
22 ms
newtopbaricon8.png
23 ms
web_a1.jpg
15 ms
web_a2_l.gif
15 ms
web_b.jpg
16 ms
xcode.png
20 ms
crossdomain.html
2277 ms
crossdomain.html
4202 ms
crossdomain.html
1386 ms
request.s
3034 ms
analyse.png
19834 ms
ava.s
3778 ms
loftericon.png
2104 ms
nb.css
30 ms
ava.s
1956 ms
background.gif
30 ms
player_02.gif
19 ms
player_06.gif
16 ms
player_16.gif
18 ms
player_17.gif
12 ms
stopping.gif
35 ms
player_23.gif
30 ms
timeline_1.gif
30 ms
player_29.gif
33 ms
analyse.png
19606 ms
analytics.js
516 ms
collect
156 ms
blogPhotoAd
20388 ms
close_01.png
133 ms
top_bg.png
130 ms
bottom_bg.png
133 ms
left_bg.png
132 ms
right_bg.png
129 ms
left_top.png
128 ms
right_top.png
334 ms
left_bottom.png
334 ms
right_bottom.png
335 ms
shadow.png
130 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
946 ms
HomeBeanNew.getFriends.dwr
1187 ms
HomeBeanNew.getAccessStatistics.dwr
5385 ms
UserBeanNew.getVisitor.dwr
1192 ms
NoteBeanNew.getNotesForPrev.dwr
1280 ms
BlogBeanNew.getRecentCommentsByOffset.dwr
3139 ms
MusicBeanNew.getPlayList.dwr
1523 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1976 ms
ava.s
457 ms
ava.s
463 ms
ava.s
859 ms
ava.s
812 ms
ava.s
915 ms
ava.s
1282 ms
ava.s
866 ms
ava.s
924 ms
ava.s
1232 ms
ava.s
1294 ms
ava.s
1296 ms
ava.s
1341 ms
ava.s
1390 ms
ava.s
1634 ms
ava.s
3363 ms
face56.gif
53 ms
face50.gif
55 ms
list_line.gif
36 ms
UserSpaceBean.getUserSpace.dwr
688 ms
AlbumBeanNew.getUserSpace.dwr
807 ms
sniff.png
903 ms
face8.gif
9 ms
34084870754695.js
428 ms
-1.gif
548 ms
251788170611656.js
666 ms
empty.png
11 ms
3141542215067846539.jpg
4265 ms
BgsBean.getBgsUserByUserId.dwr
819 ms
198910.blog.163.com SEO score
N/A
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 198910.blog.163.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), while the claimed language is Chinese. Our system also found out that 198910.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.
198910.blog.163.com
Open Graph description is not detected on the main page of 198910 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: