Tools & Wizards About Us
ilongterm.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ilongterm.com

龙腾海外房产网|海外置业|国外房产|海外房地产|全球房产，一网打尽

Page Load Speed

54.5 sec in total

First Response

1.3 sec

Resources Loaded

50.9 sec

Page Rendered

2.4 sec

ilongterm.com screenshot

About Website

Visit ilongterm.com now to see the best up-to-date Ilongterm content for China and also check out these interesting facts you probably never knew about ilongterm.com

龙腾海外房产网致力海外房产搜索，提供海外新建房产项目及二手房搜索包括美国房产和澳洲房产等；提供全面及时的海外房地产市场新闻，解答海外房产投资和海外置业过程中的房产税费、留学移民绿卡、海外购房流程及国外购房条件，组织海外购房团实地看房

Visit ilongterm.com

Key Findings

We analyzed Ilongterm.com page load time and found that the first response time was 1.3 sec and then it took 53.3 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 41 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ilongterm.com performance score

0

Network Requests Diagram

ilongterm.com

1264 ms

www.ilongterm.com

5828 ms

global.css

746 ms

index.css

742 ms

weebox.css

744 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 69% of them (70 requests) were addressed to the original Ilongterm.com, 11% (11 requests) were made to Agent.ilongterm.com and 4% (4 requests) were made to Tjs.sjs.sinajs.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Ilongterm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.0 kB (22%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ilongterm.com main page is 1.4 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.6 kB

  • Original 60.0 kB
  • After minification 47.2 kB
  • After compression 11.4 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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.6 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 57.8 kB

  • Original 1.0 MB
  • After minification 969.9 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. Ilongterm images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 180.1 kB

  • Original 294.9 kB
  • After minification 261.3 kB
  • After compression 114.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 180.1 kB or 61% of the original size.

CSS Optimization

-77%

Potential reduce by 26.5 kB

  • Original 34.5 kB
  • After minification 31.4 kB
  • After compression 8.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. Ilongterm.com needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (29%)

Requests Now

58

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ilongterm. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ilongterm.com

ilongterm.com

1264 ms

www.ilongterm.com

www.ilongterm.com

5828 ms

global.css

global.css

746 ms

index.css

index.css

742 ms

weebox.css

weebox.css

744 ms

jquery.min.js

jquery.min.js

3542 ms

weebox.js

weebox.js

742 ms

bgiframe.js

bgiframe.js

1123 ms

header.js

header.js

1347 ms

index.js

index.js

1148 ms

wb.js

wb.js

127 ms

stat.php

stat.php

2746 ms

1

1

1792 ms

1423533538781466545.jpg

1423533538781466545.jpg

2669 ms

1432490238860587906.jpg

1432490238860587906.jpg

1282 ms

company_img_1432619696.png

company_img_1432619696.png

999 ms

property_img_1417160678.jpg

property_img_1417160678.jpg

6931 ms

company_img_1417160635.jpg

company_img_1417160635.jpg

6627 ms

property_img_1419564647.jpg

property_img_1419564647.jpg

14158 ms

company_img_1419564680.jpg

company_img_1419564680.jpg

1810 ms

property_img_1440035605.jpg

property_img_1440035605.jpg

19513 ms

company_img_1420353132.jpg

company_img_1420353132.jpg

2549 ms

property_img_1444354440.jpg

property_img_1444354440.jpg

19513 ms

company_img_1444354440.jpg

company_img_1444354440.jpg

4055 ms

property_img_1417161681.jpg

property_img_1417161681.jpg

19513 ms

company_img_1417161578.jpg

company_img_1417161578.jpg

14878 ms

property_img_1417161205.png

property_img_1417161205.png

19512 ms

company_img_1417161205.jpg

company_img_1417161205.jpg

14907 ms

property_img_1443925419.jpg

property_img_1443925419.jpg

19513 ms

company_img_1443925465.jpg

company_img_1443925465.jpg

19125 ms

gz20160218.jpg

gz20160218.jpg

19513 ms

58-160330132952553.jpg

58-160330132952553.jpg

19514 ms

113GQ1E-7.jpg

113GQ1E-7.jpg

19514 ms

15123043D-0.jpg

15123043D-0.jpg

19515 ms

13233L5O-0.jpg

13233L5O-0.jpg

19515 ms

LTM201507.jpg

LTM201507.jpg

19515 ms

sh20151117.png

sh20151117.png

20505 ms

1427854702.jpg

1427854702.jpg

20503 ms

1429588553.jpg

1429588553.jpg

20504 ms

1423422762054308174.jpg

1423422762054308174.jpg

20506 ms

1432282415.jpg

1432282415.jpg

20505 ms

1423957897896598840.jpg

1423957897896598840.jpg

20511 ms

1432282682.jpg

1432282682.jpg

20514 ms

1430802847380265485.jpg

1430802847380265485.jpg

20513 ms

1433318061.jpg

1433318061.jpg

20515 ms

1433278828639949082.jpg

1433278828639949082.jpg

20515 ms

1439283266.PNG

1439283266.PNG

20516 ms

1428299448842777360.jpg

1428299448842777360.jpg

20518 ms

1437098053298230264.jpg

1437098053298230264.jpg

20518 ms

1403660919915139270.jpg

1403660919915139270.jpg

1247 ms

1403654494391679621.jpg

1403654494391679621.jpg

1246 ms

1412996537531737423.jpg

1412996537531737423.jpg

1267 ms

1403658516719328655.jpg

1403658516719328655.jpg

11836 ms

1403577420882366584.jpg

1403577420882366584.jpg

2000 ms

1403650825075384130.jpg

1403650825075384130.jpg

2023 ms

1403653077206110739.jpg

1403653077206110739.jpg

8934 ms

1403651038754826008.jpg

1403651038754826008.jpg

2136 ms

1403651617902135993.jpg

1403651617902135993.jpg

2738 ms

1403651719340803251.jpg

1403651719340803251.jpg

3276 ms

1420399420572155291.jpg

1420399420572155291.jpg

20422 ms

h.js

h.js

1732 ms

ajax_getActData

ajax_getActData

19545 ms

1433801942530275127.png

1433801942530275127.png

20233 ms

1372285144731040453.jpg

1372285144731040453.jpg

19542 ms

21.gif

21.gif

7779 ms

stat.htm

stat.htm

293 ms

core.php

core.php

852 ms

hm.gif

hm.gif

1574 ms

1446505718030864272.jpg

1446505718030864272.jpg

18829 ms

loading1.gif

loading1.gif

448 ms

bundle.js

bundle.js

2735 ms

1415324709265746664.jpg

1415324709265746664.jpg

17353 ms

client.js

client.js

52 ms

iframeWidget.js

iframeWidget.js

321 ms

aj_relationship.php

aj_relationship.php

3303 ms

1415060521341312029.jpg

1415060521341312029.jpg

19886 ms

SREX2016-0113.jpg

SREX2016-0113.jpg

19584 ms

followbutton.php

followbutton.php

782 ms

followButton.css

followButton.css

95 ms

sso.js

sso.js

136 ms

followButton.js

followButton.js

102 ms

suda.js

suda.js

119 ms

bg_flbtn.png

bg_flbtn.png

63 ms

b.gif

b.gif

1078 ms

1417142535.jpg

1417142535.jpg

20356 ms

1425637317.jpg

1425637317.jpg

19633 ms

1433295947.jpg

1433295947.jpg

19604 ms

sh20160226.jpg

sh20160226.jpg

20385 ms

bj20160311.gif

bj20160311.gif

20002 ms

gz20160112.gif

gz20160112.gif

20003 ms

wechat.jpg

wechat.jpg

15746 ms

qrcode.jpg

qrcode.jpg

17785 ms

main_logo.png

main_logo.png

18591 ms

icon.png

icon.png

20000 ms

hot01.gif

hot01.gif

19254 ms

1439529589.jpg

1439529589.jpg

19999 ms

1438159898.jpg

1438159898.jpg

19999 ms

1438159828.jpg

1438159828.jpg

19999 ms

1434007978.jpg

1434007978.jpg

19989 ms

calendar.png

calendar.png

19998 ms

agent_mask.png

agent_mask.png

19680 ms

SEO Factors

ilongterm.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ilongterm.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 Ilongterm.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.

Social Sharing Optimization

ilongterm.com

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