getaround.com website review

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

About 530 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (Google Tag Manager, gumlet.io and Sentry and others), adding 1.1 MB and 755 ms of main-thread time.

Google Tag Manager costs a phone 755 ms of main-thread work and 1.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.

About 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Some of these cookies are set by our partners. You can visi…”.

The page becomes fully interactive after 11.6 s. Good is under 3.8 s.

Scripts block taps and scrolling for 657 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 321 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 181 ms to 238 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

By the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element has a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 30 pages on getaround.com and 6 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/car-rental/united-states/type/city, /car-rental/united-states/type/commercial, /car-rental/united-states/type/family and /car-rental/united-states/type/suv declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, /car-rental/united-states/type/city, /car-rental/united-states/type/commercial, /car-rental/united-states/type/family and /car-rental/united-states/type/suv all use the title “Local Car Hire and Carsharing - Getaround”. Search engines can't tell which page to show for a search, so each competes with the others.

/help has no meta description, so Google writes the search snippet from whatever text it finds.

/car-rental/united-states/type/city, /car-rental/united-states/type/commercial, /car-rental/united-states/type/family and /car-rental/united-states/type/suv use the same meta description. A description written for each page earns more clicks.

/how-it-works has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.

Large scripts ship without source maps.

1 link go through two or more redirects, for example https://app.adjust.com/u23j79z?fallback=https%3A%2F%2Fapps.apple.com%2Fus%2Fapp%2Fdrivy%2Fid492238016%3Fmt%3D8%26l%3Den_US&redirect_macos=https%3A%2F%2Fapps.apple.com%2Fus%2Fapp%2Fdrivy%2Fid492238016%3Fmt%3D8%26l%3Den_US.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

getaround.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

getaround.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 339 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.