Tools & Wizards About Us
udrive.in screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

udrive.in

U Drive | Self Drive Car Rental India

Page Load Speed

2.8 sec in total

First Response

223 ms

Resources Loaded

2.4 sec

Page Rendered

210 ms

udrive.in screenshot

About Website

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

U Drive, Self drive car rental in Pune, Nagpur, Mumbai, Hyderabad, Bangalore & Panjim, self drive car rental, book a cab in India, Nagpur cabs service, car rental website, hire a car, luxury car renta...

Visit udrive.in

Key Findings

We analyzed Udrive.in page load time and found that the first response time was 223 ms and then it took 2.6 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

udrive.in performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

udrive.in

223 ms

js

83 ms

adsbygoogle.js

146 ms

amp-auto-ads-0.1.js

45 ms

style.css

75 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 40% of them (29 requests) were addressed to the original Udrive.in, 15% (11 requests) were made to Googleads.g.doubleclick.net and 14% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (934 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.8 kB (14%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Udrive.in 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 947.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 76.6 kB

  • Original 89.0 kB
  • After minification 78.7 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 10.3 kB, which is 12% 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 76.6 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 13.0 kB

  • Original 656.7 kB
  • After minification 643.8 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. U Drive images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 138.0 kB

  • Original 947.1 kB
  • After minification 947.1 kB
  • After compression 809.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 138.0 kB or 15% of the original size.

CSS Optimization

-36%

Potential reduce by 24.3 kB

  • Original 67.1 kB
  • After minification 67.1 kB
  • After compression 42.8 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. Udrive.in needs all CSS files to be minified and compressed as it can save up to 24.3 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (55%)

Requests Now

65

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

udrive.in

udrive.in

223 ms

js

js

83 ms

adsbygoogle.js

adsbygoogle.js

146 ms

amp-auto-ads-0.1.js

amp-auto-ads-0.1.js

45 ms

style.css

style.css

75 ms

bootstrap.css

bootstrap.css

201 ms

menu.css

menu.css

200 ms

demo-slideshow.css

demo-slideshow.css

128 ms

site.css

site.css

198 ms

jquery.js

jquery.js

37 ms

jquery.cycle2.js

jquery.cycle2.js

217 ms

examples-offline.css

examples-offline.css

144 ms

kendo.common.min.css

kendo.common.min.css

258 ms

kendo.default.min.css

kendo.default.min.css

229 ms

jquery.min.js

jquery.min.js

280 ms

kendo.web.min.js

kendo.web.min.js

528 ms

console.js

console.js

273 ms

show_ads_impl.js

show_ads_impl.js

263 ms

flowers-left.png

flowers-left.png

107 ms

image-1.jpg

image-1.jpg

191 ms

image-2.jpg

image-2.jpg

71 ms

image-3.jpg

image-3.jpg

191 ms

image-4.jpg

image-4.jpg

89 ms

image-5.jpg

image-5.jpg

126 ms

image-6.jpg

image-6.jpg

189 ms

callout_black.gif

callout_black.gif

138 ms

ritz.jpg

ritz.jpg

150 ms

dis.jpg

dis.jpg

190 ms

high.jpg

high.jpg

246 ms

touch.jpg

touch.jpg

247 ms

zrt_lookup.html

zrt_lookup.html

40 ms

ads

ads

827 ms

udrive_logo.png

udrive_logo.png

192 ms

popup_back.png

popup_back.png

192 ms

ads

ads

722 ms

spinner.gif

spinner.gif

20 ms

ads

ads

771 ms

ads

ads

686 ms

ads

ads

376 ms

ads

ads

384 ms

back.png

back.png

91 ms

ads

ads

934 ms

sprite.png

sprite.png

65 ms

ads

ads

794 ms

css

css

38 ms

m_js_controller.js

m_js_controller.js

24 ms

ufs_web_display.js

ufs_web_display.js

13 ms

abg_lite.js

abg_lite.js

27 ms

window_focus.js

window_focus.js

30 ms

qs_click_protection.js

qs_click_protection.js

31 ms

14763004658117789537

14763004658117789537

264 ms

s

s

248 ms

icon.png

icon.png

170 ms

load_preloaded_resource.js

load_preloaded_resource.js

235 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

348 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

340 ms

af5cf33f216dd68f5f355584e69bf9d6.js

af5cf33f216dd68f5f355584e69bf9d6.js

343 ms

reactive_library.js

reactive_library.js

286 ms

ca-pub-9585567906480306

ca-pub-9585567906480306

545 ms

activeview

activeview

374 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

495 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

498 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

498 ms

css

css

144 ms

css

css

281 ms

activeview

activeview

265 ms

ZsWo5sopcGxC2wQTuXy5lIV-EUe_3KQjEcUzeWd7UO0.js

ZsWo5sopcGxC2wQTuXy5lIV-EUe_3KQjEcUzeWd7UO0.js

230 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

277 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

277 ms

activeview

activeview

183 ms

activeview

activeview

170 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

48 ms

activeview

activeview

105 ms

Accessibility Review

udrive.in accessibility score

64

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

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

udrive.in best practices score

58

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

udrive.in SEO score

54

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

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Udrive.in can be misinterpreted by Google and other search engines. Our service has detected that English 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 Udrive.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

udrive.in

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