32.3 sec in total
1.6 sec
30.2 sec
507 ms
Visit gejiedongtai.blog.163.com now to see the best up-to-date Gejiedongtai Blog 163 content for China and also check out these interesting facts you probably never knew about gejiedongtai.blog.163.com
Visit gejiedongtai.blog.163.comWe analyzed Gejiedongtai.blog.163.com page load time and found that the first response time was 1.6 sec and then it took 30.7 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 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
gejiedongtai.blog.163.com performance score
1612 ms
1119 ms
745 ms
5269 ms
260 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 Gejiedongtai.blog.163.com, 26% (19 requests) were made to Img.bimg.126.net and 16% (12 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 546.2 kB (64%)
850.4 kB
304.2 kB
In fact, the total size of Gejiedongtai.blog.163.com main page is 850.4 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 74.5 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 74.5 kB or 79% 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. Gejiedongtai 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 152.1 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. Gejiedongtai.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.1 kB or 82% of the original size.
Number of requests can be reduced by 44 (62%)
71
27
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gejiedongtai 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 12 to 1 for JavaScripts and as a result speed up the page load time.
gejiedongtai.blog.163.com
1612 ms
c.css
1119 ms
b.css
745 ms
6630133180817252049.jpg
5269 ms
xcode.png
260 ms
1.0.0.js
394 ms
pc.js
1855 ms
ph.js
1893 ms
5785436671311429286.jpg
3188 ms
icon.png
54 ms
lnkbar.png
55 ms
image.png
56 ms
arrow24.png
54 ms
newtopbaricon8.png
55 ms
5785436671311429285.jpg
673 ms
5774459147219844167.jpg
707 ms
5774459147219844166.jpg
744 ms
5774459147219844169.jpg
2488 ms
5774459147219844173.jpg
1688 ms
5774459147219844177.jpg
1010 ms
5774459147219844246.jpg
1107 ms
5774459147219844249.jpg
1318 ms
5774459147219844247.jpg
2138 ms
5774459147219844185.jpg
1625 ms
5774459147219844184.jpg
1701 ms
5774459147219844186.jpg
1937 ms
5774459147219844187.jpg
1990 ms
5774459147219844188.jpg
2053 ms
5774459147219844189.jpg
2258 ms
5774459147219844191.jpg
2294 ms
5774459147219844190.jpg
2437 ms
5785436671311429283.jpg
19771 ms
crossdomain.html
1951 ms
crossdomain.html
1570 ms
crossdomain.html
597 ms
request.s
882 ms
analyse.png
1952 ms
empty.png
47 ms
ava.s
3536 ms
loftericon.png
314 ms
analyse.png
755 ms
analytics.js
14 ms
collect
15 ms
blogPhotoAd
1730 ms
close_01.png
29 ms
top_bg.png
57 ms
bottom_bg.png
57 ms
left_bg.png
57 ms
right_bg.png
56 ms
left_top.png
57 ms
right_top.png
57 ms
left_bottom.png
67 ms
right_bottom.png
65 ms
shadow.png
27 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
793 ms
HomeBeanNew.getFriends.dwr
1140 ms
HomeBeanNew.getAccessStatistics.dwr
2212 ms
UserBeanNew.getVisitor.dwr
1131 ms
NoteBeanNew.getNotesForPrev.dwr
13771 ms
HomeBeanNew.getClassifyModuleData.dwr
1971 ms
r
3976 ms
ava.s
855 ms
ava.s
841 ms
ava.s
851 ms
ava.s
2379 ms
ava.s
1009 ms
ava.s
1352 ms
ava.s
3295 ms
ava.s
1371 ms
ava.s
7363 ms
close2.png
56 ms
ava.s
968 ms
BgsBean.getBgsUserByUserId.dwr
8771 ms
ad
19531 ms
gejiedongtai.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 Gejiedongtai.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 Gejiedongtai.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.
gejiedongtai.blog.163.com
Open Graph description is not detected on the main page of Gejiedongtai 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: