Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

new.taxi-finder.com

Shuttle Direct: Book airport transfers for our cheapest prices

Page Load Speed

2.6 sec in total

First Response

192 ms

Resources Loaded

2.2 sec

Page Rendered

239 ms

new.taxi-finder.com screenshot

About Website

Visit new.taxi-finder.com now to see the best up-to-date New Taxi Finder content for Mauritius and also check out these interesting facts you probably never knew about new.taxi-finder.com

Taxi, Bus and Shuttle service. Book direct and you won’t pay more than you should. Book cheap transfers at the official ShuttleDirect.com site for our best prices.

Visit new.taxi-finder.com

Key Findings

We analyzed New.taxi-finder.com page load time and found that the first response time was 192 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

new.taxi-finder.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

new.taxi-finder.com

192 ms

653 ms

styles.5620454f.css

568 ms

js

77 ms

exoBundle.js

337 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original New.taxi-finder.com, 56% (23 requests) were made to C1www.shuttledirect.com and 10% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (700 ms) relates to the external source C1www.shuttledirect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 88.3 kB (16%)

Content Size

568.3 kB

After Optimization

480.0 kB

In fact, the total size of New.taxi-finder.com main page is 568.3 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. 55% of websites need less resources to load. Images take 328.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 86.4 kB

  • Original 102.8 kB
  • After minification 101.7 kB
  • After compression 16.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. 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 86.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 328.7 kB
  • After minification 328.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. New Taxi Finder images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 648 B

  • Original 60.4 kB
  • After minification 60.3 kB
  • After compression 59.8 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

-2%

Potential reduce by 1.2 kB

  • Original 76.3 kB
  • After minification 76.3 kB
  • After compression 75.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. New.taxi-finder.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

34

After Optimization

18

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of New Taxi Finder. 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.

Accessibility Review

new.taxi-finder.com accessibility score

76

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

new.taxi-finder.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

new.taxi-finder.com SEO score

81

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 New.taxi-finder.com 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 New.taxi-finder.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

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