26.8 sec in total
2.1 sec
24.2 sec
607 ms
Click here to check amazing Fanxian 163 Blog content for China. Otherwise, check out these important facts you probably never knew about fanxian163.blog.163.com
Visit fanxian163.blog.163.comWe analyzed Fanxian163.blog.163.com page load time and found that the first response time was 2.1 sec and then it took 24.8 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fanxian163.blog.163.com performance score
2074 ms
14 ms
810 ms
5131 ms
14634 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fanxian163.blog.163.com, 23% (17 requests) were made to Os.blog.163.com and 19% (14 requests) were made to Img.bimg.126.net. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Os.blog.163.com.
Page size can be reduced by 595.6 kB (39%)
1.5 MB
947.3 kB
In fact, the total size of Fanxian163.blog.163.com main page is 1.5 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. 35% of websites need less resources to load. Images take 739.9 kB which makes up the majority of the site volume.
Potential reduce by 77.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 77.8 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. Fanxian 163 Blog 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 150.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. Fanxian163.blog.163.com needs all CSS files to be minified and compressed as it can save up to 150.1 kB or 82% of the original size.
Number of requests can be reduced by 34 (47%)
73
39
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanxian 163 Blog. 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.
fanxian163.blog.163.com
2074 ms
c.css
14 ms
b.css
810 ms
1460855129129121954.jpg
5131 ms
1714464083145586076.jpg
14634 ms
1714464083145586054.jpg
2017 ms
1490410001683918589.jpg
14617 ms
1714464083145586049.jpg
6506 ms
1490410001683918353.jpg
2514 ms
1490410001683918347.jpg
3011 ms
1490410001683918375.jpg
9749 ms
1461136604105832667.jpg
3521 ms
1461136604105832692.jpg
9364 ms
1461136604105832670.jpg
5600 ms
1461136604105832672.jpg
6133 ms
3379951520343001049.jpg
6621 ms
icon.png
15 ms
6630133180817252049.jpg
1034 ms
xcode.png
18 ms
1.0.0.js
95 ms
pc.js
21 ms
ph.js
21 ms
1714464083145586131.jpg
14518 ms
lnkbar.png
9 ms
image.png
11 ms
arrow24.png
11 ms
newtopbaricon8.png
12 ms
crossdomain.html
775 ms
crossdomain.html
2092 ms
request.s
1040 ms
analyse.png
1054 ms
empty.png
44 ms
1996783484886085794.png
865 ms
ava.s
2219 ms
crossdomain.html
865 ms
analyse.png
1162 ms
analytics.js
20 ms
collect
79 ms
HomeBeanNew.getAccessStatistics.dwr
841 ms
UserBeanNew.getVisitor.dwr
1494 ms
NoteBeanNew.getNotesForPrev.dwr
1633 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2380 ms
blogPhotoAd
388 ms
close_01.png
6 ms
top_bg.png
11 ms
bottom_bg.png
12 ms
left_bg.png
11 ms
right_bg.png
25 ms
left_top.png
13 ms
right_top.png
13 ms
left_bottom.png
20 ms
right_bottom.png
20 ms
shadow.png
8 ms
BgsBean.getBgsUserByUserId.dwr
1603 ms
r
1896 ms
ava.s
824 ms
ava.s
3215 ms
ava.s
2073 ms
ava.s
1376 ms
ava.s
19512 ms
ava.s
1223 ms
ava.s
1631 ms
ava.s
5079 ms
ava.s
2032 ms
ava.s
2435 ms
ava.s
10432 ms
ava.s
3237 ms
ava.s
3717 ms
ava.s
4161 ms
ava.s
4039 ms
close2.png
8 ms
ad
790 ms
jquery-1.4.2.js
15 ms
ad.bid.material_9ba8a084ec524821974fa01ce2124d16
1454 ms
face60.png
4 ms
fanxian163.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 Fanxian163.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 Fanxian163.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.
fanxian163.blog.163.com
Open Graph description is not detected on the main page of Fanxian 163 Blog. 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: