11.3 sec in total
2 sec
9.1 sec
256 ms
Click here to check amazing Tmagazine Blog 163 content for China. Otherwise, check out these important facts you probably never knew about tmagazine.blog.163.com
Visit tmagazine.blog.163.comWe analyzed Tmagazine.blog.163.com page load time and found that the first response time was 2 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tmagazine.blog.163.com performance score
1954 ms
1455 ms
996 ms
1262 ms
1163 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tmagazine.blog.163.com, 21% (12 requests) were made to B.bst.126.net and 17% (10 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Api.blog.163.com.
Page size can be reduced by 632.6 kB (59%)
1.1 MB
434.9 kB
In fact, the total size of Tmagazine.blog.163.com main page is 1.1 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. 40% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.
Potential reduce by 105.2 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 105.2 kB or 80% of the original size.
Potential reduce by 19.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. Tmagazine Blog 163 images are well optimized though.
Potential reduce by 358.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 358.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. Tmagazine.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 35 (61%)
57
22
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tmagazine 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 15 to 1 for JavaScripts and as a result speed up the page load time.
tmagazine.blog.163.com
1954 ms
c.css
1455 ms
b.css
996 ms
6630133180817252049.jpg
1262 ms
xcode.png
1163 ms
1.0.0.js
368 ms
pc.js
1082 ms
ph.js
1051 ms
5720415951691284701.jpg
2658 ms
rssi.png
82 ms
icon.png
84 ms
lnkbar.png
82 ms
image.png
82 ms
arrow24.png
83 ms
newtopbaricon8.png
84 ms
5745185749641827471.jpg
1054 ms
5745185749641827469.jpg
1056 ms
5720415951691284702.jpg
1109 ms
5745185749641827577.jpg
1110 ms
5745185749641827467.jpg
1593 ms
crossdomain.html
832 ms
crossdomain.html
1366 ms
crossdomain.html
1207 ms
request.s
826 ms
analyse.png
1075 ms
ava.s
1097 ms
loftericon.png
436 ms
analyse.png
1124 ms
analytics.js
4 ms
collect
11 ms
k.gif
883 ms
SetupBeanNew.getResourceModulesData.dwr
796 ms
HomeBeanNew.getAccessStatistics.dwr
1129 ms
NoteBeanNew.getNotesForPrev.dwr
1190 ms
BlogBeanNew.getBlogClasses.dwr
3473 ms
BlogBeanNew.getHostHotBlogs.dwr
1629 ms
BlogBeanNew.getRecentArchives.dwr
1525 ms
TagBeanNew.getHostHotTags.dwr
1904 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
3881 ms
blogPhotoAd
557 ms
close_01.png
6 ms
top_bg.png
8 ms
bottom_bg.png
6 ms
left_bg.png
8 ms
right_bg.png
7 ms
left_top.png
7 ms
right_top.png
8 ms
left_bottom.png
9 ms
right_bottom.png
9 ms
shadow.png
7 ms
BgsBean.getBgsUserByUserId.dwr
1067 ms
r
1375 ms
face56.gif
6 ms
face50.gif
6 ms
close2.png
4 ms
ad
1245 ms
jquery-1.4.2.js
9 ms
0322db-300250.jpg
1204 ms
tmagazine.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 Tmagazine.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 Tmagazine.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.
tmagazine.blog.163.com
Open Graph description is not detected on the main page of Tmagazine 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: