26.3 sec in total
2 sec
23.8 sec
457 ms
Click here to check amazing Thankhumanmf 1 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about thankhumanmf1.blog.163.com
Visit thankhumanmf1.blog.163.comWe analyzed Thankhumanmf1.blog.163.com page load time and found that the first response time was 2 sec and then it took 24.2 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. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
thankhumanmf1.blog.163.com performance score
2049 ms
59 ms
31 ms
21 ms
34 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Thankhumanmf1.blog.163.com, 30% (15 requests) were made to B.bst.126.net and 18% (9 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Gorgon.youdao.com.
Page size can be reduced by 544.2 kB (67%)
807.2 kB
263.1 kB
In fact, the total size of Thankhumanmf1.blog.163.com main page is 807.2 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 449.0 kB which makes up the majority of the site volume.
Potential reduce by 76.1 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 76.1 kB or 80% of the original size.
Potential reduce by 9.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. Obviously, Thankhumanmf 1 Blog 163 needs image optimization as it can save up to 9.2 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 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 148.3 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. Thankhumanmf1.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.3 kB or 82% of the original size.
Number of requests can be reduced by 25 (57%)
44
19
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thankhumanmf 1 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.
thankhumanmf1.blog.163.com
2049 ms
c.css
59 ms
nb.css
31 ms
top_banner.jpg
21 ms
bg_tab.jpg
34 ms
tap_on.gif
38 ms
bg_web_b.gif
38 ms
icon.png
21 ms
lnkbar.png
39 ms
image.png
39 ms
arrow24.png
29 ms
6630133180817252049.jpg
3901 ms
xcode.png
27 ms
1.0.0.js
190 ms
pc.js
210 ms
ph.js
272 ms
newtopbaricon8.png
24 ms
crossdomain.html
682 ms
crossdomain.html
1787 ms
crossdomain.html
532 ms
request.s
20466 ms
analyse.png
20463 ms
ava.s
4653 ms
loftericon.png
385 ms
ava.s
890 ms
analyse.png
20193 ms
analytics.js
40 ms
collect
22 ms
HomeBeanNew.getFriends.dwr
845 ms
HomeBeanNew.getAccessStatistics.dwr
2479 ms
UserBeanNew.getVisitor.dwr
1199 ms
NoteBeanNew.getNotesForPrev.dwr
1173 ms
HomeBeanNew.getClassifyModuleData.dwr
1466 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
19517 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1678 ms
blogPhotoAd
19984 ms
close_01.png
82 ms
top_bg.png
85 ms
bottom_bg.png
80 ms
left_bg.png
84 ms
right_bg.png
160 ms
left_top.png
164 ms
right_top.png
163 ms
left_bottom.png
165 ms
right_bottom.png
165 ms
shadow.png
81 ms
ava.s
432 ms
ava.s
2466 ms
ava.s
575 ms
BgsBean.getBgsUserByUserId.dwr
813 ms
thankhumanmf1.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 Thankhumanmf1.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 Thankhumanmf1.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.
thankhumanmf1.blog.163.com
Open Graph description is not detected on the main page of Thankhumanmf 1 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: