20.1 sec in total
7.1 sec
11.6 sec
1.4 sec
Click here to check amazing Ydmm 33 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about ydmm33.blog.163.com
Visit ydmm33.blog.163.comWe analyzed Ydmm33.blog.163.com page load time and found that the first response time was 7.1 sec and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ydmm33.blog.163.com performance score
7089 ms
19 ms
880 ms
2471 ms
37 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ydmm33.blog.163.com, 16% (12 requests) were made to B.bst.126.net and 15% (11 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Ydmm33.blog.163.com.
Page size can be reduced by 681.1 kB (15%)
4.5 MB
3.8 MB
In fact, the total size of Ydmm33.blog.163.com main page is 4.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. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 106.0 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 106.0 kB or 74% of the original size.
Potential reduce by 41.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. Ydmm 33 Blog 163 images are well optimized though.
Potential reduce by 384.0 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 384.0 kB or 68% of the original size.
Potential reduce by 149.8 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. Ydmm33.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.8 kB or 82% of the original size.
Number of requests can be reduced by 27 (38%)
72
45
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ydmm 33 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 11 to 1 for JavaScripts and as a result speed up the page load time.
ydmm33.blog.163.com
7089 ms
c.css
19 ms
b.css
880 ms
4839117799610443945.jpg
2471 ms
icon.png
37 ms
5745185749641693434.jpg
440 ms
5745185749641693433.jpg
465 ms
5745185749641693431.jpg
465 ms
5761511298290881841.jpg
478 ms
5745185749641693436.jpg
511 ms
5745185749641693435.jpg
659 ms
5745185749641693437.jpg
695 ms
5750815249175915423.jpg
692 ms
6631245886583518476.jpg
466 ms
2504564342789535187.jpg
546 ms
1107041083421062325.jpg
596 ms
6630409158235395630.jpg
840 ms
6630113389607454109.jpg
635 ms
6630776395118987950.jpg
354 ms
5747719024432060111.jpg
257 ms
6630567487908508905.jpg
239 ms
6630689533699055197.jpg
207 ms
6598146188539671424.jpg
1251 ms
blog_rec.png
78 ms
841047230511760574.jpg
222 ms
5745185749641693432.jpg
525 ms
6630133180817252049.jpg
522 ms
xcode.png
71 ms
1.0.0.js
87 ms
pc.js
74 ms
ph.js
71 ms
lnkbar.png
66 ms
image.png
68 ms
arrow24.png
69 ms
newtopbaricon8.png
69 ms
3188267061301895772.jpg
3241 ms
6619431634141897767.jpg
307 ms
2171297970446190750.jpg
426 ms
2674012278851604042.jpg
359 ms
4940167316349204649.jpg
552 ms
crossdomain.html
930 ms
crossdomain.html
506 ms
crossdomain.html
514 ms
request.s
466 ms
analyse.png
532 ms
ava.s
2283 ms
loftericon.png
2045 ms
analyse.png
515 ms
analytics.js
6 ms
collect
13 ms
HomeBeanNew.getAccessStatistics.dwr
993 ms
UserSpaceBean.getUserSpace.dwr
577 ms
NoteBeanNew.getNotesForPrev.dwr
1418 ms
blogPhotoAd
286 ms
close_01.png
20 ms
top_bg.png
22 ms
bottom_bg.png
22 ms
left_bg.png
19 ms
right_bg.png
21 ms
left_top.png
22 ms
right_top.png
22 ms
left_bottom.png
22 ms
right_bottom.png
22 ms
shadow.png
16 ms
75866315403895.js
177 ms
-1.gif
5 ms
32985361127767.js
108 ms
empty.png
29 ms
r
512 ms
6619451425352333370.jpg
224 ms
ad
547 ms
close2.png
5 ms
jquery-1.4.2.js
11 ms
ad.bid.material_f84d827cd06e43a28ef019b53849c47d
1548 ms
ydmm33.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 Ydmm33.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 Ydmm33.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.
ydmm33.blog.163.com
Open Graph description is not detected on the main page of Ydmm 33 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: