24.2 sec in total
1.8 sec
21.8 sec
584 ms
Visit litie2003.blog.163.com now to see the best up-to-date Litie 2003 Blog 163 content for China and also check out these interesting facts you probably never knew about litie2003.blog.163.com
怀念我的妻子顾琪,【转载】中国人要多买日本车,中国人要多买日本车,凤凰古城收门票是一场掠夺,克强经济学,重回市场的轨道,在8点20分打假央视3.15晚会,当蒙牛被泼粪,谁来管央企?,理解“以人查房”,重建改革共识,官员财产公开,让部分领导先走!,李铁的网易博客,南方周末评论员,思想家就是与流行的谬误作战。
Visit litie2003.blog.163.comWe analyzed Litie2003.blog.163.com page load time and found that the first response time was 1.8 sec and then it took 22.4 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
litie2003.blog.163.com performance score
1780 ms
18 ms
45 ms
17 ms
16 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Litie2003.blog.163.com, 43% (30 requests) were made to B.bst.126.net and 16% (11 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Img.ph.126.net.
Page size can be reduced by 599.2 kB (59%)
1.0 MB
422.6 kB
In fact, the total size of Litie2003.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. 45% of websites need less resources to load. Javascripts take 492.4 kB which makes up the majority of the site volume.
Potential reduce by 105.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 105.4 kB or 81% of the original size.
Potential reduce by 16.6 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. Litie 2003 Blog 163 images are well optimized though.
Potential reduce by 327.9 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 327.9 kB or 67% of the original size.
Potential reduce by 149.3 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. Litie2003.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.3 kB or 82% of the original size.
Number of requests can be reduced by 39 (57%)
68
29
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Litie 2003 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 13 to 1 for JavaScripts and as a result speed up the page load time.
litie2003.blog.163.com
1780 ms
c.css
18 ms
nb.css
45 ms
blog_rec.png
17 ms
top_banner.jpg
16 ms
bg_tab.jpg
13 ms
bg_top.gif
14 ms
bg_web_a.jpg
25 ms
bg_web_f_g.gif
13 ms
bg_web_f_c.gif
24 ms
bg_web_vv.gif
49 ms
bg_web_f_b1.gif
68 ms
icon.png
67 ms
6630133180817252049.jpg
20011 ms
1.0.0.js
80 ms
pc.js
76 ms
ph.js
72 ms
goodbloghead.png
57 ms
rssi.png
63 ms
lnkbar.png
64 ms
image.png
67 ms
arrow24.png
63 ms
newtopbaricon8.png
66 ms
bg_web_f_d1.gif
63 ms
bg_web_f_h.gif
57 ms
bg_web_i.gif
66 ms
bg_web_g1.gif
61 ms
bg_web_f_b.gif
62 ms
bg_web_f_e.gif
60 ms
bg_web_f_d.gif
69 ms
bg_web_f_k.gif
67 ms
bg_web_b.jpg
65 ms
xcode.png
65 ms
crossdomain.html
2064 ms
crossdomain.html
737 ms
crossdomain.html
6631 ms
request.s
934 ms
analyse.png
820 ms
empty.png
39 ms
ava.s
759 ms
ava.s
1107 ms
loftericon.png
1605 ms
analyse.png
821 ms
analytics.js
8 ms
collect
13 ms
UserSpaceBean.getUserSpace.dwr
770 ms
blogPhotoAd
6138 ms
close_01.png
10 ms
top_bg.png
10 ms
bottom_bg.png
9 ms
left_bg.png
9 ms
right_bg.png
11 ms
left_top.png
9 ms
right_top.png
9 ms
left_bottom.png
15 ms
right_bottom.png
11 ms
shadow.png
9 ms
62672173077165.js
413 ms
-1.gif
11 ms
241892565964220.js
563 ms
HomeBeanNew.getAccessStatistics.dwr
794 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1040 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
6344 ms
968836869839077472.jpg
419 ms
BgsBean.getBgsUserByUserId.dwr
5963 ms
r
1908 ms
close2.png
14 ms
ad
1501 ms
jquery-1.4.2.js
27 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1606 ms
litie2003.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 Litie2003.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 Litie2003.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.
litie2003.blog.163.com
Open Graph description is not detected on the main page of Litie 2003 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: