Tools & Wizards About Us
amy.cab screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

amy.cab

Cab, Taxi Service, One Way Cab, Oneway Taxi, Car Rental

Page Load Speed

24.8 sec in total

First Response

516 ms

Resources Loaded

24.1 sec

Page Rendered

130 ms

amy.cab screenshot

About Website

Click here to check amazing Amy content for India. Otherwise, check out these important facts you probably never knew about amy.cab

Find best intercity cabs for your one way transfers, local sightseeing and outstation bookings. Hire taxi for full day, Hire taxi for half day. Cab Rental services available for all cab types

Visit amy.cab

Key Findings

We analyzed Amy.cab page load time and found that the first response time was 516 ms and then it took 24.2 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

amy.cab performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

amy.cab

516 ms

www.amy.cab

1574 ms

bootstrap.min.css

699 ms

font-awesome.min.css

900 ms

style.css

1124 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 57% of them (31 requests) were addressed to the original Amy.cab, 22% (12 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Embed.tawk.to.

Page Optimization Overview & Recommendations

Page size can be reduced by 807.7 kB (66%)

Content Size

1.2 MB

After Optimization

424.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amy.cab main page is 1.2 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. 45% of websites need less resources to load. Javascripts take 754.8 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 95.6 kB

  • Original 106.3 kB
  • After minification 98.5 kB
  • After compression 10.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 95.6 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 1.0 kB

  • Original 144.7 kB
  • After minification 143.7 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. Amy images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 523.0 kB

  • Original 754.8 kB
  • After minification 674.9 kB
  • After compression 231.9 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 523.0 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 188.2 kB

  • Original 226.4 kB
  • After minification 214.4 kB
  • After compression 38.2 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. Amy.cab needs all CSS files to be minified and compressed as it can save up to 188.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (66%)

Requests Now

38

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

amy.cab

amy.cab

516 ms

www.amy.cab

www.amy.cab

1574 ms

bootstrap.min.css

bootstrap.min.css

699 ms

font-awesome.min.css

font-awesome.min.css

900 ms

style.css

style.css

1124 ms

drawer.min.css

drawer.min.css

677 ms

default.css

default.css

683 ms

default.date.css

default.date.css

687 ms

default.time.css

default.time.css

902 ms

owl.theme.css

owl.theme.css

911 ms

owl.carousel.css

owl.carousel.css

916 ms

owl.transitions.css

owl.transitions.css

931 ms

jquery_new.min.js

jquery_new.min.js

2020 ms

iscroll.js

iscroll.js

1353 ms

bootstrap.min.js

bootstrap.min.js

1365 ms

drawer.min.js

drawer.min.js

1144 ms

owl.carousel.js

owl.carousel.js

1164 ms

picker.js

picker.js

1348 ms

picker.date.js

picker.date.js

1830 ms

picker.time.js

picker.time.js

1398 ms

index.js

index.js

1571 ms

js

js

84 ms

conversion.js

conversion.js

94 ms

css

css

26 ms

css

css

43 ms

css

css

51 ms

logo.jpg

logo.jpg

246 ms

google-play-store.png

google-play-store.png

245 ms

man.png

man.png

245 ms

banner-1.jpg

banner-1.jpg

673 ms

offer-1.jpg

offer-1.jpg

244 ms

offer-2.jpg

offer-2.jpg

244 ms

offer-3.jpg

offer-3.jpg

450 ms

logo-2.jpg

logo-2.jpg

451 ms

payment.png

payment.png

456 ms

default

default

20095 ms

analytics.js

analytics.js

21 ms

47 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

26 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

39 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

55 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

55 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

55 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

569 ms

gNMaW3x8Qoy5_mf8uUkJGHtiYXjmKFy5nX9YTkT4.ttf

gNMaW3x8Qoy5_mf8uUkJGHtiYXjmKFy5nX9YTkT4.ttf

102 ms

gNMaW3x8Qoy5_mf8uUkJGHtiYXjmKFy5enhYTkT4.ttf

gNMaW3x8Qoy5_mf8uUkJGHtiYXjmKFy5enhYTkT4.ttf

55 ms

S6u8w4BMUTPHjxsAXC-v.ttf

S6u8w4BMUTPHjxsAXC-v.ttf

45 ms

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

S6u_w4BMUTPHjxsI9w2_Gwfo.ttf

62 ms

S6u-w4BMUTPHjxsIPx-oPCc.ttf

S6u-w4BMUTPHjxsIPx-oPCc.ttf

62 ms

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

S6u_w4BMUTPHjxsI5wq_Gwfo.ttf

62 ms

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

S6u_w4BMUTPHjxsI3wi_Gwfo.ttf

62 ms

collect

collect

22 ms

js

js

67 ms

34 ms

Accessibility Review

amy.cab accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

amy.cab best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

amy.cab SEO score

90

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

amy.cab

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