14.1 sec in total
1.5 sec
11.9 sec
769 ms
Visit luhluhl.blog.163.com now to see the best up-to-date Luhluhl Blog 163 content for China and also check out these interesting facts you probably never knew about luhluhl.blog.163.com
Visit luhluhl.blog.163.comWe analyzed Luhluhl.blog.163.com page load time and found that the first response time was 1.5 sec and then it took 12.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
luhluhl.blog.163.com performance score
1461 ms
15 ms
858 ms
658 ms
47 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Luhluhl.blog.163.com, 25% (17 requests) were made to Os.blog.163.com and 18% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 608.3 kB (40%)
1.5 MB
918.5 kB
In fact, the total size of Luhluhl.blog.163.com main page is 1.5 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. Images take 710.6 kB which makes up the majority of the site volume.
Potential reduce by 90.6 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 90.6 kB or 80% of the original size.
Potential reduce by 10.1 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. Luhluhl 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.1 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. Luhluhl.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 82% of the original size.
Number of requests can be reduced by 29 (45%)
64
35
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Luhluhl 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 12 to 1 for JavaScripts and as a result speed up the page load time.
luhluhl.blog.163.com
1461 ms
c.css
15 ms
b.css
858 ms
6630133180817252049.jpg
658 ms
xcode.png
47 ms
1.0.0.js
99 ms
pc.js
53 ms
ph.js
54 ms
2580562586484949617.jpg
9997 ms
icon.png
150 ms
2580562586484949622.jpg
2927 ms
2580562586484949619.jpg
760 ms
2580562586484949621.jpg
1127 ms
lnkbar.png
145 ms
image.png
146 ms
arrow24.png
146 ms
newtopbaricon8.png
146 ms
crossdomain.html
2362 ms
crossdomain.html
623 ms
crossdomain.html
864 ms
request.s
791 ms
analyse.png
824 ms
empty.png
46 ms
2141180147938495138.jpg
767 ms
ava.s
419 ms
loftericon.png
394 ms
analyse.png
618 ms
analytics.js
40 ms
collect
18 ms
blogPhotoAd
391 ms
close_01.png
7 ms
top_bg.png
12 ms
bottom_bg.png
12 ms
left_bg.png
13 ms
right_bg.png
15 ms
left_top.png
13 ms
right_top.png
13 ms
left_bottom.png
15 ms
right_bottom.png
14 ms
shadow.png
10 ms
r
580 ms
ad
941 ms
HomeBeanNew.getAccessStatistics.dwr
1001 ms
HomeBeanNew.getWeatherCityCode.dwr
1598 ms
UserBeanNew.getVisitor.dwr
1567 ms
BlogBeanNew.getBlogClasses.dwr
1972 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2295 ms
close2.png
7 ms
jquery-1.4.2.js
19 ms
ad.bid.material_367e2deeea8641f19635d1be38139fea
2770 ms
BgsBean.getBgsUserByUserId.dwr
1443 ms
ava.s
363 ms
ava.s
719 ms
ava.s
721 ms
ava.s
747 ms
ava.s
795 ms
ava.s
2747 ms
ava.s
941 ms
ava.s
1077 ms
ava.s
1075 ms
ava.s
2342 ms
ava.s
1159 ms
ava.s
3316 ms
ava.s
1440 ms
ava.s
1441 ms
ava.s
1559 ms
.gif
305 ms
luhluhl.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 Luhluhl.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 Luhluhl.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.
luhluhl.blog.163.com
Open Graph description is not detected on the main page of Luhluhl 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: