22.5 sec in total
4.8 sec
16.8 sec
886 ms
Click here to check amazing Jiwonu Blog 163 content for China. Otherwise, check out these important facts you probably never knew about jiwonu.blog.163.com
Visit jiwonu.blog.163.comWe analyzed Jiwonu.blog.163.com page load time and found that the first response time was 4.8 sec and then it took 17.7 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.
jiwonu.blog.163.com performance score
4791 ms
8 ms
977 ms
1040 ms
1111 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Jiwonu.blog.163.com, 22% (21 requests) were made to Img.bimg.126.net and 19% (18 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (12.5 sec) relates to the external source Img.bimg.126.net.
Page size can be reduced by 645.9 kB (61%)
1.1 MB
418.5 kB
In fact, the total size of Jiwonu.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. 45% of websites need less resources to load. Javascripts take 527.1 kB which makes up the majority of the site volume.
Potential reduce by 118.9 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 118.9 kB or 81% of the original size.
Potential reduce by 13.4 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. Jiwonu Blog 163 images are well optimized though.
Potential reduce by 361.6 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 361.6 kB or 69% of the original size.
Potential reduce by 152.0 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. Jiwonu.blog.163.com needs all CSS files to be minified and compressed as it can save up to 152.0 kB or 82% of the original size.
Number of requests can be reduced by 47 (51%)
93
46
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jiwonu 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.
jiwonu.blog.163.com
4791 ms
c.css
8 ms
b.css
977 ms
5770799972522187428.jpg
1040 ms
5779244221823515636.jpg
1111 ms
5779244221823515635.jpg
6922 ms
5791347645822068511.jpg
1579 ms
blog_rec.png
65 ms
5791347645822068509.jpg
1146 ms
5791347645822068513.jpg
12504 ms
5780933071683780524.jpg
1198 ms
goodbloghead.png
31 ms
6630133180817252049.jpg
1286 ms
xcode.png
25 ms
1.0.0.js
72 ms
pc.js
25 ms
ph.js
24 ms
5791347645822068515.jpg
1144 ms
5791347645822068517.jpg
1211 ms
5791347645822068546.jpg
1245 ms
5791347645822068549.jpg
1675 ms
5791347645822068547.jpg
1766 ms
5776992422009831185.jpg
1780 ms
5776992422009831184.jpg
2197 ms
5776992422009831186.jpg
3991 ms
5780088646753648775.jpg
3983 ms
5776992422009831187.jpg
8299 ms
5776992422009831188.jpg
2703 ms
5776992422009831189.jpg
3190 ms
5776992422009831191.jpg
3696 ms
5776992422009831190.jpg
4214 ms
icon.png
21 ms
lnkbar.png
22 ms
image.png
23 ms
arrow24.png
23 ms
newtopbaricon8.png
23 ms
crossdomain.html
2356 ms
crossdomain.html
2124 ms
crossdomain.html
4077 ms
request.s
657 ms
analyse.png
1267 ms
ava.s
2821 ms
loftericon.png
1981 ms
ava.s
3755 ms
analyse.png
1251 ms
analytics.js
6 ms
collect
18 ms
blogPhotoAd
600 ms
close_01.png
5 ms
top_bg.png
11 ms
bottom_bg.png
12 ms
left_bg.png
13 ms
right_bg.png
14 ms
left_top.png
13 ms
right_top.png
16 ms
left_bottom.png
15 ms
right_bottom.png
15 ms
shadow.png
9 ms
r
1011 ms
HomeBeanNew.getAccessStatistics.dwr
968 ms
UserSpaceBean.getUserSpace.dwr
1103 ms
UserBeanNew.getVisitor.dwr
1368 ms
NoteBeanNew.getNotesForPrev.dwr
1347 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1375 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1361 ms
close2.png
4 ms
ad
1169 ms
BgsBean.getBgsUserByUserId.dwr
2337 ms
72567777725852.js
2137 ms
face50.gif
12 ms
face50.gif
12 ms
face51.gif
11 ms
face51.gif
13 ms
face25.gif
24 ms
ava.s
965 ms
ava.s
2620 ms
ava.s
2865 ms
ava.s
3323 ms
ava.s
965 ms
ava.s
976 ms
ava.s
2891 ms
ava.s
1405 ms
ava.s
1421 ms
ava.s
1870 ms
ava.s
3544 ms
ava.s
2314 ms
ava.s
2762 ms
ava.s
3070 ms
ava.s
3214 ms
jquery-1.4.2.js
7 ms
0316ykt-300-250.jpg
1479 ms
-1.gif
5 ms
123145312542386.js
578 ms
empty.png
4 ms
6608411229096833605.jpg
1450 ms
jiwonu.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 Jiwonu.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 Jiwonu.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.
jiwonu.blog.163.com
Open Graph description is not detected on the main page of Jiwonu 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: