Tools & Wizards About Us
99fenqi.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

99fenqi.com

给你花官网_年轻人的信用钱包

Page Load Speed

68.7 sec in total

First Response

10.7 sec

Resources Loaded

57.3 sec

Page Rendered

692 ms

99fenqi.com screenshot

About Website

Click here to check amazing 99 Fenqi content for China. Otherwise, check out these important facts you probably never knew about 99fenqi.com

给你花_手机借钱神器，极速审核最快30分钟放款！

Visit 99fenqi.com

Key Findings

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

Performance Metrics

99fenqi.com performance score

0

Network Requests Diagram

99fenqi.com

10735 ms

fq.css

10599 ms

com.css

4211 ms

swiper3.1.0.min.css

2534 ms

jquery-1.11.1.min.js

9360 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 39% of them (34 requests) were addressed to the original 99fenqi.com, 37% (32 requests) were made to Image.fenqifu.com.cn and 7% (6 requests) were made to Static.99fenqi.com.cn. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Image.fenqifu.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.3 kB (73%)

Content Size

168.0 kB

After Optimization

45.8 kB

  • HTML
  • Images
  • CSS

In fact, the total size of 99fenqi.com main page is 168.0 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. 20% of websites need less resources to load. CSS take 77.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 52.5 kB

  • Original 62.3 kB
  • After minification 52.7 kB
  • After compression 9.9 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 9.6 kB, which is 15% 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 52.5 kB or 84% of the original size.

Image Optimization

-19%

Potential reduce by 5.3 kB

  • Original 28.0 kB
  • After minification 22.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, 99 Fenqi needs image optimization as it can save up to 5.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-83%

Potential reduce by 64.5 kB

  • Original 77.7 kB
  • After minification 58.6 kB
  • After compression 13.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. 99fenqi.com needs all CSS files to be minified and compressed as it can save up to 64.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (11%)

Requests Now

61

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

99fenqi.com

99fenqi.com

10735 ms

fq.css

fq.css

10599 ms

com.css

com.css

4211 ms

swiper3.1.0.min.css

swiper3.1.0.min.css

2534 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

9360 ms

jump.js

jump.js

2918 ms

jquery.cookie.js

jquery.cookie.js

1403 ms

jquery.SuperSlide.2.1.2.js

jquery.SuperSlide.2.1.2.js

4154 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

4991 ms

lazyImg.js

lazyImg.js

874 ms

image.jsp

image.jsp

6310 ms

sale.gif

sale.gif

437 ms

index_n.png

index_n.png

837 ms

erw.png

erw.png

2353 ms

ban.png

ban.png

5478 ms

placeholder.png

placeholder.png

1292 ms

1.png

1.png

2987 ms

2.png

2.png

1256 ms

3.png

3.png

2726 ms

4.png

4.png

1716 ms

5.png

5.png

3796 ms

index_phone_1.jpg

index_phone_1.jpg

8433 ms

index_phone_2.jpg

index_phone_2.jpg

6793 ms

index_shuma.jpg

index_shuma.jpg

6560 ms

index_pc_1.jpg

index_pc_1.jpg

15811 ms

index_pc_2.jpg

index_pc_2.jpg

6780 ms

ban_pc.jpg

ban_pc.jpg

16733 ms

index_camera_1.jpg

index_camera_1.jpg

17111 ms

index_camera_2.jpg

index_camera_2.jpg

12941 ms

ban_camera.jpg

ban_camera.jpg

15530 ms

index_kupin_0.jpg

index_kupin_0.jpg

18129 ms

index_kupin_1.jpg

index_kupin_1.jpg

19564 ms

index_baihuo.jpg

index_baihuo.jpg

19564 ms

index_meizhuang_1.jpg

index_meizhuang_1.jpg

19563 ms

index_meizhuang_2.jpg

index_meizhuang_2.jpg

19560 ms

ban_meizhuang.jpg

ban_meizhuang.jpg

19559 ms

ban_jiaxiao.jpg

ban_jiaxiao.jpg

19558 ms

l1.png

l1.png

19557 ms

l2.png

l2.png

19557 ms

l3.png

l3.png

19557 ms

l4.png

l4.png

19622 ms

wx.jpg

wx.jpg

19622 ms

btn.png

btn.png

11515 ms

btn.png

btn.png

13657 ms

image.jsp

image.jsp

9267 ms

image.jsp

image.jsp

20422 ms

image.jsp

image.jsp

20421 ms

image.jsp

image.jsp

20421 ms

image.jsp

image.jsp

20421 ms

fqico.png

fqico.png

2919 ms

fqico.png

fqico.png

16120 ms

hm.js

hm.js

694 ms

h.js

h.js

20199 ms

hm.gif

hm.gif

337 ms

image.jsp

image.jsp

1773 ms

8e82b111847b37d4.png

8e82b111847b37d4.png

19972 ms

image.jsp

image.jsp

5163 ms

image.jsp

image.jsp

5289 ms

image.jsp

image.jsp

9959 ms

image.jsp

image.jsp

4855 ms

image.jsp

image.jsp

19931 ms

image.jsp

image.jsp

8602 ms

image.jsp

image.jsp

9400 ms

image.jsp

image.jsp

13390 ms

image.jsp

image.jsp

6559 ms

image.jsp

image.jsp

12572 ms

image.jsp

image.jsp

10852 ms

image.jsp

image.jsp

13386 ms

image.jsp

image.jsp

11363 ms

image.jsp

image.jsp

13995 ms

image.jsp

image.jsp

14818 ms

image.jsp

image.jsp

15424 ms

image.jsp

image.jsp

19927 ms

image.jsp

image.jsp

15169 ms

image.jsp

image.jsp

15270 ms

image.jsp

image.jsp

19926 ms

image.jsp

image.jsp

19927 ms

image.jsp

image.jsp

19926 ms

image.jsp

image.jsp

17891 ms

image.jsp

image.jsp

19926 ms

image.jsp

image.jsp

19926 ms

3b071bd9a85c15e0.png

3b071bd9a85c15e0.png

19918 ms

dp.js

dp.js

2730 ms

hm.gif

hm.gif

618 ms

ico.png

ico.png

1754 ms

line.png

line.png

3511 ms

payegisIfm.jsp

payegisIfm.jsp

1779 ms

SEO Factors

99fenqi.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 99fenqi.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 99fenqi.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

99fenqi.com

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