Tools & Wizards About Us
m.utaxi.in screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

m.utaxi.in

Airport Taxi | Cabs in Bangalore | Rs 474 Pickup | Rs 674 Drop

Page Load Speed

218 ms in total

First Response

38 ms

Resources Loaded

127 ms

Page Rendered

53 ms

m.utaxi.in screenshot

About Website

Welcome to m.utaxi.in homepage info - get ready to check M U Taxi best content for India right away, or after learning these important things about m.utaxi.in

Airport Taxi in Bangalore - Rs 474 / -Pick - Up, Rs 674 / -Drop, Cheapest OutStation rates.Indica Rs.7 / -Logan / Etios / Dzire Rs.9

Visit m.utaxi.in

Key Findings

We analyzed M.utaxi.in page load time and found that the first response time was 38 ms and then it took 180 ms 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. This domain responded with an error, which can significantly jeopardize M.utaxi.in rating and web reputation

Performance Metrics

m.utaxi.in performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.477

18/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

m.utaxi.in

38 ms

main.css

3 ms

beacon.js

61 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

24 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 50% of them (2 requests) were addressed to the original M.utaxi.in, 25% (1 request) were made to Performance.radar.cloudflare.com and 25% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (61 ms) relates to the external source Performance.radar.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.7 kB (46%)

Content Size

8.0 kB

After Optimization

4.3 kB

  • HTML
  • CSS

In fact, the total size of M.utaxi.in main page is 8.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 5.9 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.7 kB

  • Original 5.9 kB
  • After minification 5.5 kB
  • After compression 2.2 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 3.7 kB or 63% of the original size.

CSS Optimization

-1%

Potential reduce by 13 B

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 2.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. M.utaxi.in has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • CSS

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M U Taxi. According to our analytics all requests are already optimized.

Network Requests Diagram

m.utaxi.in

m.utaxi.in

38 ms

main.css

main.css

3 ms

beacon.js

beacon.js

61 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

24 ms

Accessibility Review

m.utaxi.in accessibility score

100

Accessibility Issues

Best Practices

m.utaxi.in 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

m.utaxi.in SEO score

93

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

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

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 M.utaxi.in 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 M.utaxi.in 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

m.utaxi.in

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