27.7 sec in total
2.3 sec
24.6 sec
765 ms
Visit lypp07.blog.163.com now to see the best up-to-date Lypp 07 Blog 163 content for China and also check out these interesting facts you probably never knew about lypp07.blog.163.com
Visit lypp07.blog.163.comWe analyzed Lypp07.blog.163.com page load time and found that the first response time was 2.3 sec and then it took 25.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 were 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lypp07.blog.163.com performance score
2250 ms
473 ms
3182 ms
3477 ms
2525 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Lypp07.blog.163.com, 20% (19 requests) were made to B.bst.126.net and 18% (17 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Img0.ph.126.net.
Page size can be reduced by 659.8 kB (35%)
1.9 MB
1.2 MB
In fact, the total size of Lypp07.blog.163.com main page is 1.9 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 133.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 133.4 kB or 83% of the original size.
Potential reduce by 18.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. Lypp 07 Blog 163 images are well optimized though.
Potential reduce by 358.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 358.5 kB or 69% of the original size.
Potential reduce by 149.6 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. Lypp07.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 82% of the original size.
Number of requests can be reduced by 37 (43%)
86
49
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lypp 07 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.
lypp07.blog.163.com
2250 ms
c.css
473 ms
b.css
3182 ms
6631232692443089187.png
3477 ms
6619559177491765093.png
2525 ms
6630874251653724599.jpg
1524 ms
2828542040983425201.jpg
20151 ms
6630221141746584649.jpg
2838 ms
6630133180817252049.jpg
3334 ms
xcode.png
289 ms
1.0.0.js
365 ms
pc.js
528 ms
ph.js
563 ms
4289678645072007128.jpg
20026 ms
icon.png
186 ms
lnkbar.png
201 ms
image.png
202 ms
arrow24.png
200 ms
newtopbaricon8.png
199 ms
5118622451484105495.jpg
20008 ms
5404882502798678038.jpg
20008 ms
5404882502798678145.jpg
20008 ms
5118622451484105527.jpg
20008 ms
5118622451484105561.jpg
20007 ms
crossdomain.html
887 ms
crossdomain.html
4606 ms
crossdomain.html
888 ms
request.s
3758 ms
analyse.png
764 ms
ava.s
11354 ms
loftericon.png
439 ms
nb.css
118 ms
background.gif
29 ms
player_02.gif
72 ms
player_06.gif
71 ms
player_16.gif
71 ms
player_17.gif
72 ms
player_23.gif
88 ms
timeline_1.gif
88 ms
player_29.gif
149 ms
analyse.png
724 ms
analytics.js
38 ms
collect
29 ms
SetupBeanNew.getCustomModulesData.dwr
5097 ms
HomeBeanNew.getAccessStatistics.dwr
1475 ms
UserBeanNew.getVisitor.dwr
1488 ms
BlogBeanNew.getHostHotBlogs.dwr
1438 ms
BlogBeanNew.getRecentBlogs.dwr
3397 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
5671 ms
blogPhotoAd
1597 ms
close_01.png
113 ms
top_bg.png
110 ms
bottom_bg.png
108 ms
left_bg.png
107 ms
right_bg.png
126 ms
left_top.png
106 ms
right_top.png
130 ms
left_bottom.png
130 ms
right_bottom.png
130 ms
shadow.png
224 ms
BgsBean.getBgsUserByUserId.dwr
882 ms
ava.s
793 ms
ava.s
969 ms
ava.s
1531 ms
ava.s
1651 ms
ava.s
7136 ms
ava.s
2052 ms
ava.s
4158 ms
ava.s
2583 ms
ava.s
3125 ms
ava.s
3049 ms
ava.s
9029 ms
ava.s
5412 ms
ava.s
5655 ms
ava.s
4681 ms
ava.s
7067 ms
r
739 ms
ad
1684 ms
close2.png
47 ms
PhotoBlogBean.getHeadPic.dwr
826 ms
jquery-1.4.2.js
1264 ms
6630657647863145193.jpg
699 ms
6630216743699927224.jpg
4560 ms
2843460214749087438.jpg
2192 ms
1161084278949497934.jpg
2062 ms
6631300862163644628.jpg
566 ms
6631223896349717341.jpg
1616 ms
6631396519675278080.jpg
1151 ms
6631349240675283960.jpg
1146 ms
6630128782769722638.jpg
1028 ms
6630103494002285533.jpg
1999 ms
6631283269977600763.jpg
1741 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
6607 ms
6630203549560410554.jpg
1395 ms
6630876450677074576.jpg
1325 ms
lypp07.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 Lypp07.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 Lypp07.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.
lypp07.blog.163.com
Open Graph description is not detected on the main page of Lypp 07 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: