Tools & Wizards About Us
driiveme.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

driiveme.com

100% digital automotive logistics - DriiveMe

Page Load Speed

3.6 sec in total

First Response

302 ms

Resources Loaded

3 sec

Page Rendered

246 ms

driiveme.com screenshot

About Website

Click here to check amazing Driive Me content for France. Otherwise, check out these important facts you probably never knew about driiveme.com

We move a vehicle every 90 seconds: Movements, Premium delivery, concierge service

Visit driiveme.com

Key Findings

We analyzed Driiveme.com page load time and found that the first response time was 302 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

driiveme.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

driiveme.com

302 ms

www.driiveme.com

373 ms

main.css

715 ms

jqueryUi.css

206 ms

css

63 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 60% of them (33 requests) were addressed to the original Driiveme.com, 7% (4 requests) were made to Facebook.com and 5% (3 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (961 ms) belongs to the original domain Driiveme.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 629.6 kB (63%)

Content Size

992.8 kB

After Optimization

363.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Driiveme.com main page is 992.8 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. 35% of websites need less resources to load. CSS take 399.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.0 kB

  • Original 47.4 kB
  • After minification 45.4 kB
  • After compression 8.4 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 39.0 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 6.4 kB

  • Original 178.4 kB
  • After minification 172.0 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. Driive Me images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 236.7 kB

  • Original 367.9 kB
  • After minification 367.9 kB
  • After compression 131.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 236.7 kB or 64% of the original size.

CSS Optimization

-87%

Potential reduce by 347.5 kB

  • Original 399.2 kB
  • After minification 336.9 kB
  • After compression 51.7 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. Driiveme.com needs all CSS files to be minified and compressed as it can save up to 347.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

51

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

driiveme.com

driiveme.com

302 ms

www.driiveme.com

www.driiveme.com

373 ms

main.css

main.css

715 ms

jqueryUi.css

jqueryUi.css

206 ms

css

css

63 ms

driiveme.main.js

driiveme.main.js

619 ms

config_home.js

config_home.js

210 ms

config_search_form.js

config_search_form.js

211 ms

config_slideshow_trajet.js

config_slideshow_trajet.js

215 ms

config_slideshow_testimony.js

config_slideshow_testimony.js

302 ms

conversion.js

conversion.js

32 ms

analytics.js

analytics.js

87 ms

staticmap

staticmap

69 ms

flag-FR.png

flag-FR.png

115 ms

flag-GB.png

flag-GB.png

116 ms

logo-driiveme.png

logo-driiveme.png

117 ms

icon-pin-departure.png

icon-pin-departure.png

117 ms

icon-pin-destination.png

icon-pin-destination.png

117 ms

hero-grass.png

hero-grass.png

118 ms

hero-car-group.png

hero-car-group.png

513 ms

hero-pins.png

hero-pins.png

315 ms

logos-press-white.png

logos-press-white.png

315 ms

icon-pack-1.png

icon-pack-1.png

314 ms

icon-pack-2.png

icon-pack-2.png

315 ms

icon-pack-3.png

icon-pack-3.png

314 ms

sticker-hertz.png

sticker-hertz.png

403 ms

sprite-car-type.png

sprite-car-type.png

403 ms

video-jt.jpg

video-jt.jpg

515 ms

logos-press-video.png

logos-press-video.png

405 ms

145615007548973_50x50.jpg

145615007548973_50x50.jpg

405 ms

144475757539453_50x50.JPG

144475757539453_50x50.JPG

505 ms

145450602858831_50x50.jpg

145450602858831_50x50.jpg

510 ms

143958974344583_50x50.jpg

143958974344583_50x50.jpg

513 ms

footer-head.png

footer-head.png

512 ms

logo-driiveme-white.png

logo-driiveme-white.png

606 ms

loader.svg

loader.svg

607 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

961 ms

collect

collect

40 ms

collect

collect

95 ms

63 ms

fbds.js

fbds.js

193 ms

all.js

all.js

287 ms

widget_v2.132.js

widget_v2.132.js

24 ms

133 ms

__$$__stringtable_lang_fr.js

__$$__stringtable_lang_fr.js

31 ms

21 ms

22 ms

xd_arbiter.php

xd_arbiter.php

118 ms

xd_arbiter.php

xd_arbiter.php

233 ms

4 ms

xd_arbiter.php

xd_arbiter.php

91 ms

like.php

like.php

59 ms

R-A8WEDAygL.js

R-A8WEDAygL.js

436 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

426 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

61 ms

Accessibility Review

driiveme.com accessibility score

86

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

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

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

driiveme.com 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

SEO Factors

driiveme.com SEO score

76

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Driiveme.com 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 Driiveme.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

driiveme.com

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