Tools & Wizards About Us
getaround.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

getaround.com

Local Car Rental and Carsharing - Getaround

Page Load Speed

2.6 sec in total

First Response

44 ms

Resources Loaded

2.2 sec

Page Rendered

439 ms

getaround.com screenshot

About Website

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

Rent a car in an instant, open the car with the Getaround app, #1 for carsharing! 24/7. 200mi/day and insurance included.

Visit getaround.com

Key Findings

We analyzed Getaround.com page load time and found that the first response time was 44 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

getaround.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value11,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value35.1 s

0/100

10%

Network Requests Diagram

getaround.com

44 ms

www.getaround.com

165 ms

2456610745.js

248 ms

bootstrap.css

41 ms

web_app.css

83 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 38% of them (29 requests) were addressed to the original Getaround.com, 11% (8 requests) were made to D.adroll.com and 8% (6 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (679 ms) relates to the external source I.vimeocdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 783.3 kB (45%)

Content Size

1.8 MB

After Optimization

967.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Getaround.com 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. 50% of websites need less resources to load. Images take 653.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 31.4 kB

  • Original 42.3 kB
  • After minification 34.2 kB
  • After compression 10.8 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 8.0 kB, which is 19% 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 31.4 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 653.3 kB
  • After minification 652.2 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. Getaround images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 338.8 kB

  • Original 570.1 kB
  • After minification 570.1 kB
  • After compression 231.3 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 338.8 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 412.0 kB

  • Original 484.7 kB
  • After minification 482.1 kB
  • After compression 72.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. Getaround.com needs all CSS files to be minified and compressed as it can save up to 412.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

58

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Getaround. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

getaround.com

getaround.com

44 ms

www.getaround.com

www.getaround.com

165 ms

2456610745.js

2456610745.js

248 ms

bootstrap.css

bootstrap.css

41 ms

web_app.css

web_app.css

83 ms

web_public.css

web_public.css

82 ms

modernizr.custom.min.js

modernizr.custom.min.js

66 ms

require.min.js

require.min.js

66 ms

gtm.js

gtm.js

106 ms

getaround_logo_white.svg

getaround_logo_white.svg

42 ms

60610637

60610637

74 ms

header_bg_rent.jpg

header_bg_rent.jpg

97 ms

header_bg_how_it_works.jpg

header_bg_how_it_works.jpg

69 ms

icon_num_1.svg

icon_num_1.svg

39 ms

icon_num_2.svg

icon_num_2.svg

43 ms

icon_num_3.svg

icon_num_3.svg

46 ms

car_bmw.jpg

car_bmw.jpg

95 ms

owner_kapil.jpg

owner_kapil.jpg

95 ms

car_tesla.jpg

car_tesla.jpg

95 ms

owner_bruno.jpg

owner_bruno.jpg

100 ms

car_mini.jpg

car_mini.jpg

131 ms

owner_kim.jpg

owner_kim.jpg

99 ms

header_bg_share_your_car.jpg

header_bg_share_your_car.jpg

163 ms

icon_extra_income.png

icon_extra_income.png

179 ms

icon_no_risk.png

icon_no_risk.png

256 ms

icon_smart_technology.png

icon_smart_technology.png

163 ms

app-store-badge.png

app-store-badge.png

162 ms

google_play_badge_v2.png

google_play_badge_v2.png

173 ms

getaround-min.js

getaround-min.js

210 ms

sommetroundedlight-webfont.woff

sommetroundedlight-webfont.woff

176 ms

getaroundicons-regular-webfont.woff

getaroundicons-regular-webfont.woff

191 ms

player.js

player.js

627 ms

player.css

player.css

425 ms

ga.js

ga.js

97 ms

vuid.min.js

vuid.min.js

496 ms

conversion_async.js

conversion_async.js

166 ms

roundtrip.js

roundtrip.js

85 ms

event.php

event.php

230 ms

fbds.js

fbds.js

230 ms

analytics.js

analytics.js

103 ms

__utm.gif

__utm.gif

21 ms

linkid.js

linkid.js

69 ms

47 ms

collect

collect

23 ms

collect

collect

72 ms

R5OU2FML25G6NP6QXH6NX6.js

R5OU2FML25G6NP6QXH6NX6.js

125 ms

sdk.js

sdk.js

183 ms

35 ms

135 ms

ga-audiences

ga-audiences

26 ms

56 ms

tr

tr

124 ms

tr

tr

165 ms

out

out

51 ms

out

out

61 ms

out

out

50 ms

out

out

49 ms

out

out

50 ms

out

out

60 ms

out

out

60 ms

62 ms

sync

sync

139 ms

119 ms

u.php

u.php

123 ms

pixel

pixel

160 ms

75 ms

xd_arbiter.php

xd_arbiter.php

340 ms

sd

sd

8 ms

377928.gif

377928.gif

141 ms

in

in

3 ms

proxy.html

proxy.html

137 ms

490960179.webp

490960179.webp

679 ms

tap.php

tap.php

151 ms

21 ms

lil_gee.png

lil_gee.png

106 ms

xd_arbiter.php

xd_arbiter.php

80 ms

Accessibility Review

getaround.com accessibility score

80

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 have valid values

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

getaround.com best practices score

75

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

Displays images with incorrect aspect ratio

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

getaround.com SEO score

100

Search Engine Optimization Advices

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

getaround.com

Open Graph data is detected on the main page of Getaround. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: