27.8 sec in total
5.4 sec
22.1 sec
312 ms
Click here to check amazing Ppdai content for China. Otherwise, check out these important facts you probably never knew about ppdai.com
拍拍贷官网_纽交所上市企业,网络借贷平台,解决个人小额借款、短期借款问题。 资金银行存管,安全保障。
Visit ppdai.comWe analyzed Ppdai.com page load time and found that the first response time was 5.4 sec and then it took 22.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.
ppdai.com performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value11.5 s
0/100
25%
Value9.5 s
12/100
10%
Value1,760 ms
10/100
30%
Value0
100/100
15%
Value11.7 s
18/100
10%
5392 ms
2499 ms
2594 ms
3181 ms
4648 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Ppdai.com, 65% (42 requests) were made to Ppdaicdn.com and 8% (5 requests) were made to Cms.ppdaicdn.com. The less responsive or slowest element that took the longest time to load (10 sec) relates to the external source Ppdaicdn.com.
Page size can be reduced by 246.6 kB (14%)
1.8 MB
1.6 MB
In fact, the total size of Ppdai.com main page is 1.8 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.5 MB which makes up the majority of the site volume.
Potential reduce by 39.8 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.1 kB, which is 17% 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 39.8 kB or 77% of the original size.
Potential reduce by 67.0 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. Ppdai images are well optimized though.
Potential reduce by 100.1 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 100.1 kB or 56% of the original size.
Potential reduce by 39.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. Ppdai.com needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 81% of the original size.
Number of requests can be reduced by 30 (47%)
64
34
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ppdai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.ppdai.com
5392 ms
basic.css
2499 ms
layout.css
2594 ms
validation-min.css
3181 ms
recordermarketing.js
4648 ms
index20151123.css
3998 ms
rtt
1310 ms
newnotice
763 ms
newmediareport
1143 ms
jquery.js
5474 ms
init.js
2824 ms
servicestack-min.js
2984 ms
jquery.cookie.js
3159 ms
status
2137 ms
jquery.kinMaxShow-1.0.min.js
3370 ms
index20150601.js
3500 ms
ckplayer.js
9991 ms
logo.png
2770 ms
f9cc6fd5-97f8-4a79-8388-2892212b4abb.jpg
5559 ms
loading.gif
332 ms
bannerRight20150601.png
354 ms
safe.png
2054 ms
professional.png
639 ms
tuhao.png
719 ms
no1.png
847 ms
icon_kt.png
1133 ms
autobidicon.png
1059 ms
icon_sb.png
2740 ms
icon_phb.png
1941 ms
icon_chjh.png
1409 ms
icon_bz.png
3113 ms
indexborrower2.png
1754 ms
indexborrower3.png
2096 ms
indexborrower4.png
2453 ms
videoimg.png
5386 ms
indexcase1.jpg
2828 ms
indexcase2.jpg
3221 ms
indexcase3.jpg
4691 ms
ewmimg.png
3686 ms
footerweixinerweima.png
5869 ms
e47ebb95-fcaf-4d2d-a5df-a47e6d56593b.jpg
5629 ms
46e94b48-8068-426e-aa75-27ed2a81960c.jpg
5565 ms
960d58d3-a3fd-446f-8931-5ff2faba8005.jpg
5545 ms
7a7a1a3b-4754-4e86-86dc-9d289fc946f0.png
5550 ms
media.png
3922 ms
interestcalculate.png
3943 ms
ewm.png
4273 ms
box.png
4299 ms
mobileicon.png
4627 ms
footerweixin.png
4627 ms
footerweibo.png
5030 ms
acstatus.min_d1300bb7ac0b49fab6c8348e68aeb73b.js
2975 ms
pcficon.png
4220 ms
ppd_pop.min.js
437 ms
gtm.js
29 ms
h.js
1070 ms
analytics.js
40 ms
hm.js
1755 ms
monitor.js
5459 ms
getjson
4243 ms
hm.gif
791 ms
collect
3 ms
collect
75 ms
hm.gif
353 ms
defRankIcon.png
336 ms
ppdai.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.
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
Image elements do not have [alt] attributes
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.
ppdai.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ppdai.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 uses 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 Ppdai.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 Ppdai.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.
ppdai.com
Open Graph description is not detected on the main page of Ppdai. 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: