20.8 sec in total
2.1 sec
18.5 sec
215 ms
Visit lzy3169421.blog.163.com now to see the best up-to-date Lzy 3169421 Blog 163 content for China and also check out these interesting facts you probably never knew about lzy3169421.blog.163.com
Visit lzy3169421.blog.163.comWe analyzed Lzy3169421.blog.163.com page load time and found that the first response time was 2.1 sec and then it took 18.7 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.
lzy3169421.blog.163.com performance score
2134 ms
14 ms
2618 ms
5481 ms
1960 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Lzy3169421.blog.163.com, 29% (19 requests) were made to Img.bimg.126.net and 15% (10 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (14.1 sec) relates to the external source T.163.com.
Page size can be reduced by 629.6 kB (60%)
1.0 MB
413.6 kB
In fact, the total size of Lzy3169421.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. 30% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.
Potential reduce by 96.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 96.4 kB or 79% of the original size.
Potential reduce by 22.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. Obviously, Lzy 3169421 Blog 163 needs image optimization as it can save up to 22.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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 152.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. Lzy3169421.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.1 kB or 82% of the original size.
Number of requests can be reduced by 39 (61%)
64
25
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lzy 3169421 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 8 to 1 for JavaScripts and as a result speed up the page load time.
lzy3169421.blog.163.com
2134 ms
c.css
14 ms
b.css
2618 ms
201614112250554.gif
5481 ms
6598263836345123468.png
1960 ms
6598296821693895184.png
1371 ms
09211004-ca84a7abec034e16991a2a69cebe4024.png
6124 ms
6598076919368047007.png
1446 ms
1995094635025983367.png
2397 ms
6630133180817252049.jpg
650 ms
xcode.png
17 ms
1.0.0.js
99 ms
pc.js
26 ms
ph.js
23 ms
5785436671311429286.jpg
849 ms
icon.png
45 ms
lnkbar.png
41 ms
image.png
44 ms
arrow24.png
43 ms
newtopbaricon8.png
42 ms
5785436671311429285.jpg
565 ms
5774459147219844167.jpg
633 ms
5774459147219844166.jpg
708 ms
5774459147219844169.jpg
849 ms
5774459147219844173.jpg
960 ms
5774459147219844177.jpg
1063 ms
5774459147219844246.jpg
1140 ms
5774459147219844249.jpg
1151 ms
5774459147219844247.jpg
1331 ms
5774459147219844185.jpg
1472 ms
5774459147219844184.jpg
1449 ms
5774459147219844186.jpg
1459 ms
5774459147219844187.jpg
1687 ms
5774459147219844188.jpg
1760 ms
5774459147219844189.jpg
1768 ms
5774459147219844191.jpg
1902 ms
5774459147219844190.jpg
2854 ms
5785436671311429283.jpg
2748 ms
crossdomain.html
1975 ms
crossdomain.html
843 ms
crossdomain.html
14107 ms
request.s
811 ms
analyse.png
748 ms
ava.s
2102 ms
loftericon.png
1678 ms
analyse.png
788 ms
analytics.js
16 ms
collect
16 ms
blogPhotoAd
384 ms
close_01.png
10 ms
top_bg.png
10 ms
bottom_bg.png
11 ms
left_bg.png
12 ms
right_bg.png
11 ms
left_top.png
10 ms
right_top.png
11 ms
left_bottom.png
13 ms
right_bottom.png
12 ms
shadow.png
8 ms
r
2104 ms
HomeBeanNew.getAccessStatistics.dwr
895 ms
ad
694 ms
close2.png
7 ms
jquery-1.4.2.js
18 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1462 ms
BgsBean.getBgsUserByUserId.dwr
893 ms
lzy3169421.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 Lzy3169421.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 Lzy3169421.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.
lzy3169421.blog.163.com
Open Graph description is not detected on the main page of Lzy 3169421 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: