28.1 sec in total
2.7 sec
24.3 sec
1.1 sec
Visit flydru.blog.163.com now to see the best up-to-date Flydru Blog 163 content for China and also check out these interesting facts you probably never knew about flydru.blog.163.com
Visit flydru.blog.163.comWe analyzed Flydru.blog.163.com page load time and found that the first response time was 2.7 sec and then it took 25.4 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 were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
flydru.blog.163.com performance score
2739 ms
200 ms
756 ms
7434 ms
667 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Flydru.blog.163.com, 23% (11 requests) were made to B.bst.126.net and 15% (7 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.
Page size can be reduced by 550.6 kB (63%)
879.8 kB
329.1 kB
In fact, the total size of Flydru.blog.163.com main page is 879.8 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. 40% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 80.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 80.6 kB or 79% of the original size.
Potential reduce by 10.0 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. Flydru Blog 163 images are well optimized though.
Potential reduce by 310.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 310.5 kB or 69% of the original size.
Potential reduce by 149.6 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. Flydru.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 82% of the original size.
Number of requests can be reduced by 25 (58%)
43
18
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flydru 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 10 to 1 for JavaScripts and as a result speed up the page load time.
flydru.blog.163.com
2739 ms
c.css
200 ms
b.css
756 ms
5720415951691284701.jpg
7434 ms
5745185749641827471.jpg
667 ms
5745185749641827469.jpg
667 ms
5720415951691284702.jpg
713 ms
5745185749641827577.jpg
3211 ms
icon.png
44 ms
6630133180817252049.jpg
808 ms
xcode.png
45 ms
1.0.0.js
92 ms
pc.js
44 ms
ph.js
43 ms
5745185749641827467.jpg
698 ms
lnkbar.png
37 ms
image.png
38 ms
arrow24.png
35 ms
newtopbaricon8.png
36 ms
crossdomain.html
1846 ms
crossdomain.html
831 ms
crossdomain.html
719 ms
request.s
916 ms
analyse.png
20427 ms
empty.png
45 ms
ava.s
2558 ms
loftericon.png
471 ms
analyse.png
20154 ms
analytics.js
113 ms
collect
18 ms
blogPhotoAd
19942 ms
close_01.png
13 ms
top_bg.png
9 ms
bottom_bg.png
13 ms
left_bg.png
12 ms
right_bg.png
11 ms
left_top.png
9 ms
right_top.png
17 ms
left_bottom.png
18 ms
right_bottom.png
24 ms
shadow.png
11 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
943 ms
HomeBeanNew.getAccessStatistics.dwr
1247 ms
NoteBeanNew.getNotesForPrev.dwr
1248 ms
BlogBeanNew.getBlogClasses.dwr
1256 ms
BlogBeanNew.getHostHotBlogs.dwr
3518 ms
BgsBean.getBgsUserByUserId.dwr
909 ms
flydru.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 Flydru.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 Flydru.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.
flydru.blog.163.com
Open Graph description is not detected on the main page of Flydru 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: