Tools & Wizards About Us
licai.p2peye.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

licai.p2peye.com

Page Load Speed

56.3 sec in total

First Response

13.9 sec

Resources Loaded

41.8 sec

Page Rendered

576 ms

licai.p2peye.com screenshot

About Website

Click here to check amazing Licai P 2 Peye content for China. Otherwise, check out these important facts you probably never knew about licai.p2peye.com

P2P理财提供P2P理财平台，P2P理财投资，网络投资，P2P理财公司等内容，网贷天眼P2P理财频道为您提供P2P理财全方位的信息参考。

Visit licai.p2peye.com

Key Findings

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

Performance Metrics

licai.p2peye.com performance score

0

Network Requests Diagram

licai.p2peye.com

13945 ms

licai.css

7325 ms

jquery.1.8.3.js

2711 ms

3e1e26c67e7af322b5328eda233c4de9.jpg

20489 ms

1abe24c913b277d02661f44a0ddbeb7f.jpg

20404 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 25% of them (25 requests) were addressed to the original Licai.p2peye.com, 57% (56 requests) were made to P2peye.com and 10% (10 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source P2peye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 793.0 kB (38%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 154.3 kB

  • Original 172.8 kB
  • After minification 98.5 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 74.2 kB, which is 43% 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 154.3 kB or 89% of the original size.

Image Optimization

-9%

Potential reduce by 97.0 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Licai P 2 Peye images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 436.2 kB

  • Original 660.4 kB
  • After minification 660.4 kB
  • After compression 224.2 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 436.2 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 105.5 kB

  • Original 121.6 kB
  • After minification 92.1 kB
  • After compression 16.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. Licai.p2peye.com needs all CSS files to be minified and compressed as it can save up to 105.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (24%)

Requests Now

66

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Licai P 2 Peye. 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.

Network Requests Diagram

licai.p2peye.com

licai.p2peye.com

13945 ms

licai.css

licai.css

7325 ms

jquery.1.8.3.js

jquery.1.8.3.js

2711 ms

3e1e26c67e7af322b5328eda233c4de9.jpg

3e1e26c67e7af322b5328eda233c4de9.jpg

20489 ms

1abe24c913b277d02661f44a0ddbeb7f.jpg

1abe24c913b277d02661f44a0ddbeb7f.jpg

20404 ms

efaaec0d79ab7f9b6509c1dc65a92940.jpg

efaaec0d79ab7f9b6509c1dc65a92940.jpg

20405 ms

30a2204941032b10a16e604ba16a0b7b.jpg

30a2204941032b10a16e604ba16a0b7b.jpg

20404 ms

77e38e30dc4dc1e91ddba815eb24dc16.jpg

77e38e30dc4dc1e91ddba815eb24dc16.jpg

14795 ms

149d51adafc43540ec121b8a8f7ebd5e.jpg

149d51adafc43540ec121b8a8f7ebd5e.jpg

3269 ms

07b3ec9a02f559127997cb086bfaeecc.jpg

07b3ec9a02f559127997cb086bfaeecc.jpg

10482 ms

c8d78fce6110213cbb5111f9f626e926.jpg

c8d78fce6110213cbb5111f9f626e926.jpg

16032 ms

f3954e37314dceaa76f3dd2afc239c84.jpg

f3954e37314dceaa76f3dd2afc239c84.jpg

19375 ms

af4386a0b5857608578984134a6f1d82.jpg

af4386a0b5857608578984134a6f1d82.jpg

20404 ms

fed328b445ba423d4ba96a5320a17152.jpg

fed328b445ba423d4ba96a5320a17152.jpg

20404 ms

b6294ae6de4af21f176048da4f6243aa.png

b6294ae6de4af21f176048da4f6243aa.png

20406 ms

bd9ca0f75ccedee918dad6856f7eb4b1.jpg

bd9ca0f75ccedee918dad6856f7eb4b1.jpg

20407 ms

db54a4d9b01d498587b506e32c6aaba8.png

db54a4d9b01d498587b506e32c6aaba8.png

20408 ms

6efcf25240cd69d347c4db54c35967ba.jpg

6efcf25240cd69d347c4db54c35967ba.jpg

20409 ms

d0aabcbf165b189213f715f00d1f8af1.jpg

d0aabcbf165b189213f715f00d1f8af1.jpg

20408 ms

a3137c2cb6594202dc1a3da792cb57ff.jpg

a3137c2cb6594202dc1a3da792cb57ff.jpg

20409 ms

avatar.php

avatar.php

20412 ms

avatar.php

avatar.php

20414 ms

avatar.php

avatar.php

20413 ms

avatar.php

avatar.php

20414 ms

avatar.php

avatar.php

20415 ms

avatar.php

avatar.php

20415 ms

avatar.php

avatar.php

20415 ms

avatar.php

avatar.php

20415 ms

2015060313133270.png

2015060313133270.png

20415 ms

65050c3fe9d313831561c78ef4da872e.jpg

65050c3fe9d313831561c78ef4da872e.jpg

20416 ms

2015091014433241.png

2015091014433241.png

20415 ms

2015020616283327.png

2015020616283327.png

20415 ms

d65530a6a44b3bdeca6264db533bc75c.png

d65530a6a44b3bdeca6264db533bc75c.png

20416 ms

avatar.php

avatar.php

20416 ms

avatar.php

avatar.php

20415 ms

avatar.php

avatar.php

20416 ms

avatar.php

avatar.php

20416 ms

avatar.php

avatar.php

20416 ms

avatar.php

avatar.php

20416 ms

loading-small.gif

loading-small.gif

453 ms

loading-big.gif

loading-big.gif

1475 ms

icons.png

icons.png

15461 ms

logo.png

logo.png

911 ms

yqyl_new.png

yqyl_new.png

916 ms

img1.png

img1.png

6380 ms

img2.png

img2.png

2887 ms

loading.gif

loading.gif

13892 ms

discuss.png

discuss.png

14360 ms

more-dt.png

more-dt.png

2687 ms

more-share.png

more-share.png

3661 ms

1987 ms

echarts.js

echarts.js

7972 ms

index.min.js

index.min.js

13843 ms

jbzx.png

jbzx.png

3956 ms

360_safe.png

360_safe.png

9313 ms

jiasule.png

jiasule.png

6187 ms

shanghaijinrongxinxi.png

shanghaijinrongxinxi.png

8895 ms

beijingwangdaihangye.png

beijingwangdaihangye.png

10373 ms

scancode.png

scancode.png

13651 ms

aq_auth.js

aq_auth.js

9612 ms

share.js

share.js

1372 ms

getViewsTpl

getViewsTpl

1522 ms

hm.js

hm.js

910 ms

push.js

push.js

965 ms

445 ms

smalllogo.png

smalllogo.png

458 ms

hm.gif

hm.gif

287 ms

share_api.js

share_api.js

331 ms

share_view.js

share_view.js

643 ms

tangram.js

tangram.js

1701 ms

api_base.js

api_base.js

635 ms

view_base.js

view_base.js

407 ms

partners.js

partners.js

347 ms

share_style0_16.css

share_style0_16.css

370 ms

icons_0_16.png

icons_0_16.png

2302 ms

logger.js

logger.js

1265 ms

16b6dd8cd90f9ed8ab23c1e4a320287d.jpg

16b6dd8cd90f9ed8ab23c1e4a320287d.jpg

3512 ms

65050c3fe9d313831561c78ef4da872e.jpg

65050c3fe9d313831561c78ef4da872e.jpg

5093 ms

59fa21ffab96d369a647413b7427fcd0.jpg

59fa21ffab96d369a647413b7427fcd0.jpg

5045 ms

365ad36162f84c1a61d7318617a3251e.png

365ad36162f84c1a61d7318617a3251e.png

5418 ms

e2c798a92565ac4c64476f34ae8ad6c4.jpg

e2c798a92565ac4c64476f34ae8ad6c4.jpg

4610 ms

d2b93c54a33257a255805e11676f6f68.jpg

d2b93c54a33257a255805e11676f6f68.jpg

4039 ms

7acb7b7e1978655d4ac9a10a0eb3c3b6.jpg

7acb7b7e1978655d4ac9a10a0eb3c3b6.jpg

6151 ms

getUserInvestShare

getUserInvestShare

1246 ms

getUserInvestShare

getUserInvestShare

532 ms

pie.js

pie.js

760 ms

78.jpg

78.jpg

8828 ms

31.jpg

31.jpg

4535 ms

60.jpg

60.jpg

5529 ms

5.jpg

5.jpg

4460 ms

0.jpg

0.jpg

4511 ms

3.jpg

3.jpg

4431 ms

35.jpg

35.jpg

4445 ms

65.jpg

65.jpg

4971 ms

1.jpg

1.jpg

5055 ms

25.jpg

25.jpg

4375 ms

92.jpg

92.jpg

4301 ms

67.jpg

67.jpg

4043 ms

67.jpg

67.jpg

2634 ms

SEO Factors

licai.p2peye.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Licai.p2peye.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Licai.p2peye.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

licai.p2peye.com

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