Tools & Wizards About Us
ptaxi.net screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ptaxi.net

抱歉，站点已暂停

Page Load Speed

19.3 sec in total

First Response

1.2 sec

Resources Loaded

17.5 sec

Page Rendered

644 ms

ptaxi.net screenshot

About Website

Welcome to ptaxi.net homepage info - get ready to check Ptaxi best content right away, or after learning these important things about ptaxi.net

猿著旗下品牌Ptaxi智慧出行提供网约车软件开发,城际车系统开发,代驾系统软件开发,出租车电召app开发,共享租车系统开发,网约车牌照办理服务.提供专业的出行系统开发解决方案！

Visit ptaxi.net

Key Findings

We analyzed Ptaxi.net page load time and found that the first response time was 1.2 sec and then it took 18.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

ptaxi.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value22.0 s

0/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

ptaxi.net

1157 ms

bootstrap.min.css

236 ms

font_722897_tfaoi5c9se.css

145 ms

animate.min.css

455 ms

style.css

682 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 87% of them (66 requests) were addressed to the original Ptaxi.net, 3% (2 requests) were made to At.alicdn.com and 3% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (15.5 sec) belongs to the original domain Ptaxi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.7 kB (3%)

Content Size

4.3 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ptaxi.net main page is 4.3 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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 58.9 kB

  • Original 68.8 kB
  • After minification 48.8 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 20.0 kB, which is 29% 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 58.9 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 41.1 kB

  • Original 4.0 MB
  • After minification 3.9 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. Ptaxi images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 13.4 kB

  • Original 223.1 kB
  • After minification 223.1 kB
  • After compression 209.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 15.3 kB

  • Original 78.7 kB
  • After minification 78.7 kB
  • After compression 63.4 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. Ptaxi.net needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

61

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ptaxi.net

ptaxi.net

1157 ms

bootstrap.min.css

bootstrap.min.css

236 ms

font_722897_tfaoi5c9se.css

font_722897_tfaoi5c9se.css

145 ms

animate.min.css

animate.min.css

455 ms

style.css

style.css

682 ms

swiper.min.css

swiper.min.css

458 ms

scrollreveal.min.js

scrollreveal.min.js

463 ms

jquery.min.js

jquery.min.js

788 ms

bootstrap.min.js

bootstrap.min.js

417 ms

swiper.min.js

swiper.min.js

467 ms

index.js

index.js

679 ms

pa

pa

852 ms

ae7ea5d194d15eea5b1fe5fdb0198c2e.png

ae7ea5d194d15eea5b1fe5fdb0198c2e.png

233 ms

5c28148fdeb493d07843bc73f8fc83b7.png

5c28148fdeb493d07843bc73f8fc83b7.png

680 ms

81252567bfaf7c21d17b25941c989736.png

81252567bfaf7c21d17b25941c989736.png

5441 ms

ee1fdb809de6b83b134f4b71bc578062.png

ee1fdb809de6b83b134f4b71bc578062.png

924 ms

20e91a014c170247bdc3a3162162d627.png

20e91a014c170247bdc3a3162162d627.png

5301 ms

06aff7ebba79b31a01b3a961848f5d4b.png

06aff7ebba79b31a01b3a961848f5d4b.png

5685 ms

fd85b260b10ba9b696aebfd65d253466.jpg

fd85b260b10ba9b696aebfd65d253466.jpg

697 ms

06ba67478578d318de2bae7abd8e5334.jpg

06ba67478578d318de2bae7abd8e5334.jpg

1586 ms

map_01.png

map_01.png

930 ms

map_02.png

map_02.png

1155 ms

map_03.png

map_03.png

1162 ms

map_04.png

map_04.png

2310 ms

map_05.png

map_05.png

2784 ms

map_06.png

map_06.png

1813 ms

map_07.png

map_07.png

2040 ms

map_08.png

map_08.png

2267 ms

scenes_img_01.jpg

scenes_img_01.jpg

3173 ms

scenes_01.png

scenes_01.png

2541 ms

scenes_img_02.jpg

scenes_img_02.jpg

5310 ms

scenes_02.png

scenes_02.png

3016 ms

scenes_img_05.jpg

scenes_img_05.jpg

5555 ms

scenes_03.png

scenes_03.png

3400 ms

scenes_img_04.jpg

scenes_img_04.jpg

5395 ms

scenes_04.png

scenes_04.png

5530 ms

scenes_img_03.jpg

scenes_img_03.jpg

6001 ms

scenes_05.png

scenes_05.png

5623 ms

scenes_img_06.jpg

scenes_img_06.jpg

6119 ms

scenes_06.png

scenes_06.png

5761 ms

scenes_img_07.jpg

scenes_img_07.jpg

8123 ms

scenes_07.png

scenes_07.png

5850 ms

scenes_img_08.jpg

scenes_img_08.jpg

10227 ms

scenes_08.png

scenes_08.png

5991 ms

phone_01.png

phone_01.png

6756 ms

zs_00.png

zs_00.png

7604 ms

zs_02.png

zs_02.png

8221 ms

push.js

push.js

2267 ms

hm.js

hm.js

1617 ms

font_722897_tfaoi5c9se.woff

font_722897_tfaoi5c9se.woff

426 ms

zs_10.jpg

zs_10.jpg

15509 ms

zs_01.jpg

zs_01.jpg

6979 ms

zs_03.png

zs_03.png

11263 ms

zs_04.png

zs_04.png

9676 ms

zs_05.png

zs_05.png

11379 ms

zs_06.png

zs_06.png

11506 ms

zs_07.png

zs_07.png

10664 ms

zs_08.png

zs_08.png

10364 ms

ba43be644764f1d7aaa5908ce8a5bb98.jpg

ba43be644764f1d7aaa5908ce8a5bb98.jpg

10172 ms

hm.gif

hm.gif

321 ms

b.js

b.js

2026 ms

a3d04acf70dce124cb911e2c700d2e30.png

a3d04acf70dce124cb911e2c700d2e30.png

10175 ms

c75f3c96bf5800a4bc5c355635d38f25.png

c75f3c96bf5800a4bc5c355635d38f25.png

10006 ms

a8dbbf783ea3b0f17a0449f9acf79f41.png

a8dbbf783ea3b0f17a0449f9acf79f41.png

9903 ms

00fea44c5a3857f8c6e888da6246a867.png

00fea44c5a3857f8c6e888da6246a867.png

9910 ms

f4f621e5bb4c967f96e3ba8f07452e1c.png

f4f621e5bb4c967f96e3ba8f07452e1c.png

9733 ms

button_111.gif

button_111.gif

1116 ms

d74f0f37b6c12f9ed11513746a7834a7.png

d74f0f37b6c12f9ed11513746a7834a7.png

9614 ms

891ba57150fd09387c6212e06c7f0cd8.png

891ba57150fd09387c6212e06c7f0cd8.png

9434 ms

news_img_01.jpg

news_img_01.jpg

9553 ms

news_img_02.jpg

news_img_02.jpg

9366 ms

affim.js

affim.js

2168 ms

news_img_03.jpg

news_img_03.jpg

8001 ms

bottom-icon.png

bottom-icon.png

7356 ms

telphone.png

telphone.png

7284 ms

weweima_01.jpg

weweima_01.jpg

7458 ms

Accessibility Review

ptaxi.net accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ptaxi.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ptaxi.net SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ptaxi.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Ptaxi.net 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

ptaxi.net

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