12.3 sec in total
2.9 sec
9.1 sec
373 ms
Click here to check amazing Lw 13863269753 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about lw13863269753.blog.163.com
Visit lw13863269753.blog.163.comWe analyzed Lw13863269753.blog.163.com page load time and found that the first response time was 2.9 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lw13863269753.blog.163.com performance score
2863 ms
13 ms
11 ms
20 ms
9 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Lw13863269753.blog.163.com, 43% (34 requests) were made to B.bst.126.net and 14% (11 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Img.ph.126.net.
Page size can be reduced by 605.8 kB (47%)
1.3 MB
696.8 kB
In fact, the total size of Lw13863269753.blog.163.com main page is 1.3 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. 50% of websites need less resources to load. Javascripts take 527.3 kB which makes up the majority of the site volume.
Potential reduce by 80.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 80.4 kB or 80% of the original size.
Potential reduce by 12.9 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. Lw 13863269753 Blog 163 images are well optimized though.
Potential reduce by 362.7 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 362.7 kB or 69% of the original size.
Potential reduce by 149.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. Lw13863269753.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.
Number of requests can be reduced by 46 (59%)
78
32
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lw 13863269753 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 14 to 1 for JavaScripts and as a result speed up the page load time.
lw13863269753.blog.163.com
2863 ms
c.css
13 ms
nb.css
11 ms
pic_01.jpg
20 ms
pic_04.png
9 ms
pic_03.jpg
238 ms
pic_07.gif
13 ms
pic_05.gif
16 ms
pic_06.gif
9 ms
pic_11.gif
13 ms
pic_12.gif
17 ms
pic_08.gif
15 ms
pic_09.gif
13 ms
pic_10.gif
16 ms
pic_02.jpg
17 ms
icon.png
8 ms
lnkbar.png
7 ms
image.png
12 ms
6630133180817252049.jpg
6245 ms
xcode.png
13 ms
1.0.0.js
80 ms
pc.js
22 ms
ph.js
17 ms
arrow24.png
9 ms
newtopbaricon8.png
9 ms
crossdomain.html
860 ms
crossdomain.html
1201 ms
crossdomain.html
1147 ms
request.s
563 ms
analyse.png
1262 ms
ava.s
5722 ms
loftericon.png
1640 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
1744 ms
nb.css
25 ms
BlogCircleBean.getUserShowCircles.dwr
1240 ms
ava.s
889 ms
background.gif
299 ms
player_02.gif
467 ms
player_06.gif
2210 ms
player_16.gif
1280 ms
player_17.gif
5 ms
stopping.gif
18 ms
player_23.gif
19 ms
timeline_1.gif
94 ms
player_29.gif
303 ms
analyse.png
1270 ms
analytics.js
7 ms
collect
13 ms
SetupBeanNew.getResourceModulesData.dwr
4812 ms
HomeBeanNew.getFriends.dwr
1342 ms
HomeBeanNew.getAccessStatistics.dwr
1288 ms
NoteBeanNew.getNotesForPrev.dwr
2214 ms
MusicBeanNew.getPlayList.dwr
3260 ms
HomeBeanNew.getClassifyModuleData.dwr
4128 ms
blogPhotoAd
641 ms
close_01.png
12 ms
top_bg.png
10 ms
bottom_bg.png
12 ms
left_bg.png
13 ms
right_bg.png
13 ms
left_top.png
14 ms
right_top.png
15 ms
left_bottom.png
15 ms
right_bottom.png
16 ms
shadow.png
12 ms
r
1103 ms
ava.s
454 ms
ava.s
871 ms
ava.s
872 ms
ava.s
915 ms
ava.s
2662 ms
ava.s
2504 ms
ava.s
1337 ms
ava.s
1317 ms
close2.png
3 ms
ad
1160 ms
list_line.gif
14 ms
jquery-1.4.2.js
10 ms
0316ykt-300-250.jpg
853 ms
ava.s
436 ms
lw13863269753.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 Lw13863269753.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 Lw13863269753.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.
lw13863269753.blog.163.com
Open Graph description is not detected on the main page of Lw 13863269753 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: