Tools & Wizards About Us
fanging.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fanging.com

河南房产网-郑州最新楼盘开盘-本月郑州新房-郑州新楼盘

Page Load Speed

14.4 sec in total

First Response

811 ms

Resources Loaded

13.1 sec

Page Rendered

482 ms

fanging.com screenshot

About Website

Click here to check amazing Fanging content. Otherwise, check out these important facts you probably never knew about fanging.com

河南房产网提供郑州新房楼盘信息，郑州买房购房2018最新开盘消息，2018郑州新开楼盘房价价格趋势及预测，现郑州覆盖1230个新房在售楼盘，欢迎咨询致电400-661-7898。

Visit fanging.com

Key Findings

We analyzed Fanging.com page load time and found that the first response time was 811 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fanging.com performance score

0

Network Requests Diagram

fanging.com

811 ms

www.fanging.com

866 ms

index.css

736 ms

msclass.js

1695 ms

zhengzhou.iyizhai.com

1655 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Fanging.com, 57% (44 requests) were made to Img3.iyizhai.com and 25% (19 requests) were made to Zhengzhou.iyizhai.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Img3.iyizhai.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.5 kB (41%)

Content Size

703.6 kB

After Optimization

412.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fanging.com main page is 703.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 351.6 kB which makes up the majority of the site volume.

HTML Optimization

-41%

Potential reduce by 787 B

  • Original 1.9 kB
  • After minification 1.9 kB
  • After compression 1.1 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 787 B or 41% of the original size.

Image Optimization

-6%

Potential reduce by 16.5 kB

  • Original 296.1 kB
  • After minification 279.6 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. Fanging images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 227.8 kB

  • Original 351.6 kB
  • After minification 339.7 kB
  • After compression 123.8 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 227.8 kB or 65% of the original size.

CSS Optimization

-86%

Potential reduce by 46.5 kB

  • Original 54.0 kB
  • After minification 48.9 kB
  • After compression 7.6 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. Fanging.com needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (12%)

Requests Now

75

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanging. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

fanging.com

fanging.com

811 ms

www.fanging.com

www.fanging.com

866 ms

index.css

index.css

736 ms

msclass.js

msclass.js

1695 ms

zhengzhou.iyizhai.com

zhengzhou.iyizhai.com

1655 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1582 ms

test_index.css

test_index.css

1117 ms

test_index.css

test_index.css

637 ms

huandeng_jQuery.js

huandeng_jQuery.js

1609 ms

huandeng_common.js

huandeng_common.js

845 ms

tab_jquery.js

tab_jquery.js

1638 ms

tab_lrtk.js

tab_lrtk.js

851 ms

list_yi.js

list_yi.js

601 ms

jquery.js

jquery.js

1426 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

499 ms

index_v2014.js

index_v2014.js

781 ms

index_bj2.GIF

index_bj2.GIF

248 ms

20160226_cIYJFoZ4FP60MJjL.jpg

20160226_cIYJFoZ4FP60MJjL.jpg

2569 ms

2015114_ita9lHAvDckY0lvh.jpg

2015114_ita9lHAvDckY0lvh.jpg

2444 ms

20150915_nCHdKKzVoVvcmeGZ.jpg

20150915_nCHdKKzVoVvcmeGZ.jpg

2468 ms

2016033_pj0gDF860YUyieG5.jpg

2016033_pj0gDF860YUyieG5.jpg

2361 ms

2015019_BukepWnr8aNRKfHS.jpg

2015019_BukepWnr8aNRKfHS.jpg

3277 ms

20150112_jCjeiJR46yxzRceR.jpg

20150112_jCjeiJR46yxzRceR.jpg

3565 ms

2016034_sJTEh6oVQ0TIThbD.jpg

2016034_sJTEh6oVQ0TIThbD.jpg

2872 ms

20160224_8CQ9TjTJ4Yj5F1Fs.jpg

20160224_8CQ9TjTJ4Yj5F1Fs.jpg

2937 ms

20160218_5uVMnvfL32WWZ8aM.jpg

20160218_5uVMnvfL32WWZ8aM.jpg

3202 ms

20160218_XH36UoqZc74sHQ1g.jpg

20160218_XH36UoqZc74sHQ1g.jpg

3060 ms

20160127_3R2dUk4OEEiKafnj.jpg

20160127_3R2dUk4OEEiKafnj.jpg

3377 ms

2015083_L1o7RlbWaVHli4rh.jpg

2015083_L1o7RlbWaVHli4rh.jpg

3185 ms

2015055_VoTbMTA6nyfd5oJm.jpg

2015055_VoTbMTA6nyfd5oJm.jpg

3550 ms

20150113_r1gBV3SlvaSTmdQP.jpg

20150113_r1gBV3SlvaSTmdQP.jpg

3688 ms

20151021_JjZfslxhO2kH4vnG.jpg

20151021_JjZfslxhO2kH4vnG.jpg

3695 ms

20150831_kL6WRR0cOOIPu1ac.jpg

20150831_kL6WRR0cOOIPu1ac.jpg

3774 ms

20150116_XOD4mWM6nWhyDJme.jpg

20150116_XOD4mWM6nWhyDJme.jpg

3881 ms

20150122_iOZUNSteUs4ji6EZ.jpg

20150122_iOZUNSteUs4ji6EZ.jpg

3799 ms

20151114_4rOcHOuUW0PaZTJG.jpg

20151114_4rOcHOuUW0PaZTJG.jpg

4074 ms

2015112_OYS2wXerERBPryTb.jpg

2015112_OYS2wXerERBPryTb.jpg

4183 ms

20150828_WUuTPQPFRaWB7Ds6.jpg

20150828_WUuTPQPFRaWB7Ds6.jpg

3947 ms

2015071_PUNUatUXwvXOmulE.jpg

2015071_PUNUatUXwvXOmulE.jpg

4059 ms

20150529_L1fMmZGRK6ROLRy9.jpg

20150529_L1fMmZGRK6ROLRy9.jpg

4075 ms

20150420_bAINCMWs06GMxVQL.jpg

20150420_bAINCMWs06GMxVQL.jpg

4415 ms

20150610_YJ1pXQqq3BT0PW98.jpg

20150610_YJ1pXQqq3BT0PW98.jpg

4436 ms

20150521_MliYmWVjpqGVseg6.jpg

20150521_MliYmWVjpqGVseg6.jpg

4590 ms

2015128_r1JCyvSMdkEo2KZm.jpg

2015128_r1JCyvSMdkEo2KZm.jpg

4585 ms

20160112_cYBplzZoPbK85ADJ.jpg

20160112_cYBplzZoPbK85ADJ.jpg

4588 ms

20151219_kuUWUb9zmlnlXZYv.jpg

20151219_kuUWUb9zmlnlXZYv.jpg

4432 ms

2015127_KF85Y9gIzQeTCOae.jpg

2015127_KF85Y9gIzQeTCOae.jpg

4968 ms

20151119_LSUlMGS6IAvGNe7U.jpg

20151119_LSUlMGS6IAvGNe7U.jpg

4934 ms

20151114_3VsCHxKfRvo1cpPH.jpg

20151114_3VsCHxKfRvo1cpPH.jpg

4698 ms

20160311_QHFnaNrAmxOJ2Y29.jpg

20160311_QHFnaNrAmxOJ2Y29.jpg

4848 ms

20160226_KwEPxsaZb0q4L4WI.jpg

20160226_KwEPxsaZb0q4L4WI.jpg

4866 ms

20150915_b5EO37nfKIO6nQ70.jpg

20150915_b5EO37nfKIO6nQ70.jpg

6333 ms

2016039_rUdFpftLRRcc40XQ.jpg

2016039_rUdFpftLRRcc40XQ.jpg

4954 ms

logo.GIF

logo.GIF

509 ms

index_soso.GIF

index_soso.GIF

262 ms

logo1.gif

logo1.gif

507 ms

qingbao.GIF

qingbao.GIF

248 ms

index_phone.GIF

index_phone.GIF

501 ms

index_bm.gif

index_bm.gif

515 ms

index_zc.GIF

index_zc.GIF

525 ms

index_tj.GIF

index_tj.GIF

822 ms

yuncaifu.gif

yuncaifu.gif

1281 ms

index_wx01.gif

index_wx01.gif

755 ms

index_wx02.gif

index_wx02.gif

758 ms

index_di.GIF

index_di.GIF

1029 ms

index_bj1.gif

index_bj1.gif

1215 ms

index_bj3.GIF

index_bj3.GIF

691 ms

011.jpg

011.jpg

1209 ms

20160223_CoCvDzg0hqEsCdtF.png

20160223_CoCvDzg0hqEsCdtF.png

3543 ms

20151210_zNMgLOw1tcc16KZ5.png

20151210_zNMgLOw1tcc16KZ5.png

3710 ms

20151118_zrSZMYB2Wzki4sEf.jpg

20151118_zrSZMYB2Wzki4sEf.jpg

2730 ms

20151112_pnD6G5h0ExnGGfKZ.jpg

20151112_pnD6G5h0ExnGGfKZ.jpg

2663 ms

2015117_vLateDTrFgECkHny.jpg

2015117_vLateDTrFgECkHny.jpg

2376 ms

20160316_JMsrnallt36luDQQ.JPG

20160316_JMsrnallt36luDQQ.JPG

2518 ms

2016038_pNfyyq20vOaKMFRp.JPG

2016038_pNfyyq20vOaKMFRp.JPG

2424 ms

20160223_k6mHLWDkr89aqo2s.JPG

20160223_k6mHLWDkr89aqo2s.JPG

2337 ms

001.jpg

001.jpg

1835 ms

SEO Factors

fanging.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanging.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 Fanging.com main page’s claimed encoding is gb2312. 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.

Social Sharing Optimization

fanging.com

Open Graph description is not detected on the main page of Fanging. 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: