25.6 sec in total
1.1 sec
23.6 sec
964 ms
Welcome to fishcanwalk.blog.163.com homepage info - get ready to check Fishcanwalk Blog 163 best content for China right away, or after learning these important things about fishcanwalk.blog.163.com
Visit fishcanwalk.blog.163.comWe analyzed Fishcanwalk.blog.163.com page load time and found that the first response time was 1.1 sec and then it took 24.5 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fishcanwalk.blog.163.com performance score
1090 ms
33 ms
803 ms
588 ms
17 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 Fishcanwalk.blog.163.com, 32% (30 requests) were made to Os.blog.163.com and 24% (23 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Lofter.com.
Page size can be reduced by 559.6 kB (57%)
978.3 kB
418.7 kB
In fact, the total size of Fishcanwalk.blog.163.com main page is 978.3 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. 30% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 86.8 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 86.8 kB or 81% of the original size.
Potential reduce by 10.3 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. Fishcanwalk 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.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. Fishcanwalk.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 37 (42%)
89
52
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fishcanwalk 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.
fishcanwalk.blog.163.com
1090 ms
c.css
33 ms
b.css
803 ms
6630133180817252049.jpg
588 ms
xcode.png
17 ms
1.0.0.js
89 ms
pc.js
35 ms
ph.js
28 ms
5770799972522187428.jpg
514 ms
blog_rec.png
116 ms
5779244221823515636.jpg
509 ms
5779244221823515635.jpg
547 ms
5791347645822068511.jpg
537 ms
5791347645822068509.jpg
575 ms
5791347645822068513.jpg
577 ms
5780933071683780524.jpg
695 ms
5791347645822068515.jpg
762 ms
5791347645822068517.jpg
799 ms
5791347645822068546.jpg
830 ms
5791347645822068549.jpg
832 ms
5791347645822068547.jpg
833 ms
5776992422009831185.jpg
925 ms
5776992422009831184.jpg
977 ms
5776992422009831186.jpg
1020 ms
5780088646753648775.jpg
1089 ms
5776992422009831187.jpg
1089 ms
5776992422009831188.jpg
1090 ms
5776992422009831189.jpg
1153 ms
5776992422009831191.jpg
1194 ms
5776992422009831190.jpg
1242 ms
icon.png
66 ms
lnkbar.png
75 ms
image.png
76 ms
arrow24.png
69 ms
newtopbaricon8.png
76 ms
crossdomain.html
1016 ms
crossdomain.html
479 ms
crossdomain.html
492 ms
request.s
19816 ms
analyse.png
19809 ms
empty.png
52 ms
ava.s
1936 ms
loftericon.png
348 ms
ava.s
1846 ms
5129881450568520461.jpg
1669 ms
5129881450568520517.jpg
2181 ms
analyse.png
19541 ms
analytics.js
17 ms
collect
15 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1062 ms
blogPhotoAd
20331 ms
close_01.png
14 ms
top_bg.png
18 ms
bottom_bg.png
21 ms
left_bg.png
21 ms
right_bg.png
24 ms
left_top.png
20 ms
right_top.png
19 ms
left_bottom.png
24 ms
right_bottom.png
26 ms
shadow.png
12 ms
HomeBeanNew.getFriends.dwr
1215 ms
HomeBeanNew.getAccessStatistics.dwr
1161 ms
UserBeanNew.getVisitor.dwr
1221 ms
NoteBeanNew.getNotesForPrev.dwr
5876 ms
HomeBeanNew.getClassifyModuleData.dwr
1245 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
2937 ms
BgsBean.getBgsUserByUserId.dwr
827 ms
ava.s
412 ms
ava.s
486 ms
ava.s
799 ms
ava.s
2363 ms
ava.s
792 ms
ava.s
813 ms
ava.s
912 ms
ava.s
3013 ms
ava.s
1211 ms
ava.s
2675 ms
ava.s
1223 ms
ava.s
1311 ms
ava.s
1566 ms
ava.s
2775 ms
ava.s
2996 ms
ava.s
1988 ms
ava.s
2386 ms
ava.s
2731 ms
ava.s
2812 ms
ava.s
3428 ms
ava.s
3532 ms
ava.s
3174 ms
ava.s
5548 ms
ava.s
5964 ms
ava.s
4017 ms
ava.s
4882 ms
ava.s
7699 ms
fishcanwalk.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 Fishcanwalk.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 Fishcanwalk.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.
fishcanwalk.blog.163.com
Open Graph description is not detected on the main page of Fishcanwalk 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: