35.8 sec in total
7.6 sec
27.9 sec
326 ms
Visit 6521800.blog.163.com now to see the best up-to-date 6521800 Blog 163 content for China and also check out these interesting facts you probably never knew about 6521800.blog.163.com
Visit 6521800.blog.163.comWe analyzed 6521800.blog.163.com page load time and found that the first response time was 7.6 sec and then it took 28.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
6521800.blog.163.com performance score
7607 ms
82 ms
1940 ms
689 ms
92 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original 6521800.blog.163.com, 57% (21 requests) were made to Img.bimg.126.net and 16% (6 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Lofter.com.
Page size can be reduced by 538.6 kB (66%)
817.7 kB
279.1 kB
In fact, the total size of 6521800.blog.163.com main page is 817.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 448.7 kB which makes up the majority of the site volume.
Potential reduce by 67.8 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 67.8 kB or 79% of the original size.
Potential reduce by 8.4 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. 6521800 Blog 163 images are well optimized though.
Potential reduce by 310.3 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 310.3 kB or 69% of the original size.
Potential reduce by 152.0 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. 6521800.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.
Number of requests can be reduced by 18 (51%)
35
17
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 6521800 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 4 to 1 for JavaScripts and as a result speed up the page load time.
6521800.blog.163.com
7607 ms
c.css
82 ms
b.css
1940 ms
5770799972522187428.jpg
689 ms
icon.png
92 ms
6630133180817252049.jpg
828 ms
xcode.png
153 ms
1.0.0.js
164 ms
pc.js
178 ms
ph.js
173 ms
5779244221823515636.jpg
703 ms
5779244221823515635.jpg
2084 ms
5791347645822068511.jpg
770 ms
5791347645822068509.jpg
773 ms
5791347645822068513.jpg
773 ms
5780933071683780524.jpg
972 ms
5791347645822068515.jpg
1051 ms
5791347645822068517.jpg
1164 ms
5791347645822068546.jpg
1144 ms
5791347645822068549.jpg
1140 ms
5791347645822068547.jpg
1341 ms
5776992422009831185.jpg
1451 ms
5776992422009831184.jpg
1525 ms
5776992422009831186.jpg
1528 ms
5780088646753648775.jpg
1553 ms
5776992422009831187.jpg
1666 ms
5776992422009831188.jpg
1808 ms
5776992422009831189.jpg
1923 ms
5776992422009831191.jpg
1925 ms
5776992422009831190.jpg
2786 ms
lnkbar.png
69 ms
image.png
106 ms
arrow24.png
104 ms
newtopbaricon8.png
104 ms
analyse.png
19815 ms
analytics.js
46 ms
collect
60 ms
6521800.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 6521800.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 6521800.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.
6521800.blog.163.com
Open Graph description is not detected on the main page of 6521800 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: