41.4 sec in total
6.2 sec
34.8 sec
445 ms
Visit wh.fangdr.com now to see the best up-to-date Wh Fangdr content for China and also check out these interesting facts you probably never knew about wh.fangdr.com
Visit wh.fangdr.comWe analyzed Wh.fangdr.com page load time and found that the first response time was 6.2 sec and then it took 35.2 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. Unfortunately, there were 47 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
wh.fangdr.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.1 s
0/100
25%
Value16.3 s
0/100
10%
Value50 ms
100/100
30%
Value0.002
100/100
15%
Value11.6 s
18/100
10%
6151 ms
2038 ms
1498 ms
1503 ms
7361 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 34% of them (37 requests) were addressed to the original Wh.fangdr.com, 56% (60 requests) were made to File.wh.fangdr.com and 2% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source File.wh.fangdr.com.
Page size can be reduced by 260.6 kB (48%)
544.6 kB
284.0 kB
In fact, the total size of Wh.fangdr.com main page is 544.6 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 225.6 kB which makes up the majority of the site volume.
Potential reduce by 60.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 60.5 kB or 77% of the original size.
Potential reduce by 33.8 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. Obviously, Wh Fangdr needs image optimization as it can save up to 33.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 148.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 148.5 kB or 66% of the original size.
Potential reduce by 17.7 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. Wh.fangdr.com needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 84% of the original size.
Number of requests can be reduced by 24 (42%)
57
33
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wh Fangdr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
wh.fangdr.com
6151 ms
index.css
2038 ms
tab.css
1498 ms
toTop.1.0.css
1503 ms
jquery-1.8.0.min.js
7361 ms
ext-core.js
5583 ms
toTop.1.0.js
2042 ms
scxx.js
2471 ms
sinaflash.js
4091 ms
crapLoader.js
5226 ms
ajaxNewLoaderAds.js
2582 ms
house.js
3017 ms
index_top_flag_left.js
871 ms
index_top_flag_middle.js
859 ms
index_top_flag_right.js
870 ms
jquery.KinSlideshow-1.2.1.min.js
927 ms
index_index_middle_right.js
933 ms
index_index_bottom_right.js
465 ms
javascript;base64,Y3JhcExvYWRlci5fb2x0PTI=
7 ms
javascript;base64,Y3JhcExvYWRlci5fb2x0PTM=
1 ms
topbar.jpg
574 ms
20151114af7c7c.jpg
15643 ms
20150540ce4c72.jpg
851 ms
20150540c96c0f.jpg
2385 ms
201505280501a0.jpg
4640 ms
s201305ef6a667e.jpg
4465 ms
s201307bd4890d4.GIF
560 ms
13034656674973662.jpg
1707 ms
13457871113281971.jpg
20132 ms
s201410fcd34865.jpg
5165 ms
s201410fcd1922a.jpg
18548 ms
s2013083766b13b.jpg
18049 ms
s201410fcd74886.jpg
14519 ms
s201308375ae557.jpg
8709 ms
s2013071e1ec50c.jpg
17081 ms
s2015127ba7d617.JPG
20123 ms
s201312bb1a0a56.jpg
20124 ms
s201408aa06d1da.jpg
20124 ms
13081849430767252.jpg
20121 ms
s201504fea87013.jpg
20120 ms
s201504bb902997.jpg
20113 ms
s201504b0e56cdc.jpg
20114 ms
s20141173c81023.jpg
20113 ms
s2014097d4371ce.jpg
20113 ms
s2014039149ef9f.png
20113 ms
13541668739602622.jpg
20113 ms
13332495634805893.jpg
20112 ms
13648049272927576.jpg
20113 ms
logo.jpg
20113 ms
soan.gif
634 ms
navleftbg.jpg
595 ms
SubMenu01.jpg
2728 ms
SubMenu02.jpg
1635 ms
SubMenu03.jpg
3135 ms
SubMenu04.jpg
4590 ms
navrithbg.jpg
1083 ms
news3.jpg
4370 ms
1457402226896.jpg
12119 ms
1455504392721.jpg
20058 ms
1455504064384.jpg
20059 ms
1455503791448.jpg
20059 ms
1459395252538.jpg
20058 ms
home6.jpg
19907 ms
home7.jpg
20060 ms
1455502225948.jpg
20060 ms
1368677105176.bmp
20061 ms
1459502170929.jpg
20060 ms
1431478352909.jpg
20059 ms
1456884621906.jpg
20060 ms
3dkf0.jpg
20059 ms
dzsp.jpg
20059 ms
dzxf.jpg
20057 ms
dzzz.jpg
20057 ms
ewm.jpg
20056 ms
fbh.jpg
20072 ms
searchmid.gif
19866 ms
searchleft.gif
19865 ms
searchdh.gif
19866 ms
searchright.gif
19865 ms
nav_dhbg.jpg
19801 ms
news4.jpg
19802 ms
news6.jpg
19802 ms
1449042642919.jpg
19801 ms
1455849900581.gif
19584 ms
1449042608889.jpg
20465 ms
home4.jpg
20446 ms
h.js
628 ms
news12.jpg
19974 ms
21.gif
1007 ms
hm.gif
305 ms
z_stat.php
3244 ms
newlist3.jpg
20424 ms
news9.jpg
20331 ms
1405613238762.jpg
19923 ms
news8.jpg
19684 ms
stat.htm
174 ms
core.php
728 ms
hdico.gif
17586 ms
9.gif
784 ms
pic1.gif
829 ms
AjaxServlet
18673 ms
AjaxServlet
15747 ms
AjaxServlet
16068 ms
app.gif
2040 ms
tab1.gif
10641 ms
tab.gif
3309 ms
flash_bg.gif
3164 ms
home14.jpg
5300 ms
wh.fangdr.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wh.fangdr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wh.fangdr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wh.fangdr.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wh.fangdr.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
wh.fangdr.com
Open Graph description is not detected on the main page of Wh Fangdr. 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: