16.4 sec in total
4.3 sec
11.5 sec
639 ms
Welcome to yxtq987.blog.163.com homepage info - get ready to check Yxtq 987 Blog 163 best content for China right away, or after learning these important things about yxtq987.blog.163.com
Visit yxtq987.blog.163.comWe analyzed Yxtq987.blog.163.com page load time and found that the first response time was 4.3 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yxtq987.blog.163.com performance score
4255 ms
213 ms
979 ms
1746 ms
123 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Yxtq987.blog.163.com, 31% (24 requests) were made to B.bst.126.net and 15% (12 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (6.8 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 649.2 kB (53%)
1.2 MB
581.3 kB
In fact, the total size of Yxtq987.blog.163.com main page is 1.2 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.3 kB which makes up the majority of the site volume.
Potential reduce by 125.9 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 125.9 kB or 83% of the original size.
Potential reduce by 15.2 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. Yxtq 987 Blog 163 images are well optimized though.
Potential reduce by 358.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 358.3 kB or 69% of the original size.
Potential reduce by 149.7 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. Yxtq987.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.7 kB or 82% of the original size.
Number of requests can be reduced by 43 (57%)
76
33
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yxtq 987 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.
yxtq987.blog.163.com
4255 ms
c.css
213 ms
b.css
979 ms
5750815249175833776.jpg
1746 ms
icon.png
123 ms
5750815249175833774.jpg
822 ms
5745467224618321688.jpg
686 ms
5750815249175833778.jpg
686 ms
5750815249175833777.jpg
750 ms
5750815249175833780.jpg
1790 ms
5750815249175833782.jpg
953 ms
5750815249175833784.jpg
985 ms
5750815249175833975.jpg
1143 ms
5750815249175833978.jpg
1035 ms
5750815249175833976.jpg
1249 ms
lnkbar.png
90 ms
image.png
201 ms
5750815249175833772.jpg
6827 ms
arrow24.png
66 ms
6630133180817252049.jpg
2974 ms
xcode.png
130 ms
1.0.0.js
239 ms
pc.js
247 ms
ph.js
310 ms
newtopbaricon8.png
43 ms
crossdomain.html
3218 ms
crossdomain.html
1674 ms
crossdomain.html
1071 ms
request.s
1641 ms
analyse.png
3562 ms
empty.png
76 ms
4854598923429569560.jpg
2656 ms
6630513611839065309.jpg
2498 ms
1549801221786618554.jpg
2098 ms
ava.s
2897 ms
loftericon.png
1810 ms
6619106178700041552.jpg
2475 ms
6608807053283264682.jpg
3483 ms
6631431704048908851.jpg
2593 ms
ava.s
1085 ms
6630928127724517535.jpg
3417 ms
2893281285608851393.gif
1990 ms
6597246788030767804.jpg
2034 ms
6631329449468918293.jpg
2382 ms
analyse.png
1373 ms
analytics.js
416 ms
collect
22 ms
blogPhotoAd
584 ms
close_01.png
108 ms
top_bg.png
133 ms
bottom_bg.png
132 ms
left_bg.png
133 ms
right_bg.png
138 ms
left_top.png
134 ms
right_top.png
137 ms
left_bottom.png
183 ms
right_bottom.png
182 ms
shadow.png
94 ms
r
606 ms
ad
685 ms
close2.png
48 ms
jquery-1.4.2.js
48 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
3505 ms
NoteBeanNew.getNotesForPrev.dwr
1400 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2440 ms
face1.gif
47 ms
face56.gif
40 ms
face50.gif
44 ms
face58.gif
43 ms
face55.gif
38 ms
face76.gif
75 ms
face49.gif
103 ms
face59.gif
161 ms
face51.gif
158 ms
face30.gif
101 ms
face51.gif
100 ms
face39.gif
170 ms
face50.gif
190 ms
yxtq987.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 Yxtq987.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 Yxtq987.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.
yxtq987.blog.163.com
Open Graph description is not detected on the main page of Yxtq 987 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: