Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

driveshare.com

Classic Car Rental | Rentals & Community | Experiences | DRIVESHARE

Page Load Speed

2.7 sec in total

First Response

10 ms

Resources Loaded

873 ms

Page Rendered

1.8 sec

About Website

Welcome to driveshare.com homepage info - get ready to check DRIVESHARE best content for United States right away, or after learning these important things about driveshare.com

Vintage, sport or classic car rentals for weddings, photoshoots, fun. Own a classic car? List it with DRIVESHARE to owner rental and support your hobby.

Visit driveshare.com

Key Findings

We analyzed Driveshare.com page load time and found that the first response time was 10 ms and then it took 2.7 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

driveshare.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value59.7 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

driveshare.com

10 ms

driveshare.com

205 ms

modern-reset.css

14 ms

jquery-ui.min.css

25 ms

jquery.jcrop.css

26 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 89% of them (83 requests) were addressed to the original Driveshare.com, 2% (2 requests) were made to Tags.tiqcdn.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (286 ms) relates to the external source Tags.tiqcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (8%)

Content Size

25.9 MB

After Optimization

23.8 MB

In fact, the total size of Driveshare.com main page is 25.9 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. Only a small number of websites need less resources to load. Images take 25.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 59.7 kB

  • Original 69.2 kB
  • After minification 50.5 kB
  • After compression 9.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 18.7 kB, which is 27% 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 59.7 kB or 86% of the original size.

Image Optimization

-8%

Potential reduce by 2.0 MB

  • Original 25.3 MB
  • After minification 23.3 MB

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. DRIVESHARE images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 40.9 kB

  • Original 487.7 kB
  • After minification 487.4 kB
  • After compression 446.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.9 kB

  • Original 108.6 kB
  • After minification 108.5 kB
  • After compression 106.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. Driveshare.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (57%)

Requests Now

84

After Optimization

36

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

Accessibility Review

driveshare.com accessibility score

43

Accessibility Issues

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

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

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

driveshare.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

High

Page has valid source maps

SEO Factors

driveshare.com SEO score

85

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

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

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 Driveshare.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 Driveshare.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 DRIVESHARE. 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: